Your message dated Mon, 05 Aug 2024 07:23:50 +0000
with message-id <e1sas4m-000rhi...@fasolo.debian.org>
and subject line Bug#1077960: fixed in xmedcon 0.24.0-gtk3+dfsg-2
has caused the Debian Bug report #1077960,
regarding xmedcon: missing Breaks+Replaces: medcon (<< 0.24)
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.)
--
1077960: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077960
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xmedcon
Version: 0.24.0-gtk3+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts fileconflict
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'bookworm'.
It installed fine in 'bookworm', then the upgrade to 'trixie' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.
See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces
>From the attached log (scroll to the bottom...):
Preparing to unpack .../xmedcon_0.24.0-gtk3+dfsg-1_amd64.deb ...
Unpacking xmedcon (0.24.0-gtk3+dfsg-1) ...
dpkg: error processing archive
/var/cache/apt/archives/xmedcon_0.24.0-gtk3+dfsg-1_amd64.deb (--unpack):
trying to overwrite '/usr/share/applications/xmedcon.desktop', which is also
in package medcon 0.23.0-gtk3+dfsg-1
Errors were encountered while processing:
/var/cache/apt/archives/xmedcon_0.24.0-gtk3+dfsg-1_amd64.deb
cheers,
Andreas
medcon=0.23.0-gtk3+dfsg-1_xmedcon=0.24.0-gtk3+dfsg-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: xmedcon
Source-Version: 0.24.0-gtk3+dfsg-2
Done: Étienne Mollier <emoll...@debian.org>
We believe that the bug you reported is fixed in the latest version of
xmedcon, 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 1077...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Étienne Mollier <emoll...@debian.org> (supplier of updated xmedcon 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: Mon, 05 Aug 2024 08:45:57 +0200
Source: xmedcon
Architecture: source
Version: 0.24.0-gtk3+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team
<debian-med-packag...@lists.alioth.debian.org>
Changed-By: Étienne Mollier <emoll...@debian.org>
Closes: 1077960
Changes:
xmedcon (0.24.0-gtk3+dfsg-2) unstable; urgency=medium
.
* Team upload.
* d/control: xmedcon Breaks+Replaces medcon (<< 0.24)
Thanks to Andreas Beckmann (Closes: #1077960)
* d/libmdc3t64.lintian-overrides: match any version in libmdc3 conflict.
Checksums-Sha1:
84d6a108c0033d8cab3f299f2d44a67749c9a1f6 2448 xmedcon_0.24.0-gtk3+dfsg-2.dsc
3498f92f12346fc27c82a3da2aac7e094440ce13 13416
xmedcon_0.24.0-gtk3+dfsg-2.debian.tar.xz
Checksums-Sha256:
9defa8e334d87360cc34106b18b30dfc3d6a6ed6afb150ef60f87bc2c518c134 2448
xmedcon_0.24.0-gtk3+dfsg-2.dsc
f42223a53681c48a16bc21bf55e7963aab77c303a6b95149d639f24e54efdbf0 13416
xmedcon_0.24.0-gtk3+dfsg-2.debian.tar.xz
Files:
69238400bf53f578f2f75ec019cfafe8 2448 graphics optional
xmedcon_0.24.0-gtk3+dfsg-2.dsc
9f0632f391a99ae9a0dad26deac9e41c 13416 graphics optional
xmedcon_0.24.0-gtk3+dfsg-2.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQJIBAEBCgAyFiEEj5GyJ8fW8rGUjII2eTz2fo8NEdoFAmaweQsUHGVtb2xsaWVy
QGRlYmlhbi5vcmcACgkQeTz2fo8NEdqX+g//a41hWHipNEORX16FzBioj8CPKWQx
nclSZVSOWZ4l6oTKcEEUng5YS6fWJseiZKx+E+/b8VJLDmpZepSkaaPMYQ8zQME8
EXmTaAuO9tgGD4G2nBZjfllOzXp9h9EWu0bs+Z0/q8Bc3g6gVhZLdv52gIGJKtW/
YJEWV+6m+2hIWo9FpvDuKnKuHok1X/kLoQtT8wpE7xoQe6yhxNGBKb51VgTh5+PA
3grBkd62I9mxYZYYQP9lpMGswPvRyhRA8Xx9LSP3gRP6f0uFKSy61SKYltDTveky
cpTAZoCBJszCUQcVZ37XyOJZVjc0IpRaXKl9ugu/wgnHhg+xoUZJ3fHWVw6qdw4e
kTE6G4GNtlxBC/muLOysfBB+mDbcq49mHTWL6pv4iFUtRoi54ocvA5bnlXq4ruzy
7VNDZyp1twkZ/9dJH3kRGVuf6+RK3YSE74AGLN/sZF8Kk3usmv47jFf2ycNdBbiz
TEY0bvSY1ASOEwSQu59SrwUH8tblM+s/AC/lNPWlftJ6aDrZqxBWpKgBblNqKaNl
UUubwCRZq9aeSkPh/7r4xTQotNFrdne34EQd9xe0rmgar+SaXoUMGgGzaf68FJEG
Q7IaNjWtpeQla0d8ojzV9IWn5ttBMKOGCYCjhi2YYARppz+9PVTgYiviPHIAD9Hb
2r5e1x0aQqowp7s=
=HJ/z
-----END PGP SIGNATURE-----
pgpi1Y_YOoZNO.pgp
Description: PGP signature
--- End Message ---
