Will renaming the package mean renaming the actual library as well for Lintian to be happy?
The ecere-dev package also provides /usr/lib/i386-linux-gnu/libec.so On Tue, Jan 8, 2013 at 6:44 PM, Dmitrijs Ledkovs <x...@debian.org> wrote: > On 8 January 2013 19:11, Ansgar Burchardt <ans...@debian.org> wrote: > > Control: severity -1 serious > > > > Dmitrijs Ledkovs <x...@debian.org> writes: > >> ecere-sdk and eclib packages both have binary package libec0. > > > > Two packages building the same binary is certainly a RC bug. > > > >> Both are "Library for modular symbols and elliptic curves over Q", but I > >> am not sure if the two packages are the same or different sources, and > >> how to name them. > > > > No, eclib's libec0 says that, but the one from ecere-sdk says "eC > > Compiler Library", see [1]. > > > > [1] <http://packages.debian.org/search?keywords=libec0> > > > > Ah, thanks for this link. I must have mixed up the pages I was looking at. > > >> The options are: > >> 1) ecere-sdk drops the package & build-deps on the eclib one > >> 2) eclib is dropped in favor of ecere-sdk > >> 3) ecere-sdk renames its libec0 to something else > >> 4) eclib renames its libec0 to something else > >> 5) both rename libec0 to something else, and possibly both Provides: > >> libec0 (if compatible) > > > > Just from the package description they seem to be completly unrelated > > libraries. > > > > In that case ecere-sdk should probably use a different name for that > package. > libecec?! since the .so file is already in /usr/lib/.*/ec/libec.so > > >> Also, we should decide above in context when/where we want to implement > >> this: wheezy and jessie. BTW Ubuntu already synced both packages, so the > >> clash is more evident there. > > > > Both packages are not in testing, so there is nothing to deal with for > > wheezy. > > > > Cool. > > Regards, > > Dmitrijs. >
