Your message dated Wed, 13 Aug 2025 01:01:00 +0000
with message-id <[email protected]>
and subject line Bug#1108084: fixed in hexcurse 1.60.0-1
has caused the Debian Bug report #1108084,
regarding ITS: hexcurse
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.)


-- 
1108084: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1108084
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: hexcurse
Version: 1.58-1.4
Severity: important
X-Debbugs-Cc: [email protected], Package Salvaging Team 
<[email protected]>, Gergely Risko <[email protected]>

Hi,
 
I'm interested in salvaging your package hexcurse, 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 (more than one NMU in a row).
  - Bugs filed against the package do not have answers from the
    maintainer.
  - Upstream has released a new version long ago, but it has not been
    packaged.
  - There are QA issues with the package.
 
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.
 
PS: I do not plan to upload a salvaged package before the Trixie
    release to not influenze the freeze process.
 
[1] 
https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#package-salvaging
[2] https://salsa.debian.org/salvage-team/hexcurse
[3] https://salsa.debian.org/qa/tiny_qa_tools/-/wikis/Tiny-QA-tasks

-- System Information:
Debian Release: 13.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (50, 'buildd-unstable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.3.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

--- End Message ---
--- Begin Message ---
Source: hexcurse
Source-Version: 1.60.0-1
Done: Andreas Tille <[email protected]>

We believe that the bug you reported is fixed in the latest version of
hexcurse, 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.
Andreas Tille <[email protected]> (supplier of updated hexcurse 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: Fri, 20 Jun 2025 09:32:25 +0200
Source: hexcurse
Architecture: source
Version: 1.60.0-1
Distribution: unstable
Urgency: medium
Maintainer: Package Salvaging Team <[email protected]>
Changed-By: Andreas Tille <[email protected]>
Closes: 1096805 1108084
Changes:
 hexcurse (1.60.0-1) unstable; urgency=medium
 .
   * Maintain package in Salvage team
     Closes: #1108084
   * Add Homepage
   * Add watch file
   * d/copyright: DEP5
   * New upstream version
   * Standards-Version: 4.7.2 (routine-update)
   * debhelper-compat 13 (routine-update)
   * Remove trailing whitespace in debian/control (routine-update)
   * Remove trailing whitespace in debian/copyright (routine-update)
   * Fix old-style function definition
     Closes: #1096805
   * Propagate hardening options
   * Mention fork in d/README.source
Checksums-Sha1:
 023b6c721a5f7f0a69f577fe6dda78054b181f3d 1987 hexcurse_1.60.0-1.dsc
 6cc1159c1e8b2ff13a1788eae6440f3be1d95cca 171904 hexcurse_1.60.0.orig.tar.gz
 bc642ff7071acd8c134f2db8dd94dfb8561b1b3a 4692 hexcurse_1.60.0-1.debian.tar.xz
 ee74de20cefa9c4c788e23d932366721ba7ca0c1 6240 hexcurse_1.60.0-1_amd64.buildinfo
Checksums-Sha256:
 8fb0e489c1e085f1646cdde96510f071413cfbf7fe1a8a605fe894ae7d26d6b7 1987 
hexcurse_1.60.0-1.dsc
 f6919e4a824ee354f003f0c42e4c4cef98a93aa7e3aa449caedd13f9a2db5530 171904 
hexcurse_1.60.0.orig.tar.gz
 887daa022f7b61f740a0ed293f880c5b2fdf112c00a54fdcfb713e157a91471a 4692 
hexcurse_1.60.0-1.debian.tar.xz
 4669b12f00ded7bea196e1063385e739374aef05800db506fdc973cdc62a61cb 6240 
hexcurse_1.60.0-1_amd64.buildinfo
Files:
 7792348ce5d91f1cd9899b7c658da4b3 1987 utils optional hexcurse_1.60.0-1.dsc
 cb24b564bea21a615a5c6a2ee30d6cad 171904 utils optional 
hexcurse_1.60.0.orig.tar.gz
 5d86466a3b5dce1e5ade25db3f2ba095 4692 utils optional 
hexcurse_1.60.0-1.debian.tar.xz
 ebb573ee679a43d615226da313c73b6b 6240 utils optional 
hexcurse_1.60.0-1_amd64.buildinfo

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

iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmiNMHERHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtELMQ/+LGEXI08lhNWKshDmqaYlATk8axaVjPt9
Ruy5koNHzYV9lUMtwsNrYK/WfIkUVixxCABydC4502AncVEHC/hGKI3BUx/lp/PV
qr5g1JQdLC04nnlgIvblHY212SV2fiQh0RWJ4VaEPXnhOwuUoFq7yM7ZKMy9U4F7
fimSYNLfm8jYMZ4o6f3WRJ3S5D0hNixBTe1uSa73bjoXfR3twLrtrCBEGWnYwpxk
PRPWBHYD4UOphVJXciOqja25z4tCS+niGd9YaUTUbTdzM4NJWqHu88giCWxcPS0Y
qVm6r9zJ1ldadAezzR2vHJCb8w1Zu3oz3tOHDwjNfkkUbaUc0tEUAiIoL7JdFZ+y
o5UoRaNWHbDEUx7/3ySC4N/mhFuEfzQtegGyvMK4tS/dlhVcC6ronOB04ev/Q/p5
fM22zmKAQebHGelpIFg/UGIQwpt/bVBehzPfb4ExxuO5WWI0z+CfGFS/7AscUn7Q
6bb2dLZUdGv6pE60924d51tQuOPLazWlC6Vo2dVZ+y5erD2ERzN026Bps9rg7ylD
7biW/JHnZHHMzYyCWqcDb1ec2HpbF/c5afyBfqookFEmvmawRMcwQGghKjr/Dvjn
5BWrVVCio0Hsm8W0ekVG/o5EpQv0ErNAxJDhUM++rotjeExwwCAUqKrrCXPr/yjJ
WtwOvHkdZW0=
=ck4u
-----END PGP SIGNATURE-----

Attachment: pgpoboXJY89r7.pgp
Description: PGP signature


--- End Message ---

Reply via email to