Your message dated Tue, 01 Sep 2026 06:48:51 +0000
with message-id <[email protected]>
and subject line Bug#1127646: fixed in upx-ucl 4.2.4-2
has caused the Debian Bug report #1127646,
regarding ITS: upx-ucl
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.)


-- 
1127646: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1127646
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: upx-ucl
Version: 4.2.4-1.1
Severity: important
X-Debbugs-Cc: [email protected]

Hi,

I'm interested in salvaging your package upx-ucl, in accordance with
the Package Salvaging procedure outlined in the Developers Reference[1].
Your package meets the criteria for this process, and I would love to
assist in preserving and maintaining it. As the Salvage process
suggests, here is a list of the criteria that apply, in my opinion:

  - NMU
  - Bugs filed against the package do not have answers from the
    maintainer.
  - Upstream has released several versions.
  - There are QA issues with the package.

I’d be happy to help ensure this package continues to be well
maintained.

If you’re comfortable with the ITS, I can take over maintenance myself.
If not, I’m still happy to assist however I can.
--
Thanks
Polkorny

[1] 
https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#package-salvaging

--- End Message ---
--- Begin Message ---
Source: upx-ucl
Source-Version: 4.2.4-2
Done: Bastian Germann <[email protected]>

We believe that the bug you reported is fixed in the latest version of
upx-ucl, 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.
Bastian Germann <[email protected]> (supplier of updated upx-ucl 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: Tue, 01 Sep 2026 08:26:44 +0200
Source: upx-ucl
Architecture: source
Version: 4.2.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Commons <[email protected]>
Changed-By: Bastian Germann <[email protected]>
Closes: 1127646
Changes:
 upx-ucl (4.2.4-2) unstable; urgency=medium
 .
   * Devendor doctest, ucl, and zlib.
   * Salvage the package. (Closes: #1127646)
   * Disable valgrind.
Checksums-Sha1:
 b0f1925f264633049df7edacd7fd009e4a9b6805 1806 upx-ucl_4.2.4-2.dsc
 e346567abcccdf27622fb413872ab838afe8f38b 70048 upx-ucl_4.2.4-2.debian.tar.xz
 b278280e7d546de6e7e884a2a94427dafc623025 6523 upx-ucl_4.2.4-2_source.buildinfo
Checksums-Sha256:
 00ed3407011ccffb9eef5e46c879a69942930f52352899f122399c0c28924012 1806 
upx-ucl_4.2.4-2.dsc
 3480a4b5594b11c899102edcb32474d96e2eb9d8904efb4ed1e0bd98de55a6f4 70048 
upx-ucl_4.2.4-2.debian.tar.xz
 b72ad675ed0341cfe76d8021a6f512f09904fdb73e4880eb003e1e306906ef8f 6523 
upx-ucl_4.2.4-2_source.buildinfo
Files:
 c421196ddf3f8282ae7b3b296035786a 1806 utils optional upx-ucl_4.2.4-2.dsc
 a0f12542926e3793c54c86308388d46d 70048 utils optional 
upx-ucl_4.2.4-2.debian.tar.xz
 d54ac1fc5cd168da8b87b770119ad4c0 6523 utils optional 
upx-ucl_4.2.4-2_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmqWcHkQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFMM9C/4xsnWb0kKefh8jcBk+Akp/CCLA/SzIuHaA
pCD/jnWzlBNnywuxp/U8DLUGDNZhG9dIepoiI+lxXTeMgHpXLK7EdKAdXiY+l3Ai
nLz5tABsuImLEk3bskF2KglPZ/RtpWyxU6JcoPiDUAZy+GyizELVTWJLLbp7ntF7
qDQtmXbCh2eFaCBR97SRWXOwKsxbpS3bkV/EYBipp0DmQJw6T7XTZZPRqxTlF9RA
MpHhYBux0fTIgZqdoiZz2z68BgKDc12nj424OOyrrqeWjUP6mKgK6HEZcg6wRXMM
YiMLUms9npwdcr3TSXCCDLU1rpQqN9ONe4BTNMPrqHe6xUbA4aDzhy4mg2YZXhpL
Gmo/JDEQ9Z8wiBlHoEySjZ8Ue+KYNYyft0zrWqwjHEPSRI3TaKkLJmUz18KCcReX
9L6bdUM5fWRjes3Addga9gEteHaCSlul+VHImUBMgZvVtAaucG2z/ufsdpEuKo4v
3iosZOdCr38uE4oE6JrK+4DaT81xYM4=
=OyN2
-----END PGP SIGNATURE-----

Attachment: pgp5TSCjq0EoV.pgp
Description: PGP signature


--- End Message ---

Reply via email to