Your message dated Wed, 24 Sep 2025 20:39:35 +0000
with message-id <[email protected]>
and subject line Bug#1115273: fixed in meli 0.8.12+dfsg-3
has caused the Debian Bug report #1115273,
regarding meli: upcoming update of notify to v8
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 [email protected]
immediately.)
--
1115273: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1115273
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: meli
Version: 0.8.12+dfsg-2
Severity: normal
Tags: patch
X-Debbugs-Cc: [email protected]
Hi Jonas,
In the near future we will update notify to v8, which has been in experimental
for some time. src:meli builds with it using the trivial patch in attachment.
Cheers!
P.S.: For a while I've been using a convention where I name patches 1xxx if
they are updates, since they may be useful to upstream, even if trivial. Could
you please tell me if this is correct, or if you'd rather have them named 2xxx?
notify.patch
Description: application/mbox
--- End Message ---
--- Begin Message ---
Source: meli
Source-Version: 0.8.12+dfsg-3
Done: Jonas Smedegaard <[email protected]>
We believe that the bug you reported is fixed in the latest version of
meli, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jonas Smedegaard <[email protected]> (supplier of updated meli 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 [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Wed, 24 Sep 2025 22:15:36 +0200
Source: meli
Architecture: source
Version: 0.8.12+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard <[email protected]>
Changed-By: Jonas Smedegaard <[email protected]>
Closes: 1115273
Changes:
meli (0.8.12+dfsg-3) unstable; urgency=medium
.
* add patch 1001_assert_cmd
to accept newer revisions of crate assert_cmd,
replacing patch 2001_assert_cmd
* update DEP-3 patch headers
* relax build-dependency for crate linkify
* add patch 1001_notify
to accept newer major versions of crate notify;
bump build-dependency for crate notify;
closes: bug#1115273, thanks to NoisyCoil
* add patch cherry-picked upstream
to use 127.0.0.1 in tests (not 0.0.0.0)
Checksums-Sha1:
adf61b92a539fee463644eb117235c9fe91d48d7 4230 meli_0.8.12+dfsg-3.dsc
2cd7d1bf435d4a432a78b1015a3def907b3a5cfd 17440 meli_0.8.12+dfsg-3.debian.tar.xz
c599ba0ccf2f1971f04bfabcb5a5b581cae7dba2 28444
meli_0.8.12+dfsg-3_amd64.buildinfo
Checksums-Sha256:
beb7bd27ea4bb24d23c1f5265a117d00064132bdd6c298c203013a1e10c106e5 4230
meli_0.8.12+dfsg-3.dsc
8e7c724944f0d654e5e37a19aa8873da6107e90e23e0655874c9e67b25a2177b 17440
meli_0.8.12+dfsg-3.debian.tar.xz
3d01f19425771ade2f101e8a700979ac850626109d82c15c440dd9e8c22d211c 28444
meli_0.8.12+dfsg-3_amd64.buildinfo
Files:
82bd7e1fb2f8deaae0aa36db2cc0bfb5 4230 mail optional meli_0.8.12+dfsg-3.dsc
59e6b403ccce36197b2545e0d1b404dd 17440 mail optional
meli_0.8.12+dfsg-3.debian.tar.xz
b9e9894ebb31a48954c74c3d572b9f32 28444 mail optional
meli_0.8.12+dfsg-3_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
wsG7BAEBCgBvBYJo1FJ2CRAsfDFGwaABIUcUAAAAAAAeACBzYWx0QG5vdGF0aW9u
cy5zZXF1b2lhLXBncC5vcmebGA21+kF9jMrSKaRa9EAUcuyCaHy8t990jVawIOcI
bBYhBJ/j6cNmkaaf9TzGhCx8MUbBoAEhAAAAiRAArhdx/y95Ioe6EB23GBXQmm0E
yGi+hzlJQtU/os5BUOMfSTP4Zr7tSObT7UrVA+l+uHJasTJ5MPduHnazPtSvXCGm
BTtBhqf2JQIubluyjn+laPwmSD9iF1SQlaWjnhsidTbgk0GaG+PkumvnqgudYtd9
1VZIrfG01+TiA1F41dJnlI6CFpn72jPXrpKtM3pk3IJPT01sAGsC26T6diuhEfQC
ZnBkd8ITbp4AyKSbf2wb/k0tmJdT8h+9MouRnSKne2a43hDbYuZ1mR8HHd2Mp83m
FK4M2dw1QAw56RHvMWi//4CbRLnPL8kyoURAdH2FW2K4gtw/UIMbt2c85SGcg3um
HAIz7oWCYRp0Wpm3jdVxVjGAA47MoTvfWGHFZrAB1fgzE2B4/ZDCekRdbuYQ1Qh4
p+LZ0VMkLcbkUdEOnH+2He4RVIywDQ7HJusTSvqadzd3VTg6s8Y5rcZiGRwPqV2G
eyaRQighBI+83KrfANf0i96OCVugvClgsRM8din1FbcdL6lEscShy9PT4Tvcx9Rj
NNnAbGltAauN4EbMkwyRCyIULjV0xVFf7gHLks5lJub3l/UznsJzSmKa8M7Kha++
7OLUhHlId+zFq6yUFamGyIxc3N42zEzNnFhWGLzKemsdhTUN20veo4Tb9Xp32+BP
znW8auze4mf0N78qgV0=
=sL8S
-----END PGP SIGNATURE-----
pgph1N1qZUonb.pgp
Description: PGP signature
--- End Message ---
