Your message dated Fri, 15 Nov 2024 14:36:48 +0000
with message-id <[email protected]>
and subject line Bug#1085154: fixed in rzip 2.1-5
has caused the Debian Bug report #1085154,
regarding ITS: rzip
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.)
--
1085154: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1085154
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: rzip
Version: 2.1-4.1
Severity: important
X-Debbugs-Cc: Package Salvaging Team <[email protected]>,
[email protected]
[MIA team: this is this sponsored maintainer's final package;
their last activity was in 2016]
Dear Maintainer,
I'm interested in salvaging your package rzip, 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:
- NMUs, especially if there has been more than one NMU in a row.
I've set up a repository within the salvage-team space[2] to assist you
with this initial setup. If you decide not to accept the ITS, this
repository can easily be moved to another location, such as debian/, or
any place of your choosing. I hope this service helps make the
transition to using a Git repository on Salsa smoother and more
convenient for you.
Your package was highlighted in the Bug of the Day[3] initiative, which
aims to introduce newcomers to manageable tasks and guide them through
the workflow to solve them. The focus of this initiative is on migrating
packages to Salsa, as it's a great way to familiarize newcomers with a
consistent Git-based workflow.
Kind regards
Andreas.
[1]
https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#package-salvaging
[2] https://salsa.debian.org/salvage-team/rzip
[3] https://salsa.debian.org/tille/tiny_qa_tools/-/wikis/Tiny-QA-tasks
-- System Information:
Debian Release: 12.4
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
'stable-debug'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.1.0-12-amd64 (SMP w/24 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_FIRMWARE_WORKAROUND,
TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
-- no debconf information
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: rzip
Source-Version: 2.1-5
Done: наб <[email protected]>
We believe that the bug you reported is fixed in the latest version of
rzip, 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.
наб <[email protected]> (supplier of updated rzip 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, 15 Oct 2024 16:51:08 +0200
Source: rzip
Architecture: source
Version: 2.1-5
Distribution: unstable
Urgency: medium
Maintainer: Package Salvaging Team <[email protected]>
Changed-By: наб <[email protected]>
Closes: 411706 774037 1085154 1085156
Changes:
rzip (2.1-5) unstable; urgency=medium
.
[ наб ]
* Salvage Team upload
* Maintainer: Package Salvaging Team <[email protected]>
(Closes: #1085154)
* Standards-Version: 3.9.8 -> 4.7.0
* d/patches/0009-0012:
+ Refuse compressing directories (Closes: #411706)
+ Don't loop forever if input truncated (or corrupted) (Closes: #1085156)
+ Fix UBSAN shifts
+ Detect short read, preventing uninitialised memory access
(Closes: #774037)
* Vcs-Git: https://salsa.debian.org/salvage-team/rzip.git
.
[ Andreas Tille ]
* debhelper-compat 13
* Secure URI in copyright format (routine-update)
* Rules-Requires-Root: no (routine-update)
* Trim trailing whitespace.
* Use secure URI in Homepage field.
* Drop unnecessary dependency on dh-autoreconf.
* Rely on pre-initialized dpkg-architecture variables.
* Secure URI in watch file
Checksums-Sha1:
5dffcc2246070616cb7e37ba6242fe79f7e46bc5 1821 rzip_2.1-5.dsc
a230e81022af0c8a9f7cdffa71cc73645c63bfe3 8972 rzip_2.1-5.debian.tar.xz
0898375800ad9ead67f05c71c8709c4be5246562 6057 rzip_2.1-5_amd64.buildinfo
Checksums-Sha256:
dfbcf7079166148958d7881d9c56e5657700cd160ac5b0dfaf60b06dcd629c6f 1821
rzip_2.1-5.dsc
26895c8715c743f790dda0a173539cefb1faa971430a7cc9cf0b5341d1431e46 8972
rzip_2.1-5.debian.tar.xz
2fe227b1f98bf7699991e7857e0942cfa94352019c0fa1fdcfa8fae7399907ef 6057
rzip_2.1-5_amd64.buildinfo
Files:
5226ca1181ecd4174b823c3ffcdd0289 1821 utils optional rzip_2.1-5.dsc
0fc64f580251d886b26d20ba98d00151 8972 utils optional rzip_2.1-5.debian.tar.xz
59ea3bc93bb2b2642cdaf24a76b10789 6057 utils optional rzip_2.1-5_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmcqGqwRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtHRRA/+KvZ/b++4y3zfNIAL+gfL+zGJniWPFqbj
Drp+Eau+RS/X/5VlttLbYPQpsE5i5P4+1QmhlWMVJzXGO/mdk8cYr0S65umDflON
8psfk1DhK5924vslZmPdwAfnd+eVRl6n+JPaY/y3tW124N3QHd24Jb/Wes/K4iLa
w/e5POupZibbLTCSBKluv1aTmaNxvdAlJs2eJmcH+0cgzfAiPiaIe37GR2fZEyqE
6KS25gQtdrrNEWD4vbVU9MA21tkGaquh8vR5khAQmmaZI27UlhhUwqCC5wAiOKOR
VT5EXjUy2ub/bl4yobkserkHck5Ho90Q42h28VHhwta/E5HD5pTFdTmcHlla3ZGh
mUX0d7I5BKiDk3gSi5yEDYPKMSXo6Jkw9kK4DSnBmR/BhzWm1A2e/9cB+7qsETa5
95bNOQUy12fNPKQSKNmZMY7BGK+9F3dyTL/nCZULHVjn4SaGQBHhp6JuE46d35c3
CwC8cxEY9r/XLD5aW5fNRkymGMXxehUvykgK58fBY201WclzTMnrdpwAdi9y5Jh1
/Cl5CyKnXvS+Xd+yB4G3pyBeIcQLaxz9nhdZvzJAX1FV1Afd3hEl191bwD8MIMNk
3kPzNpMGuOuZ/zS6Q3FUYkl8P8KaqtDms2qKIwbGHljpcwT04eNb7UHfdOLVBTOU
Cc3TjDl1X/o=
=pMKU
-----END PGP SIGNATURE-----
pgpBVlLbly1wU.pgp
Description: PGP signature
--- End Message ---
