FS#32807 - TU ninja edit revisions

Attached to Project: AUR web interface
Opened by Kyle Keen (keenerd) - Thursday, 22 November 2012, 15:48 GMT
Last edited by Lukas Fleischer (lfleischer) - Tuesday, 09 June 2015, 06:55 GMT
Task Type Feature Request
Category Backend
Status Closed
Assigned To canyonknight (canyonknight)
Lukas Fleischer (lfleischer)
Architecture All
Severity Low
Priority Normal
Reported Version 2.0.1
Due in Version 4.0.0
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

It is our job to keep the AUR in decent look shape. Part of this is revising bad pkgbuilds. Currently we can take ownership of the package, update and orphan. The maintainer has to re-adopt, assuming someone else does not snipe it first. This is not exactly nice to the maintainer of the package.

Feature: TUs should have the ability to overwrite packages without breaking ownership. We can do our job and the actual maintainer can continue to do theirs.
This task depends upon

Closed by  Lukas Fleischer (lfleischer)
Tuesday, 09 June 2015, 06:55 GMT
Reason for closing:  Implemented
Additional comments about closing:  Implemented in 4.0.0-rc1.
Comment by Frederik “Freso” S. Olesen (Freso) - Thursday, 31 January 2013, 20:35 GMT
If this is implemented, it would be nice to let the package maintainer know about it. I, for example, keep all my PKGBUILDs version controlled via Git. If someone edits a package but does not make a pull request or otherwise get their change pushed to my repository, next package update will just see that change wiped.
Comment by canyonknight (canyonknight) - Thursday, 21 February 2013, 22:40 GMT
This seems like a useful feature, but I think it would be wise to first implement tracking of the last packager. It would make it a bit clearer who actually updated the package.

As to the concern about letting a package maintainer know whenever their package is modified by a TU, I think a TU leaving a comment after ninja editing a package would be helpful.
Comment by Lukas Fleischer (lfleischer) - Wednesday, 07 January 2015, 11:46 GMT
Implemented in ebf8f5d (git-serve.py: Allow TUs to push to any repository, 2015-01-07). You can test this on aur-dev.archlinux.org.

Loading...