Cannot build udeb with debhelper 13.6ubuntu1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
debhelper (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Hi,
I'm trying to rebuild a traditional server installer, therefore I've to build Debian-Installer udeb Packages. But this does not work with debhelper 13.6ubuntu1 on the actual ubuntu 22.04 prerelease. I found the root cause: It's ubuntu specific patch on debhelper described in debian changelog as "Imply '<!noudeb>' profile if not set on package type udeb". I reverted that patch and now the build of udebs works again.
Greetings,
André
#######
Reverting the buggy ubuntu specific patch
#######
--- Dh_Lib.pm.orig 2022-03-22 21:27:31.984788688 +0100
+++ Dh_Lib.pm 2022-03-22 21:27:51.352850840 +0100
@@ -1974,9 +1974,6 @@
}
$package_
- if ($package_
- $build_profiles = '<!noudeb>';
- }
$package_
$package_
$package_
#######
Howto reproduce the bug:
#######
$wget http://
$wget http://
$dpkg-source -x partman-
$cd partman-
$dpkg-buildpackage -us -uc -A
dpkg-buildpackage: info: source package partman-auto-raid
dpkg-buildpackage: info: source version 47
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Holger Wansing <email address hidden>
dpkg-source --before-build .
fakeroot debian/rules clean
dh clean --with d-i
dh: warning: No packages to build. Possible architecture mismatch: amd64, want: all
debian/rules build-indep
dh build-indep --with d-i
dh: warning: No packages to build. Possible architecture mismatch: amd64, want: all
fakeroot debian/rules binary-indep
dh binary-indep --with d-i
dh: warning: No packages to build. Possible architecture mismatch: amd64, want: all
dpkg-genbuildinfo --build=all -O../partman-
dpkg-genbuildinfo: error: binary build with no binary artifacts found; .buildinfo is meaningless
dpkg-buildpackage: error: dpkg-genbuildinfo --build=all -O../partman-
#######
After applying my patch, i.e. reverting the ubuntu specific patch
#######
$wget http://
$wget http://
$dpkg-source -x partman-
$cd partman-
$dpkg-buildpackage -us -uc -A
dpkg-buildpackage: info: source package partman-auto-raid
dpkg-buildpackage: info: source version 47
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Holger Wansing <email address hidden>
dpkg-source --before-build .
fakeroot debian/rules clean
dh clean --with d-i
dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
dh_di_
dh_clean
dh_clean: warning: Compatibility levels before 10 are deprecated (level 9 in use)
debian/rules build-indep
dh build-indep --with d-i
dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
dh_di_
dh_update_
fakeroot debian/rules binary-indep
dh binary-indep --with d-i
dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
dh_testroot -i
dh_prep -i
dh_auto_install --destdir=
dh_auto_install: warning: Compatibility levels before 10 are deprecated (level 9 in use)
dh_install -i
dh_install: warning: Compatibility levels before 10 are deprecated (level 9 in use)
dh_di_
dh_di_numbers -i
dh_di_numbers: warning: Compatibility levels before 10 are deprecated (level 9 in use)
dh_installdocs -i
dh_installdocs: warning: Compatibility levels before 10 are deprecated (level 9 in use)
dh_installch
dh_installde
dh_perl -i
dh_link -i
dh_strip_
dh_compress -i
dh_compress: warning: Compatibility levels before 10 are deprecated (level 9 in use)
dh_fixperms -i
dh_missing -i
dh_missing: warning: Compatibility levels before 10 are deprecated (level 9 in use)
dh_installdeb -i
dh_gencontrol -i
dh_md5sums -i
dh_builddeb -i
dpkg-deb: building package 'partman-auto-raid' in 'debian/
Renaming partman-
dpkg-genbuildinfo --build=all -O../partman-
dpkg-genchanges --build=all -O../partman-
dpkg-genchanges: info: binary-only arch-indep upload (source code and arch-specific packages not included)
dpkg-source --after-build .
dpkg-buildpackage: info: source-only upload: Debian-native package
Nobody reads these bug reports ...
There might be a small chance to have somebody react if you follow all of the steps in https:/ /packaging. ubuntu. com/html/ fixing- a-bug.html and/or tag the one who introduced the patch in the first place