Your message dated Mon, 26 May 2025 10:18:54 +0000
with message-id <e1ujuv0-008zab...@fasolo.debian.org>
and subject line Bug#1104079: fixed in howdoi 2.0.20-1
has caused the Debian Bug report #1104079,
regarding ITS: howdoi
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 ow...@bugs.debian.org
immediately.)


-- 
1104079: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1104079
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: howdoi
Version: 1.1.9-1.1
Severity: important
X-Debbugs-Cc: 1051...@bugs.debian.org, Lucas Albuquerque Medeiros de Moura 
<lucas.moura...@gmail.com>, Package Salvaging Team 
<team+salv...@tracker.debian.org>, 1067...@bugs.debian.org, Shriram 
Ravindranathan <s...@ters.dev>

Hi,

I'm interested in salvaging your package howdoi, 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:

  - Bugs filed against the package do not have answers from the
    maintainer.
  - Upstream has released several versions, but despite there being
    a bug entry asking for it, 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.

Please note: There is no proper solution for bug #1051370 found yet.
I've pinged upstream about this.  I hope the problem can be solved
somehow soon.

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 Trixi
    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/howdoi
[3] https://salsa.debian.org/qa/tiny_qa_tools/-/wikis/Tiny-QA-tasks



-- System Information:
Debian Release: trixie/sid
  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.21-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: howdoi
Source-Version: 2.0.20-1
Done: Andreas Tille <ti...@debian.org>

We believe that the bug you reported is fixed in the latest version of
howdoi, 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 1104...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Tille <ti...@debian.org> (supplier of updated howdoi 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 ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Fri, 16 May 2025 11:15:45 +0200
Source: howdoi
Architecture: source
Version: 2.0.20-1
Distribution: unstable
Urgency: medium
Maintainer: Package Salvaging Team <team+salv...@tracker.debian.org>
Changed-By: Andreas Tille <ti...@debian.org>
Closes: 1046721 1067003 1085637 1104079
Changes:
 howdoi (2.0.20-1) unstable; urgency=medium
 .
   * New upstream version
     Closes: #1067003, #1085637
   * Maintain in Package Salvage team
     Closes: #1104079
   * Standards-Version: 4.7.0 (routine-update)
   * debhelper-compat 13 (routine-update)
     Closes: #1046721
   * Remove trailing whitespace in debian/copyright (routine-update)
   * Remove unnecessary X-Python{,3}-Version field in debian/control.
   * Replace use of deprecated $ADTTMP with $AUTOPKGTEST_TMP.
   * watch file standard 4 (routine-update)
   * Depends: python3-keep
Checksums-Sha1:
 20cf153d61bca6f4a69616426aa6f36326f03bcb 2036 howdoi_2.0.20-1.dsc
 acfd30fb73c50811630951dcbdfddb2eb2c48582 27595 howdoi_2.0.20.orig.tar.gz
 fcae0a0fc9d2f3c8736673b2bb681270301a5d49 3128 howdoi_2.0.20-1.debian.tar.xz
 375de9db28c801c323464524003554bb725d8e3b 6687 howdoi_2.0.20-1_amd64.buildinfo
Checksums-Sha256:
 f6a09575fd2e58b29b2747478d958c86336a35f682204988aacd7e2337da9d11 2036 
howdoi_2.0.20-1.dsc
 51cd40c53e0c0f8f8da88f480eb7423183be2350ab4f0a4d9d4763ca6ac3e2a9 27595 
howdoi_2.0.20.orig.tar.gz
 a1bc7b76b1f01e3deeb71c86ebedbaccb8a4b5549f985c1670c2fa6e7988b7d4 3128 
howdoi_2.0.20-1.debian.tar.xz
 cc7f0ac8a50ebac70c7a8b5db58aeb097edb1d812ff2889aaaba6836f18455f9 6687 
howdoi_2.0.20-1_amd64.buildinfo
Files:
 3c975b78eea265a535f368f3c17afce3 2036 misc optional howdoi_2.0.20-1.dsc
 87e5906deb84b13b056a42dffa564c47 27595 misc optional howdoi_2.0.20.orig.tar.gz
 795e7369f715af02bc8bdcbd90211205 3128 misc optional 
howdoi_2.0.20-1.debian.tar.xz
 2fe4606e48a018687ba27ad8fdfb07d1 6687 misc optional 
howdoi_2.0.20-1_amd64.buildinfo

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

iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmgnA1gRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtGpWA/+O0hFQqzotTpcE8YdhR/N/SC9WvCAzOZR
GGC85IbxNVl7QE0rOUDyVyj9JZRd4Js8uPo5jovZ8YcjRTEl3wPR5aY5wcSGANkA
qi/OHH9HivxD4FfEC92WWefUMOsEEj6XOrW46UEjXUgszSm8h9lsWQkkxcTP2pgD
ElhfUM6etYFmAfUtUXI0gZgJg85ap/OEksH41T8GUzxYUi0GIVx8Ge4THd4XPKrG
Gg3t2CfCqPCuBw+QAT7EcFjL/+s22wnO5XbGK24SivsMgGoWCqhZlRC+XzOj+Jy+
Dnzj3fjlzicKpT6d/hsmZWU5LhFTomZ8xVAWA0/wT2IbLHQUooO8chZtGUKsu6Mj
SwmIqD3H2kntH4V8nlLtumBZDfuWx15vSTAx61t3Xy6IKmLQ6dtpuaJMkWpzTAKJ
M3V5BjpRaJlGEyfcM1QGpe1A1VY4Dyc+qiUjbh0PZrvwi7GUs5Z6Sb09hGKTILa2
Lw8sKmZ5LDNpwCn1DDnSLQ3w5k9CWxmgvphSkEYoPWUc1yIo+z+6YMH1KH8T+GGb
wQcDGIQHCSOSacKqzOoSvFudd7cClWB7p+45sCjxDw6Tg4+wUOll2nodFJ/nKdNf
/Em9EUn6aJz0T+mu8jDbXIGdiVr4Qo1eN8jEeUjsDGj6LYU3lJmdmRp57rwy1d9K
etgG+ysSN8A=
=MKqo
-----END PGP SIGNATURE-----

Attachment: pgp7FLA1aKrnK.pgp
Description: PGP signature


--- End Message ---

Reply via email to