[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#689813: libgraphite2-3: misses Breaks: libgraphite2-2.0.0



On Sat, Oct 06, 2012 at 06:05:41PM +0200, Rene Engelhard wrote:
> And libgraphite2-3 Provides: libgraphite-2.0.0, so a Breaks:/Conflicts: would
> need to be versioned, given the whole point of this symlink and the Provides: is
> to save a tansition for a library which didn't really change ABI/API (yet).
> 
> I am not sure if with a conflicts: it would seamlessly upgrade to libgraphite3-2
> even with packages still depending on libgraphite2-2.0.0....

I added a Breaks: libgraphite2-2.0.0 and get this:

rene@frodo:~/Debian/Pakete/graphite2$ sudo dpkg -i libgraphite2-3_1.2.0-2_amd64.deb
Selecting previously unselected package libgraphite2-3.
dpkg: regarding libgraphite2-3_1.2.0-2_amd64.deb containing libgraphite2-3:
 libgraphite2-3 breaks libgraphite2-2.0.0
  libgraphite2-2.0.0 (version 1.1.3-1) is present and installed.

dpkg: error processing libgraphite2-3_1.2.0-2_amd64.deb (--install):
 installing libgraphite2-3 would break libgraphite2-2.0.0, and
 deconfiguration is not permitted (--auto-deconfigure might help)

Errors were encountered while processing:
 libgraphite2-3_1.2.0-2_amd64.deb
rene@frodo:~/Debian/Pakete/graphite2$
rene@frodo:~/Debian/Pakete/graphite2$ sudo dpkg -i --auto-deconfigure libgraphite2-3_1.2.0-2_amd64.deb
dpkg: considering deconfiguration of libgraphite2-2.0.0, which would be broken by installation of libgraphite2-3 ...
dpkg: yes, will deconfigure libgraphite2-2.0.0 (broken by libgraphite2-3)
(Reading database ... 231908 files and directories currently installed.)
Unpacking libgraphite2-3 (from libgraphite2-3_1.2.0-2_amd64.deb) ...
De-configuring libgraphite2-2.0.0 ...
Replacing files in old package libgraphite2-2.0.0 ...
Setting up libgraphite2-3 (1.2.0-2) ...
dpkg: dependency problems prevent configuration of libgraphite2-2.0.0:
 libgraphite2-3 (1.2.0-2) breaks libgraphite2-2.0.0 and is installed.

dpkg: error processing libgraphite2-2.0.0 (--install):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 libgraphite2-2.0.0

And with Breaks: libgraphite2-2.0.0 (<< 1.2.0):

rene@frodo:~/Debian/Pakete/graphite2$ sudo dpkg -i libgraphite2-3_1.2.0-2_amd64.deb
Selecting previously unselected package libgraphite2-3.
dpkg: regarding libgraphite2-3_1.2.0-2_amd64.deb containing libgraphite2-3:
 libgraphite2-3 breaks libgraphite2-2.0.0 (<< 1.2.0)
  libgraphite2-2.0.0 (version 1.1.3-1) is present and installed.

dpkg: error processing libgraphite2-3_1.2.0-2_amd64.deb (--install):
 installing libgraphite2-3 would break libgraphite2-2.0.0, and
 deconfiguration is not permitted (--auto-deconfigure might help)
Errors were encountered while processing:
 libgraphite2-3_1.2.0-2_amd64.deb
rene@frodo:~/Debian/Pakete/graphite2$
rene@frodo:~/Debian/Pakete/graphite2$ sudo dpkg -i --auto-deconfigure libgraphite2-3_1.2.0-2_amd64.deb
dpkg: considering deconfiguration of libgraphite2-2.0.0, which would be broken by installation of libgraphite2-3 ...
dpkg: yes, will deconfigure libgraphite2-2.0.0 (broken by libgraphite2-3)
(Reading database ... 231908 files and directories currently installed.)
Unpacking libgraphite2-3 (from libgraphite2-3_1.2.0-2_amd64.deb) ...
De-configuring libgraphite2-2.0.0 ...
Replacing files in old package libgraphite2-2.0.0 ...
Setting up libgraphite2-3 (1.2.0-2) ...
dpkg: dependency problems prevent configuration of libgraphite2-2.0.0:
 libgraphite2-3 (1.2.0-2) breaks libgraphite2-2.0.0 (<< 1.2.0) and is installed.
  Version of libgraphite2-2.0.0 to be configured is 1.1.3-1.

dpkg: error processing libgraphite2-2.0.0 (--install):
 dependency problems - leaving unconfigured

Errors were encountered while processing:
 libgraphite2-2.0.0

-> boom.

Defeats the purpose of this Replaces: to prevent a useless transition (and blocking
other transitions), as you can then just must rebuild everything anyway.

I do not intend to fix this "bug" as there is no bug, just a mis-reading of policy
and not-knowing common practice since ages. Not everything is to be kicked on the
head by piuparts warnings - there's valid cases there.

Regards,
 
Rene


Reply to: