On July 30, 2022 6:15:30 PM UTC, Dima Kogan <dkogan@debian.org> wrote:

Hi. This probably has been covered before, but it's so consistently
annoying that I'd like to bring it up again.

Currently the Debian build tools strongly encourage packages to have
exactly

Build-Depends: debhelper-compat (= 13)

This works fine if you're building for Debian/sid in 2022. It does not
work in any other context. I have a very common use case: at work I'm >maintaining several APT repos for the packages we use for several
distros (the last few releases of Debian and Ubuntu). The latest Debian >already has the packages in it, so the Build-Depends line is exactly as >above. But this means that building the package for any of the older
releases fails. And if I say something reasonable like

Build-Depends: debhelper-compat (>= 11)

Then this happens when building the package on sid:

dh: warning: Found invalid debhelper-compat relation: debhelper-compat (>= 11)
dh: warning: * Please format the relation as (example): debhelper-compat (= 13)
dh: warning: * Note that alternatives, architecture restrictions, build-profiles etc. are not supported.
dh: warning: * If this is not possible, then please remove the debhelper-compat relation and insert the
dh: warning: compat level into the file debian/compat. (E.g. "echo 13 > debian/compat")
dh: error: Could not parse desired debhelper compat level from relation: debhelper-compat (>= 11)
make: *** [debian/rules:8: clean] Error 255

It isn't helpful. Most packages (including mine) are very vanilla, and
there isn't any difference between debhelper 11 or 12 or 13. I'm having
to patch debian/control every time I do a build, and this isn't a useful
use of my time. Can we please loosen this in some way?

Is your package compatible with debhelper 14? If so, how do you know?

Scott K

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi. This probably has been covered before, but it's so consistently
annoying that I'd like to bring it up again.

Currently the Debian build tools strongly encourage packages to have
exactly

Build-Depends: debhelper-compat (= 13)

This works fine if you're building for Debian/sid in 2022. It does not
work in any other context. I have a very common use case: at work I'm maintaining several APT repos for the packages we use for several
distros (the last few releases of Debian and Ubuntu). The latest Debian
already has the packages in it, so the Build-Depends line is exactly as
above. But this means that building the package for any of the older
releases fails. And if I say something reasonable like

Build-Depends: debhelper-compat (>= 11)

Then this happens when building the package on sid:

dh: warning: Found invalid debhelper-compat relation: debhelper-compat (>= 11)
dh: warning: * Please format the relation as (example): debhelper-compat (= 13)
dh: warning: * Note that alternatives, architecture restrictions, build-profiles etc. are not supported.
dh: warning: * If this is not possible, then please remove the debhelper-compat relation and insert the
dh: warning: compat level into the file debian/compat. (E.g. "echo 13 > debian/compat")
dh: error: Could not parse desired debhelper compat level from relation: debhelper-compat (>= 11)
make: *** [debian/rules:8: clean] Error 255

It isn't helpful. Most packages (including mine) are very vanilla, and
there isn't any difference between debhelper 11 or 12 or 13. I'm having
to patch debian/control every time I do a build, and this isn't a useful
use of my time. Can we please loosen this in some way?

Thanks!

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Sat, Jul 30, 2022 at 11:15:30AM -0700, Dima Kogan wrote:

Hi. This probably has been covered before

It wasn't, but it's completely identical to putting 13 into debian/compat, which never supported >= either.

This works fine if you're building for Debian/sid in 2022. It does not
work in any other context. I have a very common use case: at work I'm maintaining several APT repos for the packages we use for several
distros (the last few releases of Debian and Ubuntu). The latest Debian already has the packages in it, so the Build-Depends line is exactly as above. But this means that building the package for any of the older
releases fails. And if I say something reasonable like

Build-Depends: debhelper-compat (>= 11)

And the recommendation was always "put 11 into debian/compat if you want
to build on older distros".

It isn't helpful. Most packages (including mine) are very vanilla, and
there isn't any difference between debhelper 11 or 12 or 13.

(there can be important changes even in very vanilla packages)

I'm having to patch debian/control every time I do a build

You presumably also have to patch debian/changelog, and building a single unchanged (apart from debian/changelog) package for multiple distros is
not going to always work either (even for very vanilla packages, e.g.
because of different versions for versioned B-D in Debian and Ubuntu).

--
WBR, wRAR

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

iQJhBAABCgBLFiEEolIP6gqGcKZh3YxVM2L3AxpJkuEFAmLlke8tFIAAAAAAFQAP cGthLWFkZHJlc3NAZ251cGcub3Jnd3JhckBkZWJpYW4ub3JnAAoJEDNi9wMaSZLh 8kkP/R7YfHLJYYneW/bgzSzYVDcSlm7D/QEb0fdj0SDCQ1OojCY61moFgMOa3oAj dbb7lKuB9f+o1kv1eyfySU3urBbRfve+2gG2uc1KtbcB3Bno39iUflpphyMgrkY+ SC8QIAVrI49e5AmxKXXdlCOs8BSJZqW1y84vvucJKPJSQ1c/QCV9wQ5dKARqfAds n6t4Fg8ZO7oLQbOlthT9fay48bE4JdNgqVooxoqrRdP+3CsLRLH86uu67JyQ3srS lRgM+obR+T0joAxhWt66L/K+vY854nfOpA8sy6rvlu/3vAY4aFDT+P6bX6Y4k4AF Pi0GMwZwiIXO4O7sz1Mi7AzzqHPVYPre1uk2EOyYu+Ii+jJOIubR7X+qXYYXukR7 7UAvYUrJuK1NcQObwBFBCCtlTKq6a0lDLyJFLyJLWDgZmkpBp6BOGd/Jl/mC44ji 8KQGXUf3liv2cH59EqdH8vSg6nOCo9zzyhvY6fdzz4gxgNl06VexMCtW1QojBDfI cTig1+mTCKceMB9kyjNIabwwQfJ+sJFqJhYndgOMK5hD2knWPO+bkMnCHpCNCDce 70qwVKibPVjHSfro7XeHtvoOE0zJeOlzfwp3hGi/AURhqdSv6zj1mhdHneR7OXRC P4fnJlzfOEzLTH5t4Xt/o+Q5UR9xA6OhRv3zXSjlmu8u31qh
=K5+v
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Andrey Rahmatullin <wrar@debian.org> writes:

it's completely identical to putting 13 into debian/compat

Oh. So it is. I vaguely remember that using debian/compat and
"Build-Depends: debhelper" generated some lintian complaints. I don't
see those anymore, though. Is doing something like that frowned-upon?
I'd probably stick with compat level 11 or so.

I'm having to patch debian/control every time I do a build

You presumably also have to patch debian/changelog, and building a single unchanged (apart from debian/changelog) package for multiple distros is
not going to always work either (even for very vanilla packages, e.g.
because of different versions for versioned B-D in Debian and Ubuntu).

Totally. Yeah. There aren't a huge number of packages here, and there
aren't a ton of people using them. If something breaks, I'll get a bug
report, and I'll fix it. It's well worth it to get APT as a distribution mechanism.

Thanks much

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Sat, Jul 30, 2022 at 10:21:06PM -0700, Dima Kogan wrote:

it's completely identical to putting 13 into debian/compat

Oh. So it is. I vaguely remember that using debian/compat and
"Build-Depends: debhelper" generated some lintian complaints.

Using debian/compat and "Build-Depends: debhelper-compat" generates them, because the latter replaces the former.


--
WBR, wRAR

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

iQJhBAABCgBLFiEEolIP6gqGcKZh3YxVM2L3AxpJkuEFAmLmIOEtFIAAAAAAFQAP cGthLWFkZHJlc3NAZ251cGcub3Jnd3JhckBkZWJpYW4ub3JnAAoJEDNi9wMaSZLh 6YAP/RoH27zhmYp0WNhW4S4rpkauDkZ/Q+QoIWjAHXEElk6g8aICPT6iaWD4uKM9 07cIdMGZg9nfEcL7N3AQ7kiwyBmIqooLHniLR6c/ooe7DV66yvHvCvH/Acaz0BYL FpoBNf6YoLYhc4MVAqUhfy9um/SFn1SNu6nv8UuuSdMIROpZ7e+XDkG0gMLKQKwB ng10yA51F7DbDQMTsDcSlLBmJY1DKvS9l/1QtHFADld39fKhXQ7biGxrM8fWiQu4 u0owEUzWgkANZGuAD93IOPhTdnj1+bZ2ZuMDYGHnGD4cUSLPN+3uEMr537QP4ehh LAkrpXQexXI5TrZYk58hXevolLSEdLGjC3t2bXK23/A9k/TC4DJ4wVwnpHAOGOrC xbV651218JDs8qlwSP59pipbrEHadSbkUuVmQKu5RwrlwpvjBlYHLM8nWQ5JvvFR HNmlVE2cfUsGfezSA53kvi/tD7Q9mdC0LqTOWnb6ZGD/poWHAH0iHT9Mwz1Vfxwp 3Ku0QHVg75+DWzzMpJsNf7FbQXLBKiJtupxJCks4+5YqL4+dcaqguZDtJYK6/GR8 m8x4ptpQ6INsy5asH6cgfeF3hCrvL6gzrl9jRm0SDweNyoxhjNYBXZvMdBiFHDoz cJr9XISdffChiCgV27gL7MSiHdeWHVsS7SVA9eDIKijhroau
=xgqB
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Andrey Rahmatullin <wrar@debian.org> writes:

On Sat, Jul 30, 2022 at 10:21:06PM -0700, Dima Kogan wrote:

it's completely identical to putting 13 into debian/compat

Oh. So it is. I vaguely remember that using debian/compat and
"Build-Depends: debhelper" generated some lintian complaints.

Using debian/compat and "Build-Depends: debhelper-compat" generates them, because the latter replaces the former.

OK. I'm doing it wrong, then. Thanks for the clarification!

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)