Your message dated Sun, 1 Dec 2024 13:51:19 +0100
with message-id <[email protected]>
and subject line Re: #882056: sbuild: Benign failures when sbuilding to ubuntu
14.04
has caused the Debian Bug report #882056,
regarding sbuild: Benign failures when sbuilding to ubuntu 14.04
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
882056: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882056
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: sbuild
Version: 0.73.0-4
Severity: wishlist
This has more to do with Ubuntu than Debian, but it'd be really nice if
it was fixed.
Running an sbuild to build packages in an ubuntu 14.04 chroot from
Debian/sid (normal build; no cross-build or multiarch or anything) I see
these issues:
+-------------------------------------+
| Install package build dependencies |
+-------------------------------------+
Setup apt archive
-----------------
Merged Build-Depends: debhelper (>= 9), mrbuild (>= 0.51), dh-python,
python-all-dev, libminimath-dev, libdogleg-dev, libopencv-calib3d-dev,
python-numpy
Filtered Build-Depends: debhelper (>= 9), mrbuild (>= 0.51), dh-python,
python-all-dev, libminimath-dev, libdogleg-dev, libopencv-calib3d-dev,
python-numpy
grep: debian/control: No such file or directory
/usr/bin/pkgsanitychecks: Error: not in source package directory
/usr/bin/pkgstripfiles: Error: not in source package directory
These are scary-looking, but benign errors. Apparently ubuntu's dpkg-deb
tool is a shell script (unlike the ELF executable in Debian). Sbuild is
trying to "dpkg-deb build dir something.deb". The directory dir contains
only a DEBIAN subdirectory, but ubuntu's dpkg-deb is trying to grep
debian/control. Maybe this has nothing to do with sbuild.
These prints happen a few times through the build.
Second issue is that the dose3 invocation fails to report on the broken
dependencies. The log shows this:
Preparing to unpack
.../sbuild-build-depends-dose3-dummy_0.invalid.0_amd64.deb ...
Unpacking sbuild-build-depends-dose3-dummy (0.invalid.0) ...
Setting up sbuild-build-depends-dose3-dummy (0.invalid.0) ...
E: Command line option --format is not understood
(I)Boilerplate: Parsing and normalizing...
(I)Packages: Parsing Packages file -...
E: Invalid operation cat-file
(I)Format822: total packages 0
(I)Format822: total packages 0
(I)Packages: Merging status file
(I)Packages: Merging status file
(I)Distcheck: --checkonly specified, consider all packages as background
packages
(I)Distcheck: Solving...
report:
background-packages: 0
foreground-packages: 0
total-packages: 0
It'd be good to at least print more useful things when it fails this
way.
There were a few more problems for which I have patches... in the
imminent bug report.
--- End Message ---
--- Begin Message ---
Sometime in 2017...
> Apparently ubuntu's dpkg-deb
> tool is a shell script (unlike the ELF executable in Debian). Sbuild is
> trying to "dpkg-deb build dir something.deb". The directory dir contains
> only a DEBIAN subdirectory, but ubuntu's dpkg-deb is trying to grep
> debian/control. Maybe this has nothing to do with sbuild.
I doubt there is anything actionable on the sbuild side here, and
Ubuntu's dpkg-deb seems to be the normal dpkg-deb binary nowadays.
Thus, closing. If there is something left to do, please describe
that + reopen.
Best,
Chris
--- End Message ---
