Thursday, July 5, 2018

Stop using debhelper 9 for new package updates?

This question keeps on coming up on packages I'm working on updating. I'd thought about not bumping the debhelper version from 9 to 10 on such packages until later but now I'm not so sure it's necessary. I'd thought that it would be useful to do it that way to facilitate package backports but the most likely backports in Debian would be to Stretch (Debian v9), which currently has version 10.2.5; and Jessie (Debian v8) where v10.2.5~bpo8+1 is currently in jessie-backports.  For Ubuntu: Bionic (18.04 LTS) already has v11.3.5 while Xenial (16.04 LTS) has 10.2.2ubuntu1~ubuntu16.04.1 in xenial-backports.  In both of the backport cases, packages can be built (using different methods) with the appropriate backports repository included.
As can be seen from that as well as the current package details beyond the fold;  the actual current debhelper version is 11, so bumping the version just to 10 will allow bringing the version more up-to-date but still allow backporting to fairly recent Debian or Ubuntu release versions.

 Package debhelper - helper programs for debian/rules.

 - Current versions in Debian:
wheezy (oldoldstable) (devel): 9.20120909: all
jessie (oldstable) (devel):9.20150101+deb8u2: all
jessie-backports (devel): 10.2.5~bpo8+1: all
stretch (stable) (devel): 10.2.5: all
stretch-backports (devel):11.3.2~bpo9+2: all
buster (testing) (devel): 11.3.5: all
sid (unstable) (devel):11.3.5: all

  - Current versions in Ubuntu:
trusty (14.04LTS) (devel): 9.20131227ubuntu1: all
xenial (16.04LTS) (devel): 9.20160115ubuntu3: all
xenial-backports (devel):10.2.2ubuntu1~ubuntu16.04.1: all
artful (17.10) (devel):10.7.2ubuntu2: all
bionic (18.04LTS) (devel)11.1.6ubuntu1: all
bionic-updates (devel): 11.1.6ubuntu2: all
cosmic (devel): 11.3.2ubuntu1: all