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#20452 - libassuan 2.0.1 must depend on libgpg-error >= 1.8
Attached to Project:
Arch Linux
Opened by Raphael Kubo da Costa (rakuco) - Thursday, 12 August 2010, 19:54 GMT
Last edited by Andreas Radke (AndyRTR) - Friday, 13 August 2010, 17:19 GMT
Opened by Raphael Kubo da Costa (rakuco) - Thursday, 12 August 2010, 19:54 GMT
Last edited by Andreas Radke (AndyRTR) - Friday, 13 August 2010, 17:19 GMT
|
DetailsDescription:
According to libassuan's ChangeLog, the minimum libgpg-error version it supports is now 1.8. There should be a hard dependency on this version in libassuan's PKGBUILD. Right now, libassuan has been updated to 2.0.1, but libgpg-error is still on 1.7 in extra (version 1.9 is in testing), which means I can't compile anything which uses libassuan/libgpg-error because of missing symbols. |
This task depends upon
Comment by Andreas Radke (AndyRTR) -
Friday, 13 August 2010, 05:17 GMT
should be fixed with libgpg-error 1.9-2 now moved to core. please confirm.
Comment by Raphael Kubo da Costa (rakuco) -
Friday, 13 August 2010, 15:00 GMT
Yes, everything works fine now. However, my point is just that libassuan's PKGBUILD should have a dependency on 'libgpg-error>=1.8', not simply 'libgpg-error' (and the version dependency should be updated when needed in order to prevent similar problems in the future).
Comment by Ionut Biru (wonder) -
Friday, 13 August 2010, 15:04 GMT
we can argue that versioned dependencies should be removed. versioned dependencies doesn't reflect the values from readme/changelog whatever