Your message dated Mon, 11 Aug 2025 18:50:28 +0000
with message-id <[email protected]>
and subject line Bug#1106618: fixed in libanyevent-forkobject-perl 0.09-2
has caused the Debian Bug report #1106618,
regarding ITS: libanyevent-forkobject-perl
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.)


-- 
1106618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1106618
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: libanyevent-forkobject-perl
Version: 0.09-1.1
Severity: important
X-Debbugs-Cc: Debian Perl Group <[email protected]>, 
Dmitry E. Oboukhov <[email protected]>, [email protected], Package 
Salvaging Team <[email protected]>

Hi,
 
I'm interested in salvaging your package libanyevent-forkobject-perl, 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.
  - No upload since 14 years
  - There are QA issues with the package.
 
I believe your package would be a great addition to the Debian Perl
Group, and I took the liberty to create the Salsa repository here[2]. If
you choose not to accept the ITS, I'd be more than happy to help you
move it to another location, such as debian/, or wherever you prefer. My
goal is to make it as easy as possible for you to join the team. I'd
also be delighted to assist in adding you as a team member if you could
share your Salsa login.
 
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/perl-team/modules/packages/libanyevent-forkobject-perl
[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.27-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: libanyevent-forkobject-perl
Source-Version: 0.09-2
Done: Andreas Tille <[email protected]>

We believe that the bug you reported is fixed in the latest version of
libanyevent-forkobject-perl, 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 
libanyevent-forkobject-perl 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, 27 May 2025 08:17:26 +0200
Source: libanyevent-forkobject-perl
Architecture: source
Version: 0.09-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group <[email protected]>
Changed-By: Andreas Tille <[email protected]>
Closes: 1106053 1106618
Changes:
 libanyevent-forkobject-perl (0.09-2) unstable; urgency=medium
 .
   * Maintain in Debian Perl Group
     Closes: #1106618
   * cme fix dpkg-control
   * Fix Homepage
   * Fix watch file
   * debhelper-compat=13
   * Switch from cdbs to debhelper
     Closes: #1106053
   * Fix DEP5 header
   * Add use-name for pkg-perl use.t autopkgtest
Checksums-Sha1:
 15ad3dc9256e01bb953039276a81f7d831812643 2327 
libanyevent-forkobject-perl_0.09-2.dsc
 62d95124f3da24bff6fff78627856e168015e4a9 1760 
libanyevent-forkobject-perl_0.09-2.debian.tar.xz
 c5b1a1c24de09a8eae7d6e8ff608cc538c46163a 6344 
libanyevent-forkobject-perl_0.09-2_amd64.buildinfo
Checksums-Sha256:
 89f35c8171afd9600f328b417878ddb366e05437234e46e5d412c3b33710e6b4 2327 
libanyevent-forkobject-perl_0.09-2.dsc
 fa6e19177f4a13938bf727c5e6ebdfaa18eef36c63addea3a971faafb54eaef7 1760 
libanyevent-forkobject-perl_0.09-2.debian.tar.xz
 e69e675cb0515663d263cf343e02083ec2e611d21c8e8da2e155ebb93811d199 6344 
libanyevent-forkobject-perl_0.09-2_amd64.buildinfo
Files:
 db3aa8c5ba36eb278742b6dcabaf7e93 2327 perl optional 
libanyevent-forkobject-perl_0.09-2.dsc
 d2b3926b9292abc35ec72483ea227669 1760 perl optional 
libanyevent-forkobject-perl_0.09-2.debian.tar.xz
 2803f161c03514c27ca83d0a9eb162c1 6344 perl optional 
libanyevent-forkobject-perl_0.09-2_amd64.buildinfo

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

iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmiGZrURHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtHV/g//YGF4CNGZmki8LNM/NHIpFBgpH7th39y/
dyNYBoSB7uuWh4zDUWM4XS8UHQ7r7CiBF65KZ2Gvcikoh46Gp0SSQYrXXVeU31zH
gb/MiaN4MV0Y8BuDv//4SuAnJz7XF/Ul6QWfWqOb5yoPfLj6kMXEX2rOxGBC69de
FZ0FXrNMZRzzOc8GG9XRGD08rwklKmE/mM9wNZ1b68t8rqRXm3vF8l8B/oDEYm+n
LLxkbjNxC6bIoJraapaJHNWdrkl3uFuPTJOE95Lfa7ocqnjITSlh+D3Ijt+RGjMp
eRSwcS4Vm+7ibPNULpMCnQJkN3J6QLRHYcIr92yXJi3GN3wRI1i6EwV0SF8eKfRm
iNCT2GNmNVwQY/07ei1Lh5ggoufaZfNghVHZUKgsuf5+p6eFcrkN2+9mOsWamIU1
OTzV2U1cJj5saqRTf/xkl8ILVoyv0lKiU+wpNfWPl00/6QLdjao5wDB0Bksn7+/x
9l3/KkvBomurGqG5hA00P4X6mBe24OzBdF3Zc3v4gaRYRQIJQC1QekYWNGgQ4TY9
BibZhA7mShGOb4WOENssxDp+/jbovSVbOaOHdjpX3622TVzRg4y52omIHi8tlBK1
FcLepz9gnJap7N1UjC5jJIT1JUKEHGJCihzM7nCKLgIf00OkBECw5YfmDeDbDRzx
XFKGvP7sNws=
=tJh3
-----END PGP SIGNATURE-----

Attachment: pgp_oqSXhzVDE.pgp
Description: PGP signature


--- End Message ---

Reply via email to