Community Packages

Please read this before reporting a bug:
http://wiki.archlinux.org/index.php/Reporting_Bug_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!
Tasklist

FS#58606 - [consul] Wrong version number on 'consul info'

Attached to Project: Community Packages
Opened by Tim (bastelfreak) - Tuesday, 15 May 2018, 11:06 GMT
Last edited by Thore Bödecker (foxxx0) - Tuesday, 22 May 2018, 13:01 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Hi,
I'm using the latest consul package 1.1.0-1. 'consul version' reports:

Consul 1.1.0-dev
Protocol 2 spoken by default, understands 2 to 3 (agent will automatically use protocol >2 when speaking to compatible agents)

but a 'consul version' from the official binary https://releases.hashicorp.com/consul/1.1.0/consul_1.1.0_linux_amd64.zip reports:

Consul v1.1.0
Protocol 2 spoken by default, understands 2 to 3 (agent will automatically use protocol >2 when speaking to compatible agents)

Tools that parse that version number will break. Also it might be possible that the codebase used for the arch package isn't equal to the one used for the official release. Let me know if you need further information.

Cheers, Tim
This task depends upon

Closed by  Thore Bödecker (foxxx0)
Tuesday, 22 May 2018, 13:01 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed as of consul 1.1.0-2
Comment by Eli Schwartz (eschwartz) - Thursday, 17 May 2018, 02:08 GMT
We're using the tagged release, if the tagged release does not contain the right version number then complain to upstream: https://git.archlinux.org/svntogit/community.git/tree/trunk/PKGBUILD?h=packages/consul#n15
Comment by Thore Bödecker (foxxx0) - Tuesday, 22 May 2018, 13:00 GMT
The version number itself is ok, but the method for determining any suffixes (like "-rc", "-dev", etc.) seems rather weird and is heavily mapped to their release process and will simply add "-dev" all the time when building from tagged tarballs.

After a quick study of how this version string is composed I have written a patch that simply removes all that logic and uses the supplied version number of the tarball-source without any suffixes.

Loading...