rrahl0
commented
5 months ago this is an example, which works with tar_scm but not obs_scm:
[ 294s] Compiling env_logger v0.11.3
[ 296s] error: failed to run custom build command for `cosmic-files v0.1.0 (/home/abuild/rpmbuild/BUILD/cosmic-files-0.1.0+git20240531.4a7c59b)`
[ 296s]
[ 296s] Caused by:
[ 296s] process didn't exit successfully: `/home/abuild/rpmbuild/BUILD/cosmic-files-0.1.0+git20240531.4a7c59b/target/release/build/cosmic-files-2cd4a19b5e5fecd7/build-script-build` (exit status: 1)
[ 296s] --- stdout
[ 296s] cargo:rerun-if-changed=i18n
[ 296s] cargo:rerun-if-env-changed=VERGEN_GIT_COMMIT_DATE
[ 296s] cargo:rerun-if-env-changed=VERGEN_GIT_SHA
[ 296s]
[ 296s] --- stderr
[ 296s] Error: not within a suitable 'git' worktree!
[ 296s] warning: build failed, waiting for other jobs to finish...
[ 317s] error: Recipe `build-debug` failed on line 41 with exit code 101
[ 317s] error: Bad exit status from /var/tmp/rpm-tmp.bvFIR4 (%build)
[ 317s]
[ 317s] RPM build errors:
[ 317s] Bad exit status from /var/tmp/rpm-tmp.bvFIR4 (%build)
[ 317s] ### VM INTERACTION START ###
[ 317s] [ 312.930692][ T1] sysrq: Power Off
[ 317s] [ 312.931422][ T8] reboot: Power down
[ 318s] ### VM INTERACTION END ###
[ 318s]
[ 318s] i01-ch2d failed "build cosmic-files.spec" at Mon Jun 3 18:33:02 UTC 2024.
[ 318s]
When I try to use obs_scm with package-meta, something goes awry, as the meta does get added, but when I try to build different packages (like network:vpn/tailscale or home:rrahl0:COSMIC/cosmic-files) git errors out.
With the cosmic packages I do have at least the workaround of using tar_scm, which for some reason works.
tailscale seems to be more finicky, as even tar_scm doesn't work. My workaround for now is to spin up a Leap VM and run the services in Leap (have to file another bug as leap distrobox encounters different bugs)