Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#52028 - [pacman] updpkgsums generates wrong hashes for mixed archs
Attached to Project:
Arch Linux
Opened by NicoHood (NicoHood) - Friday, 02 December 2016, 13:54 GMT
Last edited by Doug Newgard (Scimmia) - Friday, 02 December 2016, 15:21 GMT
Opened by NicoHood (NicoHood) - Friday, 02 December 2016, 13:54 GMT
Last edited by Doug Newgard (Scimmia) - Friday, 02 December 2016, 15:21 GMT
|
DetailsIf you have a package with x86_64 sources and also i686 sources updpkgsums generates wrong values for the 32 bit hashes.
I could produce this with the following spotify PKGBUILD. The linked diff shows the wrong vs the correct hashes. https://gist.github.com/NicoHood/5ae26f778d4c62aee32e4b56081cc925/revisions#diff-dfa7cdd9c34798e1af82f172b0822f08 The download sources for this package will likely change soon, so you will possibly not be able to reproduce it with exactly this package, but the bug should be clear enough. |
This task depends upon
Closed by Doug Newgard (Scimmia)
Friday, 02 December 2016, 15:21 GMT
Reason for closing: Not a bug
Additional comments about closing: updpkgsums isn't part of pacman anymore, anyway. Not sure where pacman-contrib will end up.
Friday, 02 December 2016, 15:21 GMT
Reason for closing: Not a bug
Additional comments about closing: updpkgsums isn't part of pacman anymore, anyway. Not sure where pacman-contrib will end up.
Comment by Dave Reisner (falconindy) -
Friday, 02 December 2016, 15:01 GMT
No, your PKGBUILD is broken because of your source renaming rules. $CARCH cannot be simultaneously 2 values as you expect it to be when it comes time to do checksum generation.