Re: New update fields for cme dpkg

Dominique Dumont <[email protected]> Sat, 04 Apr 2026 15:04:38 +0200
Newsgroups gmane.linux.debian.devel.perl
Message-ID <2921598.irdbgypaU6@ylum>
--nextPart14644609.uLZWGnKmhe
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"; protected-headers="v1"
From: Dominique Dumont <[email protected]>
To: [email protected]
Subject: Re: New update fields for cme dpkg
Date: Sat, 04 Apr 2026 15:04:38 +0200
Message-ID: <2921598.irdbgypaU6@ylum>
In-Reply-To: <[email protected]>
MIME-Version: 1.0

On Wednesday, 25 March 2026 21:38:59 Central European Summer Time gregor=20
herrmann wrote:
> If you look into dpt-debian-upstream -- ehm, actually
> Debian::Upstream::Metadata::Perl (bin: libdebian-source-perl, src:
> dh-make-perl) -- we can see that the authors (mostly alexm) put in
> quite some effort to fix/cleanup the URLs that are found in the
> metadata files of perl distributions (like: no ssh://, no git://,
> https:// instead of http:// if possible etc., handling Repository vs.
> Repository-Browse). All these fixups have been added and refined
> over time because of examples seen in the wild =E2=80=A6

Which makes sense.

Would it be possible to modify Debian::Upstream::Metadata::Perl so that the=
=20
fixup logic is isolated in a function callable by cme ?

This way, cme would call this function and perform the same updates as dpt-
debian-upstream.

> Maybe the upstream situation has improved by now but I fear that
> creating/updating d/u/metadata by running `cme update
> dpkg-upstream-metadata' would generate buggy entries or overwrite
> correct ones generated by
> dpt-debian-upstream/Debian::Upstream::Metadata::Perl.

Agreed.

All the best

--nextPart14644609.uLZWGnKmhe
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.
Content-Transfer-Encoding: 7Bit

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

iQIzBAABCgAdFiEEn3I5/LZk8Qsz6dwDwx9P2UmrK2wFAmnRDGYACgkQwx9P2Umr
K2xN9Q/8DdtqRjxFi/NDv+QapZJb2QPo7Avcd6O0BNwBJlCuVld1L8kI2oYwBpFq
kMJnAptq7Gm682T06+ZfOwv0hNr28k7ICFK4D2T8Z0AniiuSE0OjhJlEbLA4vp7b
nPTypUM9OC7+Z92VjiBGUL6wqdVerpEAS2Wkujm9Hr++ji2aYAuVOL5rwH8/iFO4
qUZ8snttuHlHtKO+N4MGvvPcDSePNGxxSRwA9Od6mJaj1sCVtDy8zHsAKV2CA3Zu
cWbtFcJyv0K36USV6TH8is2YU2RGrxtobOwXzpKBQ7erkp0FgWfDsM67JIaFKF15
DJrrHq1Lyb2ud5BUHX52fwpZRau7YBe0i8/MaXvRKqSdqgttTn3TsXI8UNy8wnT5
duBj0V9hrnZu2+yLCGWKOR235UYZyZdIurZ9UKpdXroZz4c0tll6XLRcHYALHBau
wHFMMt++qbQdn8yMXnZgzSa8Y/5/Cr66W+PQcWr7xLSFoN8QvWIN3TLBFIXdpcFj
pq8n5SWfVZaJz26YNZnyBn+VAec9S2WxYZfpdYpaXyffmCMllT4Er4A9fo5tP7DD
NUXMJeT8e8cEDQem67UgOdw0EmiLgaQVm7O9N5V4lZwLjmAS4k3+QoOAn/ppxgvn
PthJxcduowpwxrX/0clDCGsZydW9UqsJbaopetMywxKvhtDmaDA=
=lxAT
-----END PGP SIGNATURE-----

--nextPart14644609.uLZWGnKmhe--