Your message dated Tue, 16 May 2023 17:03:46 +0000
with message-id <e1pyy5s-00d66o...@fasolo.debian.org>
and subject line Bug#1034959: fixed in libwmf 0.2.12-5.1
has caused the Debian Bug report #1034959,
regarding libwmf-0.2-7-gtk: missing Breaks+Replaces for libwmf0.2-7-gtk when 
upgrading from bullseye
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1034959: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034959
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libwmf-0.2-7-gtk
Version: 0.2.12-5
Severity: serious
Justification: dpkg unpack error

Attempting to unpack libwmf-0.2-7-gtk/0.2.12-5 from Debian bookworm
on a minimal Debian bullseye with libwmf0.2-7-gtk/0.2.8.4-17
installed, causes an unpack error from dpkg due to
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/io-wmf.so being 
contained in both packages.

| Selecting previously unselected package libwmf-0.2-7-gtk.
| (Reading database ... 5413 files and directories currently installed.)
| Preparing to unpack .../libwmf-0.2-7-gtk_0.2.12-5_amd64.deb ...
| Unpacking libwmf-0.2-7-gtk (0.2.12-5) ...
| dpkg: error processing archive ./libwmf-0.2-7-gtk_0.2.12-5_amd64.deb 
(--unpack):
|  trying to overwrite 
'/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/io-wmf.so', which is 
also in package libwmf0.2-7-gtk 0.2.8.4-17
| Processing triggers for libgdk-pixbuf-2.0-0:amd64 (2.42.2+dfsg-1+deb11u1) ...
| Errors were encountered while processing:
|  ./libwmf-0.2-7-gtk_0.2.12-5_amd64.deb


Please ensure that libwmf-0.2-7-gtk has sufficient Breaks and Replaces 
declarations.

Helmut

--- End Message ---
--- Begin Message ---
Source: libwmf
Source-Version: 0.2.12-5.1
Done: Andreas Metzler <ametz...@debian.org>

We believe that the bug you reported is fixed in the latest version of
libwmf, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1034...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Metzler <ametz...@debian.org> (supplier of updated libwmf package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Sat, 06 May 2023 18:19:26 +0200
Source: libwmf
Architecture: source
Version: 0.2.12-5.1
Distribution: unstable
Urgency: medium
Maintainer: Yangfl <mmyan...@gmail.com>
Changed-By: Andreas Metzler <ametz...@debian.org>
Closes: 1034959
Changes:
 libwmf (0.2.12-5.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add missing Breaks/Replaces on libwmf0.2-7-gtk to libwmf-0.2-7-gtk.
     Closes: #1034959
Checksums-Sha1: 
 9b976dd025c08c7ddabd751032825687048e76cf 2533 libwmf_0.2.12-5.1.dsc
 dbc9aac1433f5236c9e52b918ecca760e6c96f25 26112 libwmf_0.2.12-5.1.debian.tar.xz
Checksums-Sha256: 
 00d1c77e1a97ac04a962fd167b88e905b7b1ae590a0b3b6634c8fce24f4a52a1 2533 
libwmf_0.2.12-5.1.dsc
 2d3ae3bc9b9b24b7a78d2c5fa5c0f06380f7864e15aa44d02a2f3ce0ed951bd5 26112 
libwmf_0.2.12-5.1.debian.tar.xz
Files: 
 4067d74856d582e6f042a081a2576df0 2533 libs optional libwmf_0.2.12-5.1.dsc
 4d5f0c250efafdeb134b23906c6f8797 26112 libs optional 
libwmf_0.2.12-5.1.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE0uCSA5741Jbt9PpepU8BhUOCFIQFAmRWfxAACgkQpU8BhUOC
FIQKUQ/9FnoXegsKlBEWuqWdbV7JNiMVwrKdMrUvGGb96zwKreKtWu/lsIh27Qps
Slt0ShuaeCphguxBaDQcctVRKVgXr9Y2+nbtcg90j63KwvvTDNEYPwP9se+97+GP
CsZ4spn5HBbT0R6ZUmntChOHGe9X/m3/R171A1B8mI4vXutWL373HdL1NFhcrrzF
/ZEzgTXnnpoaA0Yy1xsa3FgmAGhBQ1+mPiY9bo9xCoDKEs78JgF/Cyuvx1AzjjBO
Vsrc7mFi8BOLXIfcQeiOXre0tGtyvmntXB5vbwus4Yux20DPbLcj+QYs1o1dssyG
4MWGbj3lAb3rAvKkmActhZ6HU4vbbYfsp3CCBnMNecVJSKmorzqgtATjJoTgEE/Q
ym7CQmxwbhotyXarC87Ju7V6QfCwodbfxbD+1Ji+KO926ILVfkrcvo+2qM2CIr/d
FRk5GYbdHYX56ot8ZggLJxF4Q/ANMW+vFpaUxXnl32B+tru/fzWk4hKJdUKE2SGo
B+AjvWvjyC4ukVnE0tfaHasRaXdrEFlIkYtpzjISf/eTT8s0aCsGxqrzZigWoy2L
3wbiEfLPdxz0ijQ0xBihfCE5/cB2AJvG+T3fcLU2I7E8Q+naMMjI+KLuoEzQYzCT
B080CT7ScnE1wexWIwTaPNIcC7VsFgP/EhvmSPs0kWgAq+V9xJs=
=yOJ1
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to