FS#4084 - Package orphaned when created in community CVS
Attached to Project:
AUR web interface
Opened by Jeff Mickey (codemac) - Wednesday, 01 March 2006, 07:43 GMT
Last edited by Loui Chang (louipc) - Thursday, 13 August 2009, 10:47 GMT
Opened by Jeff Mickey (codemac) - Wednesday, 01 March 2006, 07:43 GMT
Last edited by Loui Chang (louipc) - Thursday, 13 August 2009, 10:47 GMT
|
Details
If you move a package from unsupported to community, the
package gets orphaned.
If you add a package to community, and it was never in unsupported, it still gets orphaned. The aur front end should reflect who is creating the files in CVS. |
This task depends upon
Closed by Loui Chang (louipc)
Thursday, 13 August 2009, 10:47 GMT
Reason for closing: Won't implement
Additional comments about closing: Community now uses devtools.
Thursday, 13 August 2009, 10:47 GMT
Reason for closing: Won't implement
Additional comments about closing: Community now uses devtools.
So this is unlikely to ever get changed, and is a stated behavior of the system, and strictly speaking not a bug. This is exactly the same way the dev system works.
If anyone wants to look at the code and strategize some good ways to actually change this, and implement them, please have a go!
How can i create a fake community in my local system to try to solve this ? So i can see if i can solve this issue.
Thanks
I'll try to look into it.