Package: debcraft
Version: 0.5.0
Followup-For: Bug #1111913
X-Debbugs-Cc: [email protected]
I think the `.dsc` mode argument for build is broken and/or not well
tested.
```
❯ debcraft build bpfcc_0.31.0+ds-7.dsc
DEBCRAFT WARNING: No previous Debcraft container was found and thus the first
run of
DEBCRAFT WARNING: this tool is expected to be slow as the container base layer
needs
DEBCRAFT WARNING: to be built. Re-runs of Debcraft will be fast.
Building container 'debcraft-debian-sid' in
'/tmp/tmp.9fhFRw2Uk5/debcraft-container' for downloader use
mkdir: created directory '/tmp/tmp.9fhFRw2Uk5/debcraft-container'
[+] Building 0.1s (1/1) FINISHED
docker:default
=> [internal] load build definition from Dockerfile
0.1s
=> => transferring dockerfile: 2B
0.0s
ERROR: failed to solve: failed to read dockerfile: open Dockerfile: no such
file or directory
DEBCRAFT ERROR: Container build failed - see output above for details
```
The same, instead, if I unpack the sources and build from the source
directory, I get the below:
```
/var/tmp/bpfcc-0.31.0+ds
13:50:55
❯ debcraft build
DEBCRAFT WARNING: No previous Debcraft container was found and thus the first
run of
DEBCRAFT WARNING: this tool is expected to be slow as the container base layer
needs
DEBCRAFT WARNING: to be built. Re-runs of Debcraft will be fast.
Running in path /var/tmp/bpfcc-0.31.0+ds that has Debian package sources for
'bpfcc'
Use 'docker' container image 'debcraft-bpfcc-debian-sid' for package 'bpfcc'
Building container 'debcraft-bpfcc-debian-sid' in
'/var/tmp/debcraft-container-bpfcc' for build ID '1757492459'
mkdir: created directory '/var/tmp/debcraft-container-bpfcc'
[+] Building 11.6s (6/22)
docker:default
=> [internal] load build definition from Containerfile
0.1s
=> => transferring dockerfile: 3.74kB
0.0s
=> [internal] load metadata for docker.io/library/debian:sid
4.2s
=> [auth] library/debian:pull token for registry-1.docker.io
0.0s
=> [internal] load .dockerignore
0.0s
=> => transferring context: 2B
0.0s
=> CANCELED [ 1/17] FROM
docker.io/library/debian:sid@sha256:a83aa6a568106eba94002 7.3s
=> => resolve
docker.io/library/debian:sid@sha256:a83aa6a568106eba94002d568df61b5f 0.0s
=> => sha256:a83aa6a568106eba94002d568df61b5fc23f22f8298fd47d2fc4d 9.58kB /
9.58kB 0.0s
=> => sha256:5d48851238b842b2199e95e09a666b3e83eb859eef0cf03c8be23 1.02kB /
1.02kB 0.0s
=> => sha256:6f2ffb0d96768103002904e9828717189cf1f5b16e38f1f04629f6330 448B /
448B 0.0s
=> => sha256:8d64c6c7c21822ac171c4c396d70161707401d6d50d133075d6 49.66MB /
49.66MB 5.9s
=> => extracting
sha256:8d64c6c7c21822ac171c4c396d70161707401d6d50d133075d661956f0 1.1s
=> [internal] load build context
0.0s
=> => transferring context: 35.60kB
0.0s
```
I hope this provides you with enough pointers to nail the issue.
Also, I really liked the idea of debcraft, using the Docker backend for
build. I hope, overtime, the issues are all hashed out and debcraft
becomes more resilient. Just that I couldn't investigate more, given my
personal limited time, otherwise I'd have helped with more information.
-- System Information:
Debian Release: forky/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.16.3+deb14-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 docker.io 26.1.5+dfsg1-9+b9
debcraft recommends no packages.
debcraft suggests no packages.
-- no debconf information
