Andreas Enge writes:
>> I am still curious what happened before, in case the previous error
>> appears again.
>
> Other people have experienced the same problem; apparently it was a bug
> that has been fixed in the meantime. So as "guix pull" finally succeeded,
> you should not see it again.
Oka
Hello Simon,
Am Wed, Mar 31, 2021 at 09:53:20AM +0200 schrieb Simon Josefsson via:
> Minutes after posting the above, 'guix pull' works again after having
> been broken in the above way for at least a week. I never realized that
> asking for help on this list would solve things this quickly! See
Simon Josefsson via writes:
> Hi. I have a machine that have been running Guix for a couple of years
> and since November I rely on unattended-upgrades to keep it updated. I
> have stopped doing manual upgrades but may have done it on reflex a
> couple of times since November. Now when I run '
guix-command:
Throw to key `bad-response' with args `("Bad Response-Line: ~s" (""))'.
substitution of /gnu/store/nvx8kkadjl81k5h544y4kahz6jlzqqyl-guix-system-tests
failed
guix pull: error: corrupt input while restoring archive from #
root@hamster ~#
unattended-upgrade-logs.tar.bz2
Description: Binary data
signature.asc
Description: PGP signature
guix-command:
Throw to key `bad-response' with args `("Bad Response-Line: ~s" (""))'.
substitution of /gnu/store/nvx8kkadjl81k5h544y4kahz6jlzqqyl-guix-system-tests
failed
guix pull: error: corrupt input while restoring archive from #
root@hamster ~#
unattended-upgrade-logs.tar.bz2
Description: Binary data
signature.asc
Description: PGP signature