Your message dated Mon, 18 Aug 2025 17:23:29 +0000 with message-id <E1uo3Zx-00GLcB-0W@fasolo.debian.org> and subject line Bug#1111463: fixed in tkrev 9.6.1-3 has caused the Debian Bug report #1111463, regarding tkrev has an undeclared file conflict on /usr/share/pixmaps/tkcvs.xpm 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 owner@bugs.debian.org immediately.) -- 1111463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1111463 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: tkrev has an undeclared file conflict on /usr/share/pixmaps/tkcvs.xpm
- From: Helmut Grohne <helmut@subdivi.de>
- Date: Mon, 18 Aug 2025 11:29:55 +0200
- Message-id: <[🔎] 20250818092955.GA3645701@subdivi.de>
Package: tkrev Version: 9.6.1-2 Severity: serious User: debian-qa@lists.debian.org Usertags: fileconflict Control: affects -1 + tkcvs tkrev has an undeclared file conflict. This may result in an unpack error from dpkg. The file /usr/share/pixmaps/tkcvs.xpm is contained in the packages * tkcvs/8.2.3-6 as present in forky|trixie * tkrev/9.6.1-2 as present in unstable These packages can be unpacked concurrently, because there is no relevant Replaces or Conflicts relation. Attempting to unpack these packages concurrently results in an unpack error from dpkg, because none of the packages installs a diversion for the affected file. Kind regards Helmut
--- End Message ---
--- Begin Message ---
- To: 1111463-close@bugs.debian.org
- Subject: Bug#1111463: fixed in tkrev 9.6.1-3
- From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>
- Date: Mon, 18 Aug 2025 17:23:29 +0000
- Message-id: <E1uo3Zx-00GLcB-0W@fasolo.debian.org>
- Reply-to: Andreas Metzler <ametzler@debian.org>
Source: tkrev Source-Version: 9.6.1-3 Done: Andreas Metzler <ametzler@debian.org> We believe that the bug you reported is fixed in the latest version of tkrev, 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 1111463@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Metzler <ametzler@debian.org> (supplier of updated tkrev 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 ftpmaster@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Mon, 18 Aug 2025 19:02:34 +0200 Source: tkrev Architecture: source Version: 9.6.1-3 Distribution: unstable Urgency: medium Maintainer: Debian QA Group <packages@qa.debian.org> Changed-By: Andreas Metzler <ametzler@debian.org> Closes: 1111463 Changes: tkrev (9.6.1-3) unstable; urgency=medium . * QA upload. * Add missing break/replaces on tkcvs to tkrev. Closes: #1111463 Checksums-Sha1: 4ea0f0ed969656023de71c9cddd17d8898ab4b44 1888 tkrev_9.6.1-3.dsc 9de932685117807ce9d13cdfc0ee5e5c1eda6eeb 10488 tkrev_9.6.1-3.debian.tar.xz Checksums-Sha256: 502d731beb1caf3c8b3993ec7ebdf4f3cdb5ce1b01b43e77e4a6aa18221d8a31 1888 tkrev_9.6.1-3.dsc d3c55a0e7dd80a1cb4b9b4020f725014468b6376ecb3cd559b7cb99043089852 10488 tkrev_9.6.1-3.debian.tar.xz Files: 86fc03d88ff8571e89914828288e3ece 1888 vcs optional tkrev_9.6.1-3.dsc 28a553d423cdb2ac3feb31f66bb7b044 10488 vcs optional tkrev_9.6.1-3.debian.tar.xz -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEE0uCSA5741Jbt9PpepU8BhUOCFIQFAmijXYIACgkQpU8BhUOC FITC1w//UWwBLeZKZB7lA6t0/RHESf0/nrC0L5Mr8uX4wl5Otd39mp8Br4oVid29 Jx8ub6s1ePT4eoqsz0+iT7j1sHFUzi4J3y91kyEx7uopr2Fxd0ryvWepq8QWOmH2 4ozQXMI2FYvr9ky2Dv6zUsyp//KSHLPKwv6PhAWpAqhG3tKuuQ8d7OblSD2VqxVX fhnrqGi+4fgTBK0ItR2GbL8wa4vzejp1EOx4q8Gq9lpCvuXQhi1qOXSF5rWeBwbx IrTx7JEeDGHSOXwBtSOSYZfldR/u8IyLosTYWhAYpypeS9jCJz+dFM6nyuwQcVh5 Jgzf3fWLtm88P/4GBzp7xFzjImSAdn7b7YytkNg5lpwTI/m8X5G0evLXABkGLw7Z cAeOiMVKUSMzSspSGoiGTibZXRfWN6YRoyBhBQ5TetUyEYuCIEwc+YX8WeM+Idut Bc2hXgE/svqF9TlCZVVaJQBJuZkzw+2iiMhbJtBSqjM0Tesjxn5lt8tHKVWP2n+0 jeo/lbjUmcEUj+IxEgdP5ssZvXPZYb7c+o9bgP8cPdiRsUVc59HGYjIMk/KvnFU4 E74CqCBsGvYaXlBT3ijp2MmgUe1NA0wcK5uBLDIeELgCR3HEEtAnbLj1+akOqMV5 lCWnSQOA0eoHgTfhFQmlrMWjnEcvJ+0iNXX008CRTKFIoyw769g= =NMTB -----END PGP SIGNATURE-----Attachment: pgpqQlj7VMZ1O.pgp
Description: PGP signature
--- End Message ---