[Bug 1965758] Re: [BPO] debhelper/13.6ubuntu1 from jammy to bionic, focal

Thomas Ward 1965758 at bugs.launchpad.net
Mon Mar 21 13:37:16 UTC 2022


waveform: Paride: given this bug, wouldn't this be more suited for full
SRU and rebuilds?  I'm wondering whether this is truly a backportable
case because this requires rebuild of all affected packages, and if
anyone builds with debhelper in backports (which is NOT available in
standard build envs I believe easily) that will lead to the upgrade
breakage.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to debhelper in Ubuntu.
https://bugs.launchpad.net/bugs/1965758

Title:
  [BPO] debhelper/13.6ubuntu1 from jammy to bionic, focal, impish

Status in debhelper package in Ubuntu:
  Fix Released
Status in debhelper source package in Bionic:
  New
Status in debhelper source package in Focal:
  New
Status in debhelper source package in Impish:
  New

Bug description:
  Please backport debhelper (>= 13.6ubuntu1) to Bionic and Focal.
  Currently we have

   debhelper | 13.5.2ubuntu1~bpo18.04.1    | bionic-backports | source, all
   debhelper | 13.5.2ubuntu1~bpo20.04.1    | focal-backports  | source, all

  Those versions are affected by LP: #1959054, which is fixed in
  13.6ubuntu1. Especially bad about that bug is that it requires
  rebuilding packages which were built against the buggy debhelper to
  update their maintainer scripts.

  I'm not preparing the upload myself as [1] specifies debhelper is
  handled by the Backports team.

  [1] https://wiki.ubuntu.com/UbuntuBackports#Special_Cases

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/1965758/+subscriptions




More information about the foundations-bugs mailing list