FS#40517 - [xapian-core] Odd versioning scheme

Attached to Project: Arch Linux
Opened by Daurnimator (daurnimator) - Saturday, 24 May 2014, 02:15 GMT
Last edited by Bartłomiej Piotrowski (Barthalion) - Saturday, 24 May 2014, 09:05 GMT
Task Type General Gripe
Category Packages: Extra
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

The version number scheme for this package is very odd.
Why `1:1.2.17-1` instead of `1.2.17-1`?

The `1:` prefix doesn't seem to come from upstream (e.g. see annouce at http://article.gmane.org/gmane.comp.search.xapian.general/9685 )

Other packages like https://aur.archlinux.org/packages/xapian-lua-bindings/ are depending on `xapian-core>=1.3.1`.
Which manages to (incorrectly) pass!
This task depends upon

Closed by  Bartłomiej Piotrowski (Barthalion)
Saturday, 24 May 2014, 09:05 GMT
Reason for closing:  Not a bug
Comment by Doug Newgard (Scimmia) - Saturday, 24 May 2014, 05:17 GMT
It's a epoch: https://wiki.archlinux.org/index.php/PKGBUILD#epoch
Comment by Daurnimator (daurnimator) - Saturday, 24 May 2014, 05:29 GMT
Ah; okay.

Nowhere in the wiki could I find documentation of the epoch appearing as a `n:` prefix.
I'll file bugs with the other packages that depend on this one, that don't have an epoch set.

Out of curiosity, what was the epoch event for xapian-core?
Comment by Doug Newgard (Scimmia) - Saturday, 24 May 2014, 05:35 GMT
It was added here: https://projects.archlinux.org/svntogit/community.git/commit/?id=5086a4a1f463fe9aa7e832bde90b470e6d3651d6

The package was downgraded, so an epoch was necessary.
Comment by Daurnimator (daurnimator) - Saturday, 24 May 2014, 05:37 GMT
heh; interesting, I just made an AUR package for 1.3.1 too... https://aur.archlinux.org/packages/xapian-core-development/

Loading...