[aur-general] Can't update my own PKGBUILD, where to find errors?
Hello everybody, trying to update small fixes to the eibd package, AUR upload always responses to me with "error: failed to upload bcusdk-0.0.5-5.src.tar.gz: You are not allowed to overwrite the eibd package.", although I own the package. I am quite a AUR NOOB, but trying to find a hint what could be wrong led me to nothing. Wouldn't it be possible to respond with an error that tells me WHY I am unable to upload (missing permission, wrong version etc....)? Regards, Sven -- Sven Fischer -- Platzer Höhenweg 34, 51429 Bergisch Gladbach, Germany Tel: +49-(0)2204-480985, Fax: +49-(0)2204-9670019 sven@leiderfischer.de
On Thu, 22 Jan 2015 23:24:24 +0100 Sven Fischer <sven@leiderfischer.de> wrote:
Hello everybody,
trying to update small fixes to the eibd package, AUR upload always responses to me with "error: failed to upload bcusdk-0.0.5-5.src.tar.gz: You are not allowed to overwrite the eibd package.", although I own the package. I am quite a AUR NOOB, but trying to find a hint what could be wrong led me to nothing. Wouldn't it be possible to respond with an error that tells me WHY I am unable to upload (missing permission, wrong version etc....)?
Regards, Sven
Because you're trying to overwrite one pkgbase (eibd) with a different one (bcusdk).
On Fri, 23 Jan 2015 at 00:02:02, Doug Newgard wrote:
On Thu, 22 Jan 2015 23:24:24 +0100 Sven Fischer <sven@leiderfischer.de> wrote:
Hello everybody,
trying to update small fixes to the eibd package, AUR upload always responses to me with "error: failed to upload bcusdk-0.0.5-5.src.tar.gz: You are not allowed to overwrite the eibd package.", although I own the package. I am quite a AUR NOOB, but trying to find a hint what could be wrong led me to nothing. Wouldn't it be possible to respond with an error that tells me WHY I am unable to upload (missing permission, wrong version etc....)?
Regards, Sven
Because you're trying to overwrite one pkgbase (eibd) with a different one (bcusdk).
Let me elaborate just a bit: There currently isn't a bcusdk package base in the AUR, so a new package base is created upon package submission. That new package base contains a package eibd which is already part of the package base eibd, though. Since a package base cannot contain a package that is already provided by another one, you receive that strange error message. Hope that clarifies it a bit. Regards, Lukas
On 23-01-15 00:23, Lukas Fleischer wrote:
Let me elaborate just a bit: There currently isn't a bcusdk package base in the AUR, so a new package base is created upon package submission. That new package base contains a package eibd which is already part of the package base eibd, though. Since a package base cannot contain a package that is already provided by another one, you receive that strange error message. Hope that clarifies it a bit. Regards, Lukas
The situation is weirder then that, check the PKGBUILD for the current version : pkgbase=('bcusdk') pkgname=('eibd') pkgver=0.0.5 pkgrel=4 Maybe the problems are caused by uploading a faulty .AURINFO or .SRCINFO file in the past. Sven, if you do want pkgbase bcusdk and pkgname eidb, i suggest you upload a dummy bcusdk pacakge, then request eidb to be merged into bcusdk. Once the merge has completed, you can then upload the correct package. LVV
On Fri, 23 Jan 2015 at 12:34:40, LoneVVolf wrote:
On 23-01-15 00:23, Lukas Fleischer wrote:
Let me elaborate just a bit: There currently isn't a bcusdk package base in the AUR, so a new package base is created upon package submission. That new package base contains a package eibd which is already part of the package base eibd, though. Since a package base cannot contain a package that is already provided by another one, you receive that strange error message. Hope that clarifies it a bit. Regards, Lukas
The situation is weirder then that, check the PKGBUILD for the current version :
pkgbase=('bcusdk') pkgname=('eibd') pkgver=0.0.5 pkgrel=4
Maybe the problems are caused by uploading a faulty .AURINFO or .SRCINFO file in the past.
No, the package was last updated on 2014-03-04 20:25 which was before the AUR supported split packages. During the migration, we automatically assigned the package base eibd.
Sven, if you do want pkgbase bcusdk and pkgname eidb, i suggest you upload a dummy bcusdk pacakge, then request eidb to be merged into bcusdk.
... where "dummy bcusdk pacakge" means: Use the package base bcusdk without any additional packages.
Once the merge has completed, you can then upload the correct package.
Agreed.
LVV
Regards, Lukas
participants (4)
-
Doug Newgard
-
LoneVVolf
-
Lukas Fleischer
-
Sven Fischer