Your message dated Fri, 17 Oct 2025 13:39:13 -0700
with message-id
<CAOU6tACAxFKJ3qNAPTUjrPfTuEt=b_gF58ZVuDX+84gzBJ=p...@mail.gmail.com>
and subject line Re: Bug#1111913: debcraft: miscellaneous issues
has caused the Debian Bug report #1111913,
regarding debcraft: ERROR: failed to solve: failed to read
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.)
--
1111913: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1111913
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: debcraft
Version: 0.5.0
Severity: normal
X-Debbugs-Cc: [email protected]
I'm trying to evaluate debcraft as an option for Debian package building
and thus far came across 2 observations.
```
❯ debcraft build bpfcc_0.31.0+ds-7.dsc --build-arg HOST_ARCH=arm64
Building container 'debcraft-debian-sid' in
'/tmp/tmp.jctgXKrIdX/debcraft-container' for downloader use
mkdir: created directory '/tmp/tmp.jctgXKrIdX/debcraft-container'
WARN[0000] missing "HOST_ARCH" build argument. Try adding "--build-arg
HOST_ARCH=<VALUE>" to the command line
STEP 1/14: FROM debian:sid
STEP 2/14: ARG HOST_ARCH
```
debcraft reports about option `--build-arg` but such an option doesn't
seem to be available/documented.
Then, when trying to simply build a .dsc, it failed with:
```
Successfully tagged localhost/debcraft-debian-sid:latest
49a1bf1a5b19ef59d935cac7d35329f72d6d7264e93373311c6c2b690f339b5f
Unpack bpfcc_0.31.0+ds-7.dsc and associated Debian and source tar packages with
'dpkg-source'
usage: sopv-gpgv inline-verify [-h] [--debug] [--not-before TIMESTAMP]
[--not-after TIMESTAMP]
[--verifications-out VERIFICATIONS]
CERTS [CERTS ...]
sopv-gpgv inline-verify: error: the following arguments are required: CERTS
dpkg-source: warning: cannot verify inline signature for
./bpfcc_0.31.0+ds-7.dsc: error code 2
dpkg-source: info: extracting bpfcc in bpfcc-0.31.0+ds
dpkg-source: error: unpack target exists: bpfcc-0.31.0+ds
DEBCRAFT ERROR: Downloading package 'bpfcc_0.31.0+ds-7.dsc' failed
```
The same package and the same sources built fine when, instead of
providing .dsc file argument, I simply unpacked the sources and
triggered the build with just `debcraft build <unpacked source folder>`
```
COMMIT debcraft-bpfcc-debian-sid
--> 6eb9f5f74821
Successfully tagged localhost/debcraft-bpfcc-debian-sid:latest
6eb9f5f7482113c370da0d5d25719cf2ba4a6f2299b9adc0609b72010cc07ecd
Building package at /var/tmp/debcraft-build-bpfcc-1755962453
```
Other than that, I found the documentation quite limited. Like, how do I
go about using ccache, or do cross buildling utilizing qemu based
virtualization. I'd also prefer to inject package installs, like ccache
and auto-apt-proxy for efficiency. But I couldn't find much pointers.
-- System Information:
Debian Release: forky/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.12.38+deb13-amd64 (SMP w/6 CPU threads; PREEMPT)
Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8), LANGUAGE=C
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages debcraft depends on:
ii podman 5.4.2+ds1-2+b1
debcraft recommends no packages.
debcraft suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
I am not able to reproduce the issue "debcraft: ERROR: failed to
solve: failed to read" that was the original topic of this bug report.
The `sopv-gpgv inline-verify` error is a separate issue and seems to
stem from how new versions of dpkg uses sopv-gpgv instead of old
venerable gpg, see details in
https://bugs.debian.org/cgi-bin/bugreport.cgi. bug=1111617. It seems
also that there is no workaround to be done in Debcraft, so no
actionable items here.
I am thus closing this bug on Debcraft as not reproducible anymore.
Feel free to file new bug reports on new issues, and please include
steps to reproduce so I can easily investigate and fix them.
--- End Message ---
