-
Notifications
You must be signed in to change notification settings - Fork 602
Upgrade suitesparse to 7.11.0 #15289
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: 3.0-dev
Are you sure you want to change the base?
Upgrade suitesparse to 7.11.0 #15289
Conversation
088ae4f to
c8e85ed
Compare
c8e85ed to
fd102f8
Compare
|
|
||
| %changelog | ||
| * Mon Dec 15 2025 Durga Jagadeesh Palli <v-dpalli@microsoft.com> - 7.11.0-1 | ||
| - Upgrade to 7.11.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please mention upgrade reference. Fedora.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @sandeepkarambelkar, I have incorporated the changes based on your suggestions.
-Thank you!
fd102f8 to
d449df8
Compare
Hi @sandeepkarambelkar, can you please retrigger buddy build with the following packages? |
d449df8 to
37e143c
Compare
Hi @sandeepkarambelkar, I have made the necessary changes to fix the 55 license warnings in doc section. Thank you! |
3d42f06 to
72a31ef
Compare
|
I have addressed contribution-license warning. |
Buddy build has been completed successfully. Thank you! |
sandeepkarambelkar
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is rpmbuild warning -
time="2025-12-24T08:05:08Z" level=debug msg="RPM build warnings:"
time="2025-12-24T08:05:08Z" level=debug msg=" File listed twice: /usr/lib/libumfpack.so.6"
time="2025-12-24T08:05:08Z" level=debug msg=" File listed twice: /usr/lib/libumfpack.so.6.3.6"
Hi @sandeepkarambelkar, I have resolved this warnings and updated my changes.
-Thank you! |
sandeepkarambelkar
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Buddy Build Successful.
Changes LGTM.
sandeepkarambelkar
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
License files tagging need to be verified
| ! -iname "GPLv2.txt" \ | ||
| ! -iname "lesserv3.txt" \ | ||
| ! -iname "CONTRIBUTOR-LICENSE.txt" \ | ||
| ! -iname "SuiteSparse Individual Contributor License Agreement (20241011).pdf" \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you verify if all these license files are added in the licese file tagged. If not, can you actually tag all the valid license files with license tag?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @sandeepkarambelkar, I've verified that all license files are included in the RPM file (i.e, suitesparse-7.11.0-1.azl3.x86_64.rpm) using %license Licenses at line 331.

All the license files are placed in the below directory.
/usr/share/licenses/suitesparse/Licenses/

-Thank you!





Merge Checklist
All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)
*-staticsubpackages, etc.) have had theirReleasetag incremented../cgmanifest.json,./toolkit/scripts/toolchain/cgmanifest.json,.github/workflows/cgmanifest.json)./LICENSES-AND-NOTICES/SPECS/data/licenses.json,./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md,./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)*.signatures.jsonfilessudo make go-tidy-allandsudo make go-test-coveragepassSummary
Change Log
Does this affect the toolchain?
NO
Associated issues
Links to CVEs
Test Methodology