FS#72740 - [vmaf] package flagged as outdated for almost a year, still in the v1 branch.

Attached to Project: Community Packages
Opened by Alexandre Demers (oxalin) - Sunday, 14 November 2021, 03:27 GMT
Last edited by Allan McRae (Allan) - Sunday, 14 November 2021, 04:17 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture All
Severity Very Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: I'm lib32-vmaf's maintainer. The lib32 package depends on the native one. The native package hasn't been updated since almost a year, which means it has completely skipped the v2 branch for now. Is there any obvious reason for not updating this package and not letting any cue about why this would be? I've waited for many months for an update and I just pushed my update to v2.3.0


Additional info:
lib32-vmaf depends on vmaf, which was not updated for almost a year. This prevents updating the lib32 version.
This task depends upon

Closed by  Allan McRae (Allan)
Sunday, 14 November 2021, 04:17 GMT
Reason for closing:  Not a bug
Additional comments about closing:  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.

Loading...