[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Possibility of backports for debhelper



On Fri, Sep 18, 2026 at 09:46:34AM -0300, Leandro Cunha wrote:
> Hi,
> 
> On Fri, Sep 18, 2026 at 9:01 AM Peter Pentchev <roam@ringlet.net> wrote:
> >
> > On Fri, Sep 18, 2026 at 08:35:32AM -0300, Leandro Cunha wrote:
> > > Hi,
> > >
> > > On Fri, Sep 18, 2026 at 4:26 AM Peter Pentchev <roam@ringlet.net> wrote:
> > > >
> > > > On Fri, Sep 18, 2026 at 10:20:12AM +0300, Peter Pentchev wrote:
> > > > > On Thu, Sep 17, 2026 at 08:37:11PM -0300, Leandro Cunha wrote:
> > > > > > Em qui., 17 de set. de 2026, 19:51, Peter Pentchev <roam@ringlet.net>
> > > > > > escreveu:
> > > > > >
> > > > > > > On Fri, Sep 18, 2026 at 01:49:26AM +0300, Peter Pentchev wrote:
> > > > > > > > On Thu, Sep 17, 2026 at 11:04:34AM -0300, Leandro Cunha wrote:
> > > > > > > > > Hi everyone
> > > > > > > > >
> > > > > > > > > I was packaging using Debian Trixie and migrating some packages to
> > > > > > > > > debhelper 14. The issue I encountered when using sbuild was the lack
> > > > > > > of a
> > > > > > > > > debhelper 14 version in *backports*, although I believe this is
> > > > > > > feasible;
> > > > > > > > > there is an open bug and a recognized need for it. I am continuing to
> > > > > > > build
> > > > > > > > > the packages using an *unstable* (sid) *chroot*.
> > > > > > > > >
> > > > > > > > > And I’ll just add a comment that there is no urgency regarding this.
> > > > > > > >
> > > > > > > > FWIW, most of the things debhelper compat level 14 brings to the table
> > > > > > > > were already available in earlier versions, but you had to explicitly
> > > > > > > > tell debhelper that you want compat level 14, and then you had to
> > > > > > > > explicltly tell Lintian that, yes, debhelper handles more than Lintian
> > > > > > > > knows about. Basically, do the reverse of what this stunnel change does:
> > > > > > > >
> > > > > > > >
> > > > > > > https://salsa.debian.org/debian/stunnel/-/commit/52dfd6cef1da8b80e08b9f229e963252d872aad1
> > > > > > > >
> > > > > > > > Of course, you then have to check that earlier versions of debhelper
> > > > > > > > (like 13.31 in trixie-backports) can actually handle everything your
> > > > > > > > specific package wants to throw at it, but I hope this helps.
> > > > > > >
> > > > > > > Ah, sorry, that was silly of me: that was not the change I wanted to
> > > > > > > point to :) The stunnel change, while correct, does not really show
> > > > > > > all the Lintian overrides that I had to use before it learned about
> > > > > > > debhelper 14; this wmanager change is more like it:
> > > > > > >
> > > > > > > https://salsa.debian.org/debian/wmanager/-/commit/7c19fc477e22649a4aea5373a4902609813523fc
> > > > > >
> > > > > > However, the specific version of debhelper must be installed on the
> > > > > > machine. Otherwise, a build error will occur which would be a standard
> > > > > > issue up to this point.
> > > > >
> > > > > I don't understand what you mean... debhelper 13.31 is in trixie-backports?
> > > >
> > > > Sorry if I was unclear in my previous messages: the changes that
> > > > I linked to, the 13.15.2 -> 14 ones, are the ones that need to be
> > > > reverted if these particular packages should be backported.
> > > > I linked to them as examples of the differences, not as the exact
> > > > commits to make to your packages in order to backport them.
> > > >
> > > > G'luck,
> > > > Peter
> > > >
> > > > --
> > > > Peter Pentchev  roam@ringlet.net roam@debian.org peter@morpheusly.com
> > > > PGP key:        https://www.ringlet.net/roam/roam.key.asc
> > > > Key fingerprint 2EE7 A7A5 17FC 124C F115  C354 651E EFB0 2527 DF13
> > >
> > > The way you did it, one would expect an error during package building
> > > in sbuild; you specified `debhelper = 14`, and based on my analysis,
> > > the changes do not appear to be compatible with the version range (13
> > > to 14) specified in the control file (though that isn't the specific
> > > issue being analyzed here).
> >
> > The control file specifies debhelper (>> 13.15.2~), which matches
> > recent debhelper versions in both trixie-backports and unstable before
> > debhelper 14 was uploaded (and it also matches 14.x now :)). And then
> > the control file specifies X-DH-Compat: 14, which is supported in
> > debhelper 13.15 and later. So I really don't understand what
> > you mean here.
> >
> > Note that this is not some kind of experiment, I had these settings -
> > debhelper >> 13.15.2~ and X-DH-Compat: 14 - on literally dozens of
> > packages for years before debhelper 14.x hit the archive, and
> > everything worked just fine :)
> >
> > > However, the main point is this: I can
> > > build my packages normally in a Sid chroot without relying on sbuild
> > > in this context. The smoothest approach remains having the required
> > > version installed on the build machine using a host running
> > > Trixie/Debian stable so the build completes successfully.
> >
> > OK, so maybe I was confused when your very first sentence mentioned
> > the lack of debhelper 14 in backports; that's what I was trying to
> > help with - tell you how to adapt your packages so that the version of
> > debhelper in backports will be able to build them. Apologies if
> > that was not your intent :)
> 
> I am referring to what I saw in the commit you pushed to Salsa.
> 
> Your point makes sense, but I was referring specifically to the commit
> where you set the debhelper compatibility level to 14. Without a
> sufficiently recent version of debhelper, the build will fail.

...right, so it has a dependency on...

> On the other hand, if the functionality required by the package is
> already available since debhelper 13.15.2, using:
> 
> ```
> debhelper (>> 13.15.2~)
> ```

...a sufficiently recent version of debhelper. So no problem there.

> Would allow the package to build with any sufficiently recent
> debhelper version instead of requiring version 14 specifically.

Exactly, that's how it worked for years, and how it is documented to
work in the debhelper documentation.

> For example, Debian stable-backports currently provides debhelper 13.31~bpo13+1:
> https://packages.debian.org/source/stable-backports/debhelper
> 
> My concern is that compatibility level 14 introduces behavioral
> changes compared with level 13. Unless the package actually requires
> one of the features specific to compat 14, requiring it may introduce
> unnecessary compatibility issues or behavioral changes in the build.
> 
> Therefore, I think keeping the minimum required debhelper version,
> rather than requiring compat 14, would be safer if no
> compat-14-specific feature is needed.

Once again, I was trying to help you with, and this is a direct quote
from your e-mail, "migrating some packages to debhelper 14". I assumed
that you meant that you *wanted* the debhelper 14 compat features.
If you did not want them, then I must have misunderstood what you wrote :)

(just to be clear: I am one of those weird people that sometimes try
new debhelper features while they are still in beta, hence the use of
X-DH-Compat instead of debhelper-compat, and the Lintian overrides
before debhelper 14.x hit the archive)

Anyway, I think we've sorted things out now :)

G'luck,
Peter

-- 
Peter Pentchev  roam@ringlet.net roam@debian.org peter@morpheusly.com
PGP key:        https://www.ringlet.net/roam/roam.key.asc
Key fingerprint 2EE7 A7A5 17FC 124C F115  C354 651E EFB0 2527 DF13

Attachment: signature.asc
Description: PGP signature


Reply to: