Hi,
> No, it's not. Unless the new package provides the same SONAME as
> libechonest2.1
> (which it does not), this is not "renaming a package".
>
> I was looking for some documentation, but I think the best think I can point
> you
> to is ยง8 of the policy. But in short: transitiong from the old
On 2015-12-09 22:47:04, Stefan Ahlers wrote:
> Hi,
>
> > You need to drop libechonest2.1 from the package. An empty libechonest2.1
> > depending on libechonest2.3 is wrong.
>
> libechonest2.1 is a transitional dummy package
> (https://wiki.debian.org/Renaming_a_Package). And so it should be corr
Hi,
> You need to drop libechonest2.1 from the package. An empty libechonest2.1
> depending on libechonest2.3 is wrong.
libechonest2.1 is a transitional dummy package
(https://wiki.debian.org/Renaming_a_Package). And so it should be correct that
this package is empty.
Regards,
Stefan Ahlers
Hi
On 2015-12-09 21:49:45, Stefan Ahlers wrote:
> libechonest2.3.1 provides libechonest.so.2.3 and so clementine has to be
> rebuild against libechonest2.3, after rebuilding, clementine will work
> correctly.
You need to drop libechonest2.1 from the package. An empty libechonest2.1
depending on l
Hi,
libechonest2.3.1 provides libechonest.so.2.3 and so clementine has to be
rebuild against libechonest2.3, after rebuilding, clementine will work
correctly.
Kind regards,
Stefan Ahlers
Package: libechonest2.1
Version: 2.3.1-0.1
Severity: grave
libechonest2.1 no longer provides libechonest.so.2.1 and breaks all its reverse
dependencies.
$ clementine
clementine: error while loading shared libraries: libechonest.so.2.1: cannot
open shared object file: No such file or directory
I
6 matches
Mail list logo
