Allan McRae <[EMAIL PROTECTED]> wrote: > Loui wrote: > > Allan McRae <[EMAIL PROTECTED]> 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.
