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

Bug#1115860: marked as done (trixie-pu: package mailfromd/9.0-1+deb13u1)

Your message dated Sat, 15 Nov 2025 11:21:45 +0000
with message-id <736c7150dc08501cc89945035c406eaf9688e144.camel@adam-barratt.org.uk>
and subject line Closing requests for updates included in 13.2
has caused the Debian Bug report #1115860,
regarding trixie-pu: package mailfromd/9.0-1+deb13u1
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.)


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

Bug #1115720 reports, that the amd64 binary of mailfromd 9.0-1+b1
always fails on startup with the message
/usr/sbin/mailfromd: symbol lookup error: /usr/sbin/mailfromd:
undefined symbol: mu_debug_level_p

I have to confirm this issue.
Re-building the package on a trixie (or even sid) environment results
in a working binary.

I suspect, that this is an issue with either with the time_t64
bin-nmu or with an update of mailutils which sadly didn't trigger an
autotest problem with the bin-nmu version mailfromd.

A simple re-build of the package solves this issue, so I suggest to
build 9.0-1+deb13u1 with no changes for the trixie 13.2 point release.

[ Reason ]
As #1115720 mentions this package is currently completely unusable.

[ Impact ]
The package keeps being completely unusable.

[ Tests ]
I built the package (9.0-1+deb13u1) in my trixie pbuilder.
Then I entered this (clean) trixie chroot and first installed 9.0-1+b1
and run mailfromd, which resulted in the undefined symbol error
mentioned above.

After this I installed 9.0-1+deb13u1 build of the package, which runs
without any issues.

I also run autopkgtest on 9.0-1+b1, which runs the testsuite with the
mailfromd 9.0-1+b1 binary, which fails on nearly all tests.
Then I run the same autopkgtest on 9.0-1+deb13u1, which succeeds on
all tests.

[ Risks ]
None (from my point of view).

[ 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 (old)stable
  [x] the issue is verified as fixed in unstable (just uploaded 9.0-2,
      this package runs autopkgtest without problems)

[ Changes ]
No changes...

[ Other info ]

Greetings
Roland

diff --git a/debian/changelog b/debian/changelog
index 870e0de..1bdc1ea 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+mailfromd (9.0-1+deb13u1) trixie; urgency=medium
+
+  * Rebuild because of mailutils incompatibility (Closes: #1115720).
+
+ -- Roland Rosenfeld <roland@debian.org>  Sat, 20 Sep 2025 18:57:33 +0200
+
 mailfromd (9.0-1) unstable; urgency=medium
 
   * New upstream release 9.0 (this removes support for old .mf file
diff --git a/debian/salsa-ci.yml b/debian/salsa-ci.yml
index 6b698a8..e31023e 100644
--- a/debian/salsa-ci.yml
+++ b/debian/salsa-ci.yml
@@ -4,5 +4,5 @@ include:
   - https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/pipeline-jobs.yml
 
 variables:
-  RELEASE: 'unstable'
+  RELEASE: 'trixie'
   SALSA_CI_DISABLE_CROSSBUILD_ARM64: 1

--- End Message ---
--- Begin Message --- 
Package: release.debian.org
Version: 13.2

Hi,

The updates referenced in each of these bugs were included in today's
13.2 trixie point release.

Regards,

Adam

--- End Message ---
Reply to: