Bug#1087202: ITS: libimage-base-bundle-perl

наб <[email protected]> Sat, 9 Nov 2024 16:49:50 +0100
Newsgroups	gmane.linux.debian.devel.perl
Message-ID	<7q3n47rbza3gqb4nyjvqltpjk5tm3s2bfdeoi7ppyo6qoazv7z__11367.9748306581$1731167668$gmane$org@tarta.nabijaczleweli.xyz>
Source: libimage-base-bundle-perl
Severity: important
X-Debbugs-Cc: Package Salvaging Team <[email protected]>, [email protected]

Dear Maintainer,

I'm interested in salvaging your package libimage-base-bundle-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:

  - NMUs, especially if there has been more than one NMU in a row.
  - 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.

This package is best-fit for the Perl Group, which is in CC:.
Individual members of the Perl Group have done the majority of the NMUs.
The main issue with this package is its multi-upstream-tarball layout.
Well, it was before source version 3.0 (quilt). This d/watch:
  version=4
  opts=versionmangle=s/.*/2/	https://lfs.nabijaczleweli.xyz	(empty).tar.gz	group
  opts=component=Image-Base	https://metacpan.org/release/Image-Base	.*/Image-Base-v?@ANY_VERSION@@ARCHIVE_EXT@$	group
  opts=component=Image-Xpm	https://metacpan.org/release/Image-Xpm	.*/Image-Xpm-v?@ANY_VERSION@@ARCHIVE_EXT@$	group
  opts=component=Image-Xbm	https://metacpan.org/release/Image-Xbm	.*/Image-Xbm-v?@ANY_VERSION@@ARCHIVE_EXT@$	group
correctly watches the three packages and yields version
2+~1.17+~1.13+~1.10-1 currently, indicating the versions in order.
This works with the normal gbp workflow,
and matches the post-unpack layout basically verbatim (sans .tar.gz).
Also, quilt patches work.

I've rejuvenated the package based on this, forwarded still-relevant patches,
and fixed all outstanding bugs in my import at
  https://salsa.debian.org/salvage-team/libimage-base-bundle-perl
a DD (probably tille@ ‒ he's R/W in salvage-team too? idk how the ACLs are)
would need to move this to [2], yielding:
  $ debdiff libimage-base-bundle-perl_1.0.7-3.5_all.deb libimage-base-bundle-perl_2+~1.17+~1.13+~1.10-1_all.deb
  File lists identical (after any substitutions)
  
  Control files: lines which differ (wdiff format)
  ------------------------------------------------
   [-Requred-]
   {+Required+} by Image::Info to parse xpm and xbm files.
  Homepage: [-http://search.cpan.org/~summer/-] {+https://metacpan.org/author/KRYDE+}
  Installed-Size: [-81-] {+103+}
  Provides: [-libimage-base-perl, libimage-xbm-perl,-] {+libimage-base-perl (= 1.17), libimage-xbm-perl (= 1.10),+} libimage-xpm-perl {+(= 1.13)+}
  Version: [-1.0.7-3.5-] {+2+~1.17+~1.13+~1.10-1+}

I would rather point to something in the people.debian.org space
for the empty tarball in d/watch
(H4sICEhkL2cCA2EudGFyAO3BAQ0AAADCoPdPbQ43oAAAAAAAAAAAAIA3A5reHScAKAAA,
 created with tar -cf empty.tar -T /dev/null; gzip -9 empty.tar;
 it's 10k of 0 bytes post-unpack)
rather than a random URL in mine,
much like we do with the fake watches under
  https://people.debian.org/~eriberto/
but idk if there's a canonical location for this.

Best,
наб

[1] https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#package-salvaging
[2] https://salsa.debian.org/perl-team/modules/packages/libimage-base-bundle-perl
signature.asc (application/pgp-signature, 833 B)