Yeah; this should be an upstream change to the control generator ideally otherwise we're going to lose them (or manually need to track) on the next refresh.
Could you point out which ones had problems? I recently brought 2.0.20 back to trixie-backports without a problem, I'm surprised that 2.1.1 had problems. On Mon, Mar 30, 2026 at 10:53 AM Christoph Biedl <[email protected]> wrote: > > Source: fwupd > Version: 2.1.1-1 > Severity: wishlist > X-Debbugs-Cc: [email protected] > > Dear maintainer, > > for reasons I wanted to backport fwupd but got a hard time from the > unversioned build dependencies: While at first it seemed they could be > met easily, the actual build failed several times as the versions of the > build dependencies are checked later, when checking the definitions in > meson.build. > > Please add versions to the build dependencies in debian/control. > Initially, I was about to provide a patch for this as the information > can be extracted from meson.build with likely some handwork. But then I > realized there's a generator for debian/control, being > contrib/ci/generate_debian.py - so possibly this is something for > upstream, and this will need an enhancement for versioned dependencies. > In my opinion that's sensible to do anyway. > > Christoph > > -- System Information: > Debian Release: forky/sid > APT prefers unstable > APT policy: (500, 'unstable') > Architecture: amd64 (x86_64) > > Kernel: Linux 6.12.68 (SMP w/8 CPU threads) > Kernel taint flags: TAINT_WARN > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not > set > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > -- Mario Limonciello [email protected]
