pkg-config --modversion libargon2 reports wrong version

Bug #1761418 reported by Herbert V. Riedel on 2018-04-05
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
argon2 (Debian)
Fix Released
Unknown
argon2 (Ubuntu)
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://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.

tags: added: bionic
Changed in argon2 (Debian):
status: Unknown → New
Changed in argon2 (Debian):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.