Bullseye packages - debhelper compatibility level 13 OK?

johnraff · 2021-02-02 02:31:42

debhelper 13 is available in buster-backports, default in Bullseye, and brings some enhancements over 12 (and certainly 10, which we are currently using) that might possibly be useful in the future.

@nobody is debhelper 13 available in your build environment? Would it cause no problems at your end if I started setting 13 as the compatibility level in the source of packages for Beryllium?

Otherwise I'll use 12 which is presumably OK?

Last edited by johnraff (2024-04-21 05:11:56)

nobody · 2021-02-02 17:51:21

Per se updating a build dep to a package version from backports would require backports to be enabled on all target systems, because apt-get source would otherwise fail.

Current dockerbuild does not support backports at build time yet but I already have working patches so it's possible to go that route.

I would keep non-backports version in lithium/buster.

Maybe only raise the compat level if functionality of the next level is used (or must be used)?

johnraff · 2021-02-03 05:27:27

Debhelper in Buster: 12
Debhelper in Buster-backports: 13
Debhelper in Bullseye: 13

Debhelper compat level set in our Lithium source packages: 10

I was suggesting setting compat level 13 in the Beryllium/Bullseye packages as I migrate them now. No intention of changing the existing packages.

It's not a big issue though, because we aren't using any fancy new debhelper features (unless you are in bunsen-os-release); I was just thinking if in the future we wanted to use something it would be easier if the 13 compat level was already set and any inconsistencies that came up had already been dealt with.

Backports:

updating a build dep to a package version from backports would require backports to be enabled on all target systems

This means backporting a Beryllium package build-depending on debhelper 13 to Lithium would require the Lithium build system to have backports enabled, in order to use the backported version (13) of debhelper?

Don't Lithium backports (buster-backports) already require the Debian buster-backports repos to be available to satisfy their possible dependencies on some Debian packages? Or is that different from what build environment they require?

Anyway, if 13 in Beryllium would make life more complicated for you, by all means lets drop it. I guess 12 (Buster default) would be OK, even though current packages are using 10?

johnraff · 2021-02-04 05:05:10

Anyway, I'll start migrating Beryllium packages, and set the debhelper compatibility to 12. If we ever hit a case where 13 would make things easier we can think about it at that point.

#1 2021-02-02 02:31:42

Bullseye packages - debhelper compatibility level 13 OK?

#2 2021-02-02 17:51:21

Re: Bullseye packages - debhelper compatibility level 13 OK?

#3 2021-02-03 05:27:27

Re: Bullseye packages - debhelper compatibility level 13 OK?

#4 2021-02-04 05:05:10

Re: Bullseye packages - debhelper compatibility level 13 OK?

Board footer