Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_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!
https://wiki.archlinux.org/title/Bug_reporting_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!
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
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
|
DetailsThe 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
Saturday, 24 May 2014, 09:05 GMT
Reason for closing: Not a bug
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?
The package was downgraded, so an epoch was necessary.