Your message dated Sun, 02 Nov 2025 07:49:08 +0000
with message-id <[email protected]>
and subject line Bug#1117032: fixed in git-crypt 0.8.0-1
has caused the Debian Bug report #1117032,
regarding ITS: git-crypt
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.)


-- 
1117032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1117032
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: git-crypt
Version: 0.7.0-0.1
Severity: important
X-Debbugs-Cc: Andrew Ayer <[email protected]>, Package Salvaging Team 
<[email protected]>, [email protected]

Hi,
 
I would be interested in helping with git-crypt, following the Package
Salvaging procedure outlined in the Developers Reference[1]. From what I
see, the package seems to meet the criteria for this process, and I'd
like to support keeping it maintained in Debian. As the Salvage process
suggests, here is a list of the criteria that I believe apply:
 
 
  - NMUs
  - Bugs filed against the package do not have answers from the
    maintainer.
  - Upstream has released new versions
  - 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.
 
This 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 help newcomers become familiar
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/git-crypt
[3] https://salsa.debian.org/qa/tiny_qa_tools/-/wikis/Tiny-QA-tasks


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

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

--- End Message ---
--- Begin Message ---
Source: git-crypt
Source-Version: 0.8.0-1
Done: Andreas Tille <[email protected]>

We believe that the bug you reported is fixed in the latest version of
git-crypt, 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 git-crypt 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: Thu, 23 Oct 2025 09:06:36 +0200
Source: git-crypt
Architecture: source
Version: 0.8.0-1
Distribution: unstable
Urgency: medium
Maintainer: Package Salvaging Team <[email protected]>
Changed-By: Andreas Tille <[email protected]>
Closes: 1061080 1117032
Changes:
 git-crypt (0.8.0-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version
     Closes: #1061080
   * Maintain in Salvage team
     Closes: #1117032
   * Standards-Version: 4.7.2 (routine-update)
   * debhelper-compat 13 (routine-update)
   * Secure URI in copyright format (routine-update)
   * Update watch file format version to 4.
   * Set upstream metadata fields: Bug-Database, Repository.
   * Set upstream metadata fields: Bug-Submit.
   * d/watch:
      - Upstream does not provide a signature on web page
      - Version: 5
   * d/rules: hardening options
Checksums-Sha1:
 55865a31188c0b691ff151503ff5f48213c79b3c 1991 git-crypt_0.8.0-1.dsc
 d77984aea1f76ebff7f57270d6c5823eb04b7e77 57457 git-crypt_0.8.0.orig.tar.gz
 dbe383c679b30062219f9f50b7fb2abd1bd72652 10228 git-crypt_0.8.0-1.debian.tar.xz
 88db620a00124bf0cc16d0217613ca560394418d 6030 git-crypt_0.8.0-1_amd64.buildinfo
Checksums-Sha256:
 6ba1958464130adfcf785c74694b0dc837eb68de652d98ce27f3858ad68a9dbc 1991 
git-crypt_0.8.0-1.dsc
 540d424f87bed7994a4551a8c24b16e50d3248a5b7c3fd8ceffe94bfd4af0ad9 57457 
git-crypt_0.8.0.orig.tar.gz
 2711251697b47ad919acd4745faaaa211412ca1acf30f1dba5309b3e45309756 10228 
git-crypt_0.8.0-1.debian.tar.xz
 d06d5a8103ee974c3b2598f97e258ed093a7a1a5cf0bad2ba5bd5e3f4b6a6c4e 6030 
git-crypt_0.8.0-1_amd64.buildinfo
Files:
 a69b46555187b88b54f817b7774547f6 1991 vcs optional git-crypt_0.8.0-1.dsc
 fb7cae94cab749bb745e0a39fe6bd6e0 57457 vcs optional git-crypt_0.8.0.orig.tar.gz
 b28fc660219b40bbd8f3a5719cd75d5f 10228 vcs optional 
git-crypt_0.8.0-1.debian.tar.xz
 5cb4c9f433cbd9dab9d8b369a2c5cffe 6030 vcs optional 
git-crypt_0.8.0-1_amd64.buildinfo

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

iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmj51IQRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtFcKQ/8DLrS36ysOXEXyeR76dEuptGFOKppVOWJ
sZViU/v2Os65r/8IVx3wbdQomD5WG70GjIV7trIkidUG8REYYgOUgiBkoJTIf3LD
yPR3/va61fpww9KzveS/3UW7gh5TjwAsSauLyLQMl/LCkNaaR4DysEK0xFw2co0z
9jNymgjm9MtpLUvYNC6TrNwW7QCrpRC2rj/lR5l53sjd4SqH2LoU72Ma+zbj1Jwn
AKx/+EwcKySQ7VXFf2AY3KwSkldolw/3SQawmxVxEopCl0Jgmv44eQ2sIpmAPg3l
UOxuyJ0dY5/UGOmeUfHdUSokR0K/JFGNgyu/jDZWZIerRzp7u9EYbU8U38ri7inf
GD/F+PjJ6bTke75X8xJ/vGaMIv8cSI35I6HYpmKW7lJfu+UMID2Jpjd5Y6MjhrgC
bPzJoTVAxiMsf5UbK+hVKhmsqbx7jRr0BKCSksvpeAGkhZRbdHB3HJDB79AeWxur
jHxnn1A4mn7BeEQe+NF8+Y/6ihzbsskN8oiv97+Wq+1vIV2AcSihIlzhCsr5Y5WU
tYrj5bm052c5vCr675d/ejaH66VLHYBRgLV1sy9+z9i8e2NNPob00qPvLVZxqqb/
MW9vDm31zx/2boIPvFj7/etX157lKtvVv6eBZl92lbel84ydolwFW5kJpjUYKzk+
eHJBYQxQIxo=
=+eQD
-----END PGP SIGNATURE-----

Attachment: pgp4lxQPobyX5.pgp
Description: PGP signature


--- End Message ---

Reply via email to