AUR web interface

Tasklist

FS#2446 - Return package to Unsupported Repository if lost interest by TU

Attached to Project: AUR web interface
Opened by Mark A. Friedman (maf19590) - Thursday, 24 March 2005, 17:12 GMT
Last edited by Paul Mattal (paul) - Monday, 11 April 2005, 20:13 GMT
Task Type Feature Request
Category Backend
Status Closed
Assigned To Paul Mattal (paul)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

Your process states:

Alternately, if a TU loses interest in a package, the TU may abandon the package or remove it from the AUR repository altogether.

Why not return the package to the Unsupported Repository?
This task depends upon

Closed by  Paul Mattal (paul)
Thursday, 14 April 2005, 00:54 GMT
Reason for closing:  Fixed
Additional comments about closing:  Ben has added the verbiage to the next version of the Guidelines. These will appear in the next version.
Comment by Paul Mattal (paul) - Sunday, 10 April 2005, 01:25 GMT
It's hard to transition from AUR (now community) repository to unsupported in a graceful way, since the files are in different places. In community, they're in CVS, and there's a binary package in the repo. For unsupported, it's on the filesystem linked off the webserver.

Since these two are so different, the easiest way to go back is simply to re-upload the package to unsupported after it has been deleted from the community repo.

Does this make sense? If so, I'll close this bug.
Comment by Dusty Phillips (Dusty) - Wednesday, 13 April 2005, 19:27 GMT
It makes sense to me, but the documentation/guidelines should probably be updated to reflect this suggestion.
Comment by Paul Mattal (paul) - Wednesday, 13 April 2005, 22:01 GMT
I've recommended this to Ben to add to the docs. As soon as I've heard from him, I'll close this bug. Then the new Guidelines would be released along with v1.0.1 sometime in the next few days.

Loading...