Community Packages

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#56697 - [groovy] pkgrel decreased

Attached to Project: Community Packages
Opened by Erich Eckner (deepthought) - Wednesday, 13 December 2017, 08:48 GMT
Last edited by Alexander F. Rødseth (xyproto) - Wednesday, 13 December 2017, 14:26 GMT
Task Type General Gripe
Category Packages
Status Closed
Assigned To Alexander F. Rødseth (xyproto)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No



The pkgrel of groovy was decreased from 2 to 1 in git commit 0054a8dae002 (svn-to-git).
Please don't do that. Either the built package was already pkgrel=1, then you should keep attention, that the source matches the package, or it was already published as pkgrel=2, then you'll break the version comparison in pacman and users won't fetch the new version.

In any case, this breaks downstream distributions (like archlinux32), who assume increasing package epoch-version-pkgrel combinations.

Additional info:
* package version(s)
groovy 2.4.13-2 vs. groovy 2.4.13-1
This task depends upon

Closed by  Alexander F. Rødseth (xyproto)
Wednesday, 13 December 2017, 14:26 GMT
Reason for closing:  None
Comment by Alexander F. Rødseth (xyproto) - Wednesday, 13 December 2017, 14:26 GMT
The package was only pushed to [community] with an increasing pkgrel, but I'll keep archlinux32 in mind in the future.