> Message-ID: <20150123115017.14690.22831(a)typhoon.lan>
> 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.
Okay, thanks for the info, will do that. In fact, the PKGBUILD I attached was
not the most recent one (with the correct version numbers). Anyway, a more
delightful error message like "Package eibd already exists in pkgbase eibd,
cannot overwrite with base bcusdk" would have made more sense to me...
Sven Fischer -- Platzer Höhenweg 34, 51429 Bergisch Gladbach, Germany
Tel: +49-(0)2204-480985, Fax: +49-(0)2204-9670019