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

Bug#1110207: marked as done (unblock: kmailtransport/24.12.3-2)

Your message dated Thu, 14 Aug 2025 13:52:43 +0200
with message-id <906e549b-f761-4c21-b196-54e704c4bee0@debian.org>
and subject line close all open unblock requests, the trixie release happened
has caused the Debian Bug report #1110207,
regarding unblock: kmailtransport/24.12.3-2
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.)


-- 
1110207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1110207
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: kmailtransport@packages.debian.org
Control: affects -1 + src:kmailtransport
User: release.debian.org@packages.debian.org
Usertags: unblock

Dear Release Team,

please unblock package kmailtransport.

[ Reason ]
It contains the following change:
* Remove the Breaks for libkf5mailtransport-data to allow mbox-
  importer to be upgraded (Closes: #1109519).

[ Impact ]
mbox-importer gets removed when running an apt full-upgrade from
bookworm to trixie.

[ Tests ]
- Install a minimal bookworm
- Install mbox-importer
- update sources.list to target trixie and run apt update
- run apt upgrade --without-new-pkgs
1. As is
   - run apt full-upgrade
   => notice apt takes long seconds to find a solution and wants to
   remove mbox-importer
2. With a patched Packages file
   - patch out the likmailtransport-data Breaks libkf5mailtransport-data
     relation in
     deb.debian.org_debian_dists_trixie_main_binary-amd64_Packages
   - run apt full-upgrade
   => notice apt finds a solution immediately and proposes an upgrade
   path that doesn’t remove mbox-importer.

[ Risks ]
No risk identified.
We keep the likmailtransport-data Replaces libkf5mailtransport-data
relation since both packages have files in common, and only remove the
Breaks relation that confuses apt in this case.

mbox-importer is a leaf package only useful in combination with kmail.
If it gets removed because the solution still doesn’t work, users can
easily reinstall it after upgrade.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing


Thanks !



diff -Nru kmailtransport-24.12.3/debian/changelog kmailtransport-24.12.3/debian/changelog
--- kmailtransport-24.12.3/debian/changelog	2025-03-29 18:49:09.000000000 +0100
+++ kmailtransport-24.12.3/debian/changelog	2025-07-31 17:08:12.000000000 +0200
@@ -1,3 +1,11 @@
+kmailtransport (24.12.3-2) unstable; urgency=medium
+
+  [ Patrick Franz ]
+  * Remove the Breaks for libkf5mailtransport-data to allow mbox-
+    importer to be upgraded (Closes: #1109519).
+
+ -- Patrick Franz <deltaone@debian.org>  Thu, 31 Jul 2025 17:08:12 +0200
+
 kmailtransport (24.12.3-1) unstable; urgency=medium
 
   [ Patrick Franz ]
diff -Nru kmailtransport-24.12.3/debian/control kmailtransport-24.12.3/debian/control
--- kmailtransport-24.12.3/debian/control	2025-03-29 10:21:51.000000000 +0100
+++ kmailtransport-24.12.3/debian/control	2025-07-31 17:06:20.000000000 +0200
@@ -41,7 +41,7 @@
 Architecture: all
 Multi-Arch: foreign
 Depends: ${misc:Depends},
-Breaks: libkf5mailtransport-data, libkf5mailtransport5 (<< 20.04.1-2~),
+Breaks: libkf5mailtransport5 (<< 20.04.1-2~),
 Replaces: libkf5mailtransport-data, libkf5mailtransport5 (<< 20.04.1-2~),
 Description: mail transport service library - data files
  Mailtransport is a library that provides the following functionality:



unblock kmailtransport/24.12.3-2

--- End Message ---
--- Begin Message --- 
Hi,
I'm sorry we couldn't unblock your request in time for trixie. I'm closing all open unblock requests in one go, so I'm not going into details of the particular request, but reasons are typically as follow: 
- the request came after the deadline of 2025-07-30
- the request came late and we just didn't have the time to deal with it
- the request was waiting for action from the submitter (moreinfo tag)
- the request didn't appear to be in line with the freeze policy and we
  didn't have the energy to engage (sorry for that, see our FAQ [1])
- there was discussion in the unblock request but no agreement was
  reached in time for the release.

Paul

[1] https://release.debian.org/trixie/FAQ.html

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature


--- End Message ---
Reply to: