Your message dated Sat, 30 Nov 2024 14:42:52 +0000
with message-id <[email protected]>
and subject line Bug#1084788: fixed in utfout 0.0.1-2
has caused the Debian Bug report #1084788,
regarding ITS: utfout
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.)


-- 
1084788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1084788
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: utfout
Version: 0.0.1-1
Severity: normal
X-Debbugs-Cc: [email protected], James Hunt <[email protected]>, 
Package Salvaging Team <[email protected]>

Hi James,

I perfectly understood tat your package utfout does not really fulfill
the ITS criteria outlined in the Developers Reference[1].  Its a tiny
little tool that works (might deserve some enhancement as reported in
#962515).  

However your package was highlighted in the Bug of the Day[2]
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.  This was
mainly the reason why I have touched the package despite I know it does
not really match the ITS criteria and you probably have more urgent
things to do.  I hope you might rather consider the effort some helping
hand in modernising the package.

Strictly speaking about ITS we have:

  - Bugs filed against the package do not have answers from the
    maintainer (and applied the patch provided in bug #986379)
  - There are QA issues with the package - lintian is blaming the
    package about old Standards-Version, debhelper compat level, etc.

I've set up a repository within the salvage-team space[3] 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.

Kind regards
    Andreas.

[1] 
https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#package-salvaging
[2] https://salsa.debian.org/tille/tiny_qa_tools/-/wikis/Tiny-QA-tasks
[3] https://salsa.debian.org/FIXME-team/FIXME



-- 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.10.9-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: utfout
Source-Version: 0.0.1-2
Done: Andreas Tille <[email protected]>

We believe that the bug you reported is fixed in the latest version of
utfout, 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 utfout 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: Wed, 20 Nov 2024 14:52:38 +0100
Source: utfout
Architecture: source
Version: 0.0.1-2
Distribution: unstable
Urgency: medium
Maintainer: Package Salvaging Team <[email protected]>
Changed-By: Andreas Tille <[email protected]>
Closes: 986379 1084788
Changes:
 utfout (0.0.1-2) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Andreas Tille ]
   * Maintain package on Salsa (for the moment in Package Salvage team)
     Closes: #1084788
   * Standards-Version: 4.7.0 (routine-update)
   * debhelper-compat 13 (routine-update)
   * Secure URI in copyright format (routine-update)
   * Remove trailing whitespace in debian/changelog (routine-update)
   * Remove trailing whitespace in debian/control (routine-update)
   * Rules-Requires-Root: no (routine-update)
   * watch file standard 4 (routine-update)
   * Enable hardening options
   * Original Uploader address is bouncing ... remove Uploaders field
 .
   [ David Schledewitz ]
   * Norwegian Bokmål initial translation
     Closes: #986379
Checksums-Sha1:
 cc03e64e014484eff6d5a0acda40a509217d8a6b 1868 utfout_0.0.1-2.dsc
 ab160f53b141d60baa2a1ab87b5be89e4e26c41c 2564 utfout_0.0.1-2.debian.tar.xz
 d5360c20d9c06815323008f629be2d9603c84380 6090 utfout_0.0.1-2_amd64.buildinfo
Checksums-Sha256:
 e790d2ae31d3dc61934a4cd22abb7475e8a8210cbc2358a7ced8187814394267 1868 
utfout_0.0.1-2.dsc
 e631775a3ebce4daab5f4286e789f682a230089dcfb9e2a4af01d798de4e7f99 2564 
utfout_0.0.1-2.debian.tar.xz
 6958471d7383258f2b2f81ea07908c4118bc781fb7a7c54e68cb718585c2064e 6090 
utfout_0.0.1-2_amd64.buildinfo
Files:
 04c5d1b7e7970da4e5bb379fe2f5c893 1868 utils optional utfout_0.0.1-2.dsc
 56d9aec01871ffe9c0e163d6371ad2de 2564 utils optional 
utfout_0.0.1-2.debian.tar.xz
 e859b0aec9b6d513d552ea0e8212dba0 6090 utils optional 
utfout_0.0.1-2_amd64.buildinfo

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

iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmc97A4RHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtH4yg//WUk58oyASZRHj7X8BLuArw4Md2ynk4JP
s18MOKLMJs/Yyn8g8P/3UkWI+D7sw02yQObMekjDpE0UB8OitvPEQ790YL6ezjRm
AkmDyweIWezP5x953YLtVgwAaU/CK3TL+Km7Bj+UEyh9KbDlArA6jMbWTHgSPYV5
JpfL98x5BiT2VybSN79J5KI8kJ0cpBZfM38VOObskqp33dR6L6hwSLz5LSND5HtP
6cyjWc1qckwyl8MMhO9VL5QOSY8txQ9cOqbcoPhHfzr7GepGyvGOjelJ2trMFwWY
0pTRC8XssYsBPtNnUkhsTcO2ugfEuqIqzfXi48pMIQmkz8XC6Nzjvkrj2U3Zfi3i
4pD0xWJB3yC+8TwCvxH9T/HzYVO3JL+K47BQgclQWsPitYCCpPHRdVtD+ZpkgSZD
m6hDosdSD2cojloDgipmgZhZDY2+rlGe96uXPGCHzQ9xTYpta9p+DRx8WJxku4Ao
qqojuUolZbRo0HKMoVlxo8P7InCBdS6PPl/d+VrppkFznYHFykTTQ1jn69ETUZK5
2cVvClDN9ndS4eaRGtkKJN72M5K/MvUy1pjoiR/YrB6FfpQFupjDmWI8ywXTIjmx
V8Bnoa/F2YxkWjpbXNL4UaFIXK1T4PUNHec6B6l4dt8HNtTObO/Gub3fRg8ZM5pV
FfTx4DL6GYQ=
=B/4d
-----END PGP SIGNATURE-----

Attachment: pgp4AvBeFh1Et.pgp
Description: PGP signature


--- End Message ---

Reply via email to