FS#48555 - {AUR} git push requests whitelist

Attached to Project: Arch Linux
Opened by Que Quotion (quequotion) - Sunday, 13 March 2016, 04:07 GMT
Last edited by Doug Newgard (Scimmia) - Sunday, 13 March 2016, 08:22 GMT
Task Type Feature Request
Category Arch Projects
Status Closed
Assigned To No-one
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

If AUR accepted only updates containting changes to at least .SRCINFO and PKGBUILD--the first time and every time (ie, refuse to open new repositories without them, thow some errors)--it would avoid users having to plod through painful git reset procedures, and ensure that maintainers do not neglect to update the version information reported by AUR.

Additional info:
* package version(s)
* config and/or log files etc.


Steps to reproduce:

AUR accepts an initial push request without {{ic|.SRCINFO}} and creates a broken repository (something should certainly be done about that).
AUR also accepts pushes without any change to {{ic|.SRCINFO}}, letting the version information go stale (although I've done this myself, to push minor changes, it's bad practice that perhaps should be prevented by mechanism).
This task depends upon

Closed by  Doug Newgard (Scimmia)
Sunday, 13 March 2016, 08:22 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#46130 
Comment by Que Quotion (quequotion) - Sunday, 13 March 2016, 04:56 GMT
I had a good idea.

If this were implemented, I would furthermore propose that it removes the need for pkgrel() in PKGBUILD and .SCRINFO altogether: we can use the commit number as pkgrel()

Why don't we use commit numbers as pkgrel()?

Loading...