On 2023-07-15, Martin Monperrus wrote: > Version: 1.3.0-4 This is a quite old version of guix already, stable has 1.4.0-3...
> Systemd job `guix-publish.service` fails with > > ``` > systemd[1]: guix publish: error: open-file: No such file or directory: > "/etc/guix/signing-key.pub" > systemd[1]: guix-publish.service: Main process exited, code=exited, > status=1/FAILURE > systemd[1]: guix-publish.service: Failed with result 'exit-code'. > ``` This is not a great default behavior, agreed! I have noticed this issue in the past and not quite gotten around to figuring out what to do about it. > Workaround: > > call `guix archive --generate-key` manually to create "/etc/guix/signing- > key.pub". this should be part of the Deb package installation script. I think it would be better if guix-publish was not enabled by default, as this matches the defaults of Guix System upstream and I *think* also guix installed from script on a foreign distro. Some instructions on how to enable it could be added to README.Debian, including mentioning generating the key. > -- System Information: > Debian Release: bookworm/sid > APT prefers jammy-updates > APT policy: (500, 'jammy-updates'), (500, 'jammy-security'), (500, > 'jammy'), (100, 'jammy-backports') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 This seems like some hybrid Debian and Ubuntu system, which is as far as I know is unsupported on both Debian and Ubuntu... That said, I can confirm the issue is present on regular Debian install as well.. live well, vagrant
signature.asc
Description: PGP signature
