RC bug in libgnomeprint*, need to conflict/replace gnome-print
reopen 125283
reopen 135285
severity 125283 serious
severity 125285 serious
thanks
I made a current potato chroot and installed gnumeric on it with all of
it's dependencies, including gnome-print. I then changed sources list to
point to woody, updated, and did the following:
alpha:~# apt-get install gnumeric
...
Unpacking libgnomeprint-bin (from .../libgnomeprint-bin_0.35-1_i386.deb) ...
dpkg: error processing
/var/cache/apt/archives/libgnomeprint-bin_0.35-1_i386.deb (--unpack):
trying to overwrite `/usr/bin/gnome-font-install', which is also in
package gnome-print
...
Errors were encountered while processing:
/var/cache/apt/archives/libgnomeprint-bin_0.35-1_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
alpha:~# apt-get install gnumeric
...
Unpacking libgnomeprint-bin (from .../libgnomeprint-bin_0.35-1_i386.deb) ...
dpkg: error processing
/var/cache/apt/archives/libgnomeprint-bin_0.35-1_i386.deb (--unpack):
trying to overwrite `/usr/bin/gnome-font-install', which is also in
package gnome-print
...
Unpacking libgnomeprint-data (from .../libgnomeprint-data_0.35-1_all.deb) ...
dpkg: error processing
/var/cache/apt/archives/libgnomeprint-data_0.35-1_all.deb (--unpack):
trying to overwrite `/usr/share/fonts/afms/adobe/pagd8a.afm', which is
also in package gnome-print
...
etc, the upgrade runs fail.
Your assumptions are completely false - whilst this bug is not shown in
your simple test case, it happens during normal potato->woody upgrade
runs. It has happened to me twice, when I first reported it and when I
just reproduced it in a chroot. This is because there is nothing in the
package headers of libgnomeprint-data and libgnomeprint-bin to say that
they must be unpacked after gnome-print is removed, or to say that the
files in these packages are allowed to replace those in gnome-print.
This is a serious policy violation according to section 7.5,
particularly:
7.5.1: 'Firstly, as mentioned before, it is usually an error for a
package to contain files which are on the system in another package.'
and:
7.5.2: 'Secondly, Replaces allows the packaging system to resolve which
package should be removed when there is a conflict - see Conflicting
binary packages - Conflicts, Section 7.3. This usage only takes effect
when the two packages do conflict, so that the two usages of this field
do not interfere with each other.'
libgnomeprint-data and libgnomeprint-bin, and probably libgnomeprint15
should be made to *both* Conflict and Replace gnome-print, as is the
correct procedure when a package is split and wholly replaced by several
others.
This is a reproducible release critical bug affecting upgrades from
stable, and should not be closed or downgraded until fixed.
Regards,
Rob
Reply to: