pkg-config --modversion libargon2 reports wrong version
Bug #1761418 reported by
Herbert V. Riedel
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| argon2 (Debian) |
Fix Released
|
Unknown
|
|||
| argon2 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
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:/
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-
which then fails to report the correct status.
| tags: | added: bionic |
| Changed in argon2 (Debian): | |
| status: | Unknown → New |
| Changed in argon2 (Debian): | |
| status: | New → Fix Released |
Revision history for this message
| Bastian Germann (bastian-germann) wrote | #1 |
| Changed in argon2 (Ubuntu): | |
| status: | New → Confirmed |
| status: | Confirmed → Fix Released |
To post a comment you must log in.
This was fixed in argon2/0~20161029-2 (cosmic).