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#47889 - [confuse] Wrong checksum
Attached to Project:
Community Packages
Opened by Jonathan Arnold (jdarnold) - Monday, 25 January 2016, 11:49 GMT
Last edited by Doug Newgard (Scimmia) - Tuesday, 26 January 2016, 00:46 GMT
Opened by Jonathan Arnold (jdarnold) - Monday, 25 January 2016, 11:49 GMT
Last edited by Doug Newgard (Scimmia) - Tuesday, 26 January 2016, 00:46 GMT
|
DetailsDescription:
md5sum is wrong for the x86_64 architecture. I get 92a8754f72a6af2e219232ec516f1849 for an md5sum, but that's not what is in the pkgbuild. Additional info: * package version(s) 2.8.2 * config and/or log files etc. Steps to reproduce: |
This task depends upon
Comment by Todd Morrison (toddpi314) -
Monday, 25 January 2016, 14:08 GMT
Just hit this as a dep of i3Status when using TWM
Comment by Doug Newgard (Scimmia) -
Monday, 25 January 2016, 14:56 GMT
Looks correct to me.
Comment by Doug Newgard (Scimmia) -
Monday, 25 January 2016, 16:20 GMT
Deleted unrelated comments. Keep it on topic, people.
Comment by Jonathan Arnold (jdarnold) -
Monday, 25 January 2016, 18:40 GMT
Ah, thanks for the (now deleted) comment about the unknown trust. I must have missed that part of the error and just saw the checksum problem - weird way to report it. Guess the keyring got updated and it now works fine.
Comment by Doug Newgard (Scimmia) -
Tuesday, 26 January 2016, 00:46 GMT
So this was never about the md5sum. Please include EXACT error messages next time.