FS#77656 - [archweb] Package "out of date" flag date is inaccurate for mixed major/minor releases

Attached to Project: Arch Linux
Opened by Mark Blakeney (bulletmark) - Sunday, 26 February 2023, 22:58 GMT
Last edited by Kristian (klausenbusk) - Monday, 05 June 2023, 17:41 GMT
Task Type Bug Report
Category Web Sites
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 3
Private No

Details

Easiest to just immediately give example for one package:

Package "python" major version 3.11 was released on 2022-10-24 (i.e. 126 days ago) and was flagged out of date then. However, there have been 3.10.* minor releases updated on Arch since so the "out of date" flag gets reset until somebody notices and re-flags it. Thus the new flag date (currently 2022-12-24, 65 days ago) is grossly miss-representative. A possible (simple?) solution is to allow the flag raiser to enter a version number on the form so the flag is not cleared until the new update(s) is that version or beyond? Of course should allow the package maintainer to reset that field for the inevitable cases where the version is entered incorrectly.

Related to this is the case the Arch "python" package is currently 3.10.9 but the latest available is 3.10.10 (2022-02-08, 18 days ago), i.e. there is also a new minor update pending and there should be a way to flag that. So possibly a (more involved?) solution is to have 2 separate out-of-date flags, one for major releases and another for minor releases?
This task depends upon

Closed by  Kristian (klausenbusk)
Monday, 05 June 2023, 17:41 GMT
Reason for closing:  Upstream
Additional comments about closing:  Please report upstream if this is still relevant: https://github.com/archlinux/aurweb.