Your message dated Sun, 08 Jun 2025 04:04:16 +0000
with message-id <e1uo7ga-003v7d...@fasolo.debian.org>
and subject line Bug#1103308: fixed in mlmmj 1.5.2-1
has caused the Debian Bug report #1103308,
regarding mlmmj: build failures on non-mainstream arches
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.)
--
1103308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1103308
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mlmmj
Version: 1.5.0-1
X-Debbugs-CC: Chris Knadle <chris.kna...@coredump.us>, Michael Jeanson
<mjean...@debian.org>, Thomas Goirand <z...@debian.org>, d...@darkboxed.org
Hi Chris,
I'm moving this to the BTS for visibility.
On Wed, Apr 16, 2025 at 12:03:42AM -0400, Chris Knadle wrote:
> On further looking at Michael's Git repository and saw how the Debian build
> goes through an upstream test suite, I decided to incorporate the work that
> was done into an MLMMJ 1.5.0 package, and I uploaded that to Debian this
> evening before the Trixie build freeze.
Thank you! I was meaning to but lost track of it. Did you figure out the
necessary exim config change to fix the new tainting logic too? I have
something locally I've been meaning to post about.
((I already have to go plead with release team over dovecot-fts-flatcurve
no need for yet another package to do that for ;-))
> At the moment I don't have a good way of doing a build on the array of
> Debian release architectures, so I didn't test that before the
> upload.
That's fine. This is how many DDs seem to work. You can use porterboxes for
this but honestly it's too much of a hassle for pre-upload testing. Many
use experimental so as to not disrupt unstable users.
Often perfect is the enemy of good enough anyway. Especially with a freeze
looming. I find often as soon as there's activity other people might jump
in to help, so it's really vital to Debian functioning well to just do
*something* even if it's (still) broken.
Think of it this way: nothing attracts motivated nerds quite like hard
problems to solve. As maintainers we should endeavor to create as many
visible and well understood problems as possible :D.
Which is what I tried to do months ago as you'll recall.
Remember: reverting to an old upload (using +really) is always possible.
> Unfortunately there are a bunch of Debian release architectures that the
> build fails for, and I'm hoping to get hints as to how to fix that in the
> next month before the hard freeze so that MLMMJ 1.5.0 can make it to the
> Trixie release.
While not the first thing we should try, process wise you can also declare
architectures mlmmj doesn't build on as unsupported by asking ftp-master to
RM them from the archive.
Then the working binaries will migrate just fine. A less than ideal
solution, but it's a decision you ultimately get to make as Maintainer.
--Daniel
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: mlmmj
Source-Version: 1.5.2-1
Done: Christopher Knadle <chris.kna...@coredump.us>
We believe that the bug you reported is fixed in the latest version of
mlmmj, 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 1103...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Christopher Knadle <chris.kna...@coredump.us> (supplier of updated mlmmj
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, 07 Jun 2025 23:42:07 -0400
Source: mlmmj
Architecture: source
Version: 1.5.2-1
Distribution: unstable
Urgency: medium
Maintainer: Christopher Knadle <chris.kna...@coredump.us>
Changed-By: Christopher Knadle <chris.kna...@coredump.us>
Closes: 1103308 1104274 1106691
Changes:
mlmmj (1.5.2-1) unstable; urgency=medium
.
* Newer upstream version, fixes outdated PHP for mlmmj-php-web-admin
(Closes: #1106691)
* debian/patches: add 08_fix-ftbfs-diff to fix FTBFS bug. This patch brings
the 1.5.0 tarball up to upstream version 1.5.2
(Closes: #1103308, #1104274)
Checksums-Sha1:
299c8aebb23bc16ccfdaa0efaea9f2621e30a04e 2125 mlmmj_1.5.2-1.dsc
15b87d061891c90891b46a0855bad91768d6d46e 278204 mlmmj_1.5.2.orig.tar.xz
e4d51ea4c5ae73ab8dc3a492c3ae127cfbdc72b3 28272 mlmmj_1.5.2-1.debian.tar.xz
fb250378c64aa29361f0e4577de28ecf564d7948 5998 mlmmj_1.5.2-1_source.buildinfo
Checksums-Sha256:
6cf665084d75c7ef539ac61c440cb566f5bd9e7747187750d8300751142c0e49 2125
mlmmj_1.5.2-1.dsc
de0be6c2910ac8bf8291dc86a3819a08b7cdb1019c54ede1791e166967bf1baa 278204
mlmmj_1.5.2.orig.tar.xz
57578396cf6fbd6edf53b258a27d5933e85af16e2c3a5d262163e1ecb85edece 28272
mlmmj_1.5.2-1.debian.tar.xz
b3a532419102981b39a57efee551823147fbef728bdd0dabc3aa20d1a65acfda 5998
mlmmj_1.5.2-1_source.buildinfo
Files:
4ce4e83d336569e6c3475a5ffc0c22f2 2125 mail optional mlmmj_1.5.2-1.dsc
d2f3850755f16222745bb1e7264a0ded 278204 mail optional mlmmj_1.5.2.orig.tar.xz
fcb5724ab8beb4e00ac0de40392c0917 28272 mail optional
mlmmj_1.5.2-1.debian.tar.xz
840d4734c647e9a417ae79f7c690533d 5998 mail optional
mlmmj_1.5.2-1_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEe1KzyGmRW/4DhtV6ieLKD9m6RHAFAmhFBuEACgkQieLKD9m6
RHC0iQ//fSAhEidwDlX/T9RrMzeQsDjNkLGy5JuWgJH4Sl9ciAfEDEdbSZ7YXekd
EzqfpBap5poPsShCURnIuqHaedZbM0MKK0YJb8jrbNggrA8FhDcn2UkOEYGoQfI8
g0Z4S95dCC/usUBU5wZAXOD0hoG55d4jKwYHqlW5FcZHtjfNnRkcRKrj06/e9k4G
mjriwQ4A+bV3RSgjlpSzf6/6Jla4O9KlRgVgjaLb+hR38e5KyljHToF/Y3NiLY4H
H8NZ9aAqqNRcsGmH7lLwflqXogOzWZnK080gOmKnQOTl/BD69mOpJ4ud7VBft3C9
AaW0zRiqIHC8L3YI4bgWyeTJRCI1D7cKVg5P1x+i2G1beCgEPsX9Eswt+S5Cvbv9
ZHeGBQKGIAyBkTQt73H05CuQYCEeKDbWWJaDXwhtZS//uPReck6FWLiKQDHDuAG3
28AveYEGNI8HK1g7RY5FUvwPq4sVFfxHoVhUs/pDjFUmcSxnbgerm1cdhzLnODX9
t884rw5Xx9yHaUSNL1BQ2776pzWBMSA5PbKYh5AcoczTq1C2ZGHd2R9AZEVvtkLG
ysv5i7yPlsbHmPDpzWUGHpDn+g7QpGYN/I7GqctZlWpKaE8c1BxmqNihZxK8KUun
d2/Qf3aGHykLUMUgyUiPITkC80GC2G7BjwpQptZQne1yxaJ9ZzQ=
=34CS
-----END PGP SIGNATURE-----
pgpedg3C1R4Q1.pgp
Description: PGP signature
--- End Message ---
