Firmicus wrote:

I am trying to upload the package perl-ppi to AUR, but I get the error message "You are not allowed to overwrite the perl-ppi package" even though this package does not exist on AUR.

It would seem you've run into the worlds most annoying bug (http://bugs.archlinux.org/task/8672). But it is interesting that this package appears to have never existed in the AUR.

Firmicus wrote:

Allan McRae a écrit :

...

Firmicus wrote:

...

I am trying to upload the package perl-ppi to AUR, but I get the error message "You are not allowed to overwrite the perl-ppi package" even though this package does not exist on AUR.

It would seem you've run into the worlds most annoying bug (http://bugs.archlinux.org/task/8672). But it is interesting that this package appears to have never existed in the AUR.

This is a pain, coz perl-ppi is a dependency of perl-critic, which I have uploaded to AUR on Saturday. What should I do?

Well, I'm not really sure. Maybe directly contact a person with server powers (Simo?). We should probably see about getting a TU access so we can clear those buggy packages out as they occur, at least until the bug gets properly fixed. I have seen this pop up on the mailing list several times now. In the mean time, I would post the perl-ppi PKGBUILD as a comment in perl-critic. Allan

On Wed, 21 May 2008 16:49:31 +1000 Allan McRae wrote:

Reading the bug report, there might be a work around. If perl-critic is the only package depending on perl-ppi, delete it, then try uploading perl-ppi. It seems you should always upload dependencies first. I am interested to see if this works.

From what I remember about the database it shouldn't work. The ghost entries for the package and it's dependencies will still remain even after you delete it. If you're starting off fresh though, and you upload the deps first then things should be alright.

Allan McRae wrote:

Loui wrote:

...

Allan McRae wrote:

...

Reading the bug report, there might be a work around. If perl-critic is the only package depending on perl-ppi, delete it, then try uploading perl-ppi. It seems you should always upload dependencies first. I am interested to see if this works.

From what I remember about the database it shouldn't work. The ghost entries for the package and it's dependencies will still remain even after you delete it.

If you're starting off fresh though, and you upload the deps first then things should be alright.

OK then. What about, remove perl-critic. Upload perl-ppi to community. Remove perl-ppi from community. Submit perl-ppi to AUR. Submit perl-critic to AUR. Would that clear the ghost entry by converting it to a real entry first?

That could work. I haven't looked at the [community] tools enough to be really sure. Try it out! Cheers.

On Thu, 22 May 2008 15:38:35 +0200 Xavier wrote:

I am curious why there doesn't seem to be any progress on this. Is this caused by serious lack of man power or is the issue so complex no one is able to figure out what is happening or is it something else? From my limited point of view as an user, AUR development seemed to go well recently with a cool 1.5 release. Please don't take this as a complaint / whining, I try my best to help out with pacman so I know how hard it is :) I am just a bit concerned since that issue is apparently generating quite some noise, and also seems to slow things down by preventing users from uploading packages.

Lack of developer manpower is an issue. There are about 10 outstanding patches on the aur-dev list that haven't seen any response by a developer. The earliest one was sent on May 4th, the latest on May 11th. There are even more patches that I submitted that had positive responses but haven't been pushed to the main testing repo. Developers are the only ones that can push them into the source and are the only ones that can access the actual server and database. We need more developers.