smoser
commented
7 hours ago OK. Here is a simple recreate that throws out the red-herring of a self-dependent package or the bootstrap archive.
-
test-me-dep.yaml
package: name: test-me-dep version: 1.0 epoch: 0 environment: contents: packages: - busybox pipeline: - runs: | printf '#!/bin/busybox sh\necho hello world\n' > greet-me install -D -m755 -t "${{targets.contextdir}}/usr/bin" greet-me -
test-me.yaml
package: name: test-me version: 1.0 epoch: 0 environment: contents: packages: - busybox - test-me-dep pipeline: - runs: | mkdir ${{targets.contextdir}}/etc greet-me > ${{targets.contextdir}}/etc/greeting
Then from the wolfi-dev/os tree (commit listed above)
$ rm -Rf ~/.cache/dev.chainguard.go-apk/
$ make clean
$ make package/test-me-dep
$ rm packages/x86_64/test-me-dep-1.0-r0.apk
$ make package/test-me
melange build test-me.yaml --repository-append /home/user/src/wolfi-os/packages
--keyring-append local-melange.rsa.pub --signing-key local-melange.rsa
--arch x86_64 --env-file build-x86_64.env --namespace wolfi
--license 'Apache-2.0'
--git-repo-url 'https://github.com/wolfi-dev/os'
--generate-index false
--pipeline-dir ./pipelines/
-k https://packages.wolfi.dev/os/wolfi-signing.rsa.pub
-r https://packages.wolfi.dev/os
2024/11/14 10:37:19 INFO git commit for build config not provided, attempting to detect automatically
2024/11/14 10:37:19 WARN SOURCE_DATE_EPOCH is specified but empty, setting it to 1969-12-31 19:00:00 -0500 EST
2024/11/14 10:37:19 INFO melange is building:
2024/11/14 10:37:19 INFO configuration file: test-me.yaml
2024/11/14 10:37:19 INFO workspace dir: /home/user/tmp/melange-workspace-496249841
2024/11/14 10:37:19 INFO evaluating pipelines for package requirements
2024/11/14 10:37:19 INFO --cache-dir ./melange-cache/ not a dir; skipping
2024/11/14 10:37:19 INFO populating workspace /home/user/tmp/melange-workspace-496249841 from ./test-me/
2024/11/14 10:37:19 INFO building workspace in '/home/user/tmp/melange-guest-3256530904' with apko
2024/11/14 10:37:19 INFO setting apk repositories: [/home/user/src/wolfi-os/packages https://packages.wolfi.dev/os]
2024/11/14 10:37:19 INFO image configuration:
2024/11/14 10:37:19 INFO contents:
2024/11/14 10:37:19 INFO build repositories: []
2024/11/14 10:37:19 INFO runtime repositories: []
2024/11/14 10:37:19 INFO keyring: []
2024/11/14 10:37:19 INFO packages: [busybox test-me-dep]
2024/11/14 10:37:19 INFO accounts:
2024/11/14 10:37:19 INFO runas:
2024/11/14 10:37:19 INFO users:
2024/11/14 10:37:19 INFO - uid=1000(build) gid=1000
2024/11/14 10:37:19 INFO groups:
2024/11/14 10:37:19 INFO - gid=1000(build) members=[build]
2024/11/14 10:37:19 INFO auth configured for: []
2024/11/14 10:37:19 INFO installing ca-certificates-bundle (20241010-r2)
2024/11/14 10:37:19 INFO installing wolfi-baselayout (20230201-r15)
2024/11/14 10:37:19 INFO installing glibc (2.40-r3)
2024/11/14 10:37:19 INFO installing ld-linux (2.40-r3)
2024/11/14 10:37:19 INFO installing libgcc (14.2.0-r5)
2024/11/14 10:37:19 INFO installing glibc-locale-posix (2.40-r3)
2024/11/14 10:37:19 INFO installing libxcrypt (4.4.36-r8)
2024/11/14 10:37:19 INFO installing libcrypt1 (2.40-r3)
2024/11/14 10:37:19 INFO installing busybox (1.37.0-r0)
<hang here>
^C
2024/11/14 10:38:42 INFO deleting guest dir /home/user/tmp/melange-guest-3256530904
2024/11/14 10:38:42 INFO deleting workspace dir /home/user/tmp/melange-workspace-496249841
2024/11/14 10:38:42 ERRO failed to build package:
unable to build guest: unable to generate image:
installing apk packages: installing packages:
expanding test-me-dep (ver:1.0-r0 arch:x86_64):
fetching package "test-me-dep":
failed to read repository package apk /home/user/src/wolfi-os/packages/x86_64/test-me-dep-1.0-r0.apk:
open /home/user/src/wolfi-os/packages/x86_64/test-me-dep-1.0-r0.apk:
no such file or directory: context canceled
make[1]: *** [Makefile:125: packages/x86_64/test-me-1.0-r0.apk] Error 1
make: *** [Makefile:115: package/test-me] Interrupt
This is quite possibly in the realm of user error or "don't do that".
I got my wolfi-dev/os tree into a state that would not build packages.
Here should be enough information to recreate.
Note: ncurses does depend on itself.
I prettied-up the output a bit of the final ERROR message (after the ctrl-c). It actually does give a reasonable error, but I dont' know that I've ever read error messages of a program after hitting ctrl-c, so I feel justified in my lost time debugging why it was hung.