FS#63913 - [hey] Suggestion: bump epoch to 1 to prioritize it over previous AUR package

Attached to Project: Community Packages
Opened by Vic Luo (htfy96) - Tuesday, 24 September 2019, 23:08 GMT
Last edited by Jelle van der Waa (jelly) - Sunday, 03 November 2019, 14:28 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Jelle van der Waa (jelly)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Previous AUR package is date-versioned like 20180918.274_3dd8421-1. Therefore a warning is output for every upgrade:

warning: hey: local (20180918.274_3dd8421-1) is newer than community (0.1.2-1)

To automatically update previously-installed AUR package, I suggest bump the epoch of this epoch to 1.

Steps to reproduce:

$ sudo pacman -Syu
:: Starting full system upgrade...
warning: hey: local (20180918.274_3dd8421-1) is newer than community (0.1.2-1)
there is nothing to do
This task depends upon

Closed by  Jelle van der Waa (jelly)
Sunday, 03 November 2019, 14:28 GMT
Reason for closing:  Won't fix
Additional comments about closing:  agreed with eli's comment. Thankfully pacman warns about hey being in community now.
Comment by Eli Schwartz (eschwartz) - Tuesday, 24 September 2019, 23:39 GMT
The AUR package I just looked at was far too broken to worry about being compatible with it. Among numerous other issues, it built from bleeding edge git. I'm not sure I see the value in establishing continuity with the utterly broken travesty that was the old pkgver, and I'm not sure it is worth adding an epoch forever just because someone uploaded a broken package to the AUR -- if it were merely a matter of a pkgrel then it's a much easier case to make for respecting a properly formatted version specifier.

Loading...