Your message dated Thu, 22 May 2025 12:03:39 +0200
with message-id <382eb6e4-f2b3-4e14-a065-5dfdc483c...@debian.org>
and subject line Re: Bug#1106165: unblock: mlmmj/1.5.0-2
has caused the Debian Bug report #1106165,
regarding unblock: mlmmj/1.5.0-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 ow...@bugs.debian.org
immediately.)
--
1106165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1106165
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Subject: unblock: mlmmj-1.5.0-2
Package: release.debian.org
Severity: normal
User: release.debian....@packages.debian.org
Usertags: unblock
Please unblock package mlmmj
MLMMJ 1.5.0 fails to build on a number of architectures due to certain
post-compile tests timing out. I have added a workaround to the
debian/rules file to avoid the build tests for the architectures where
the build tests fail, to allow the build to succeed and continuing to
the the build tests for the architectures where the build tests work.
MLMMJ upstream was first forked and then slowly taken over by another
developer that was involved in the project and has now finally taken
over the upstream website.
In the proposed upload I have also included fixes to the
debian/copyright file to fix Lintian errors.
A debdiff is attached.
Thank you
--
Chris Knadle
chris.kna...@coredump.us
mlmmj-1.5.0-1_to_1.5.0-2.diff.xz
Description: application/xz
--- End Message ---
--- Begin Message ---
Hi,
On 21-05-2025 00:23, Chris Knadle wrote:
In
terms of "fixing the tests", I'm stuck.
I looked at the build results of reproducible builds, and there also the
amd64 build fails. I suspect that the build is sensitive to the load of
the host. (I suspect that the reported version in bug #1104274 is wrong,
I make that mistake regularly as I use reportbug on a testing host and
sometimes I forget to fix the version when filing bugs against the
version in unstable).
Anyways, it seems you "only" try to get a new upstream version into
testing, there are no important bugs closed by the version in unstable
as far as I can tell. Therefor, I decided to *not* unblock mlmmj and
we'll keep the current version in trixie. Please reopen this bug if you
have information that you think might change my mind (if so, we'd also
need a debdiff against the version in testing to judge).
Paul
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
