[Bug 1761418] Re: pkg-config --modversion libargon2 reports wrong version
Bastian Germann
1761418 at bugs.launchpad.net
Tue Feb 28 14:45:21 UTC 2023
This was fixed in argon2/0~20161029-2 (cosmic).
** Changed in: argon2 (Ubuntu)
Status: New => Confirmed
** Changed in: argon2 (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to argon2 in Ubuntu.
https://bugs.launchpad.net/bugs/1761418
Title:
pkg-config --modversion libargon2 reports wrong version
Status in argon2 package in Ubuntu:
Fix Released
Status in argon2 package in Debian:
Fix Released
Bug description:
Currently on a Ubuntu 18.04 (alpha/beta) installation,
pkg-config --modversion libargon2
reports
0~20161029
instead of the expected
20161029
output.
This however conflicts with the upstream pkg-config template,
https://github.com/P-H-C/phc-winner-argon2/blob/master/libargon2.pc
which advises the version 20161029 w/o a prefixed `0~` to be
advertised.
This breaks scripting which either parses the version reported by
pkg-config (e.g. `cabal`) or also scripting like
pkg-config --atleast-version=20161029 libargon2
which then fails to report the correct status.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/argon2/+bug/1761418/+subscriptions
More information about the foundations-bugs
mailing list