guix archive --export broken on foreign distro

  • Done
  • quality assurance status badge
Details
2 participants
  • Lars-Dominik Braun
  • Ludovic Courtès
Owner
unassigned
Submitted by
Lars-Dominik Braun
Severity
important
L
L
Lars-Dominik Braun wrote on 1 Oct 2020 13:22
(address . bug-guix@gnu.org)
20201001112245.GA3101@zpidnp36
Hi,

as discussed on IRC [1][2] `guix archive --export` is currently broken on
foreign distributions. It fails with the error message:

guix archive: error: corrupt input while restoring archive from #<closed: file 7f27c396e150>

strace reveals `guix authenticate` prints a message to stderr, which the
guix-daemon does not expect:

guile: warning: failed to install locale

Installing the package glibc-locales into root’s user profile (because
guix-daemon.service references that) and restarting the daemon solves the
issue.


Cheers,
Lars

-----BEGIN PGP SIGNATURE-----

iQGzBAABCgAdFiEEyk+M9DfXR4/aBV/UQhN3ARo3hEYFAl91vAEACgkQQhN3ARo3
hEblcgwAxclbFtFdcOQNxnGsnlpQHNz2hDncerg/daW477sj+JpJdR/+xYNumOEz
UEIrxSz7nKWuMY5JljmiITUlgzgDawKpwXswbO9Hjnta6WAyYP7sjULHTp9m6qyH
YCHxT7IS8wFj87/o8yDIonIFDshckoiIBi+PbqRvkplLp3YwZYLvrx7PC2fh5lAN
v9dCMAjZwqCfPA1OnBWy86v3IzjTMdrEnA89uaWPPGMV4l9Xy7L4YZiMxTK7RycC
HWDfXcMNv48+kOGCbrBTcUnacjSSOg0fKRgLCv/M9nIc5zdp14hK8lYjkS2GtWHD
lhQ9eNqDIx+JKNobPo2mYfIHuidV9KQv7HxtYp+j5IzqvsS6aTAokPX5DsgNM8Cr
IMb3BOqdNqqUHtRz4lc1bHpx4l2m5n8rNdMtWMNgI+fsh/aFJhKcVffUNGgP5JRO
/F7sVfRnthjwy1WtPcCVdCnVZaPBZt31ngHO7rxU/8ctehY0wamegDHS6FnD0e/Q
FC9dLJZR
=m4DE
-----END PGP SIGNATURE-----


L
L
Ludovic Courtès wrote on 1 Oct 2020 17:56
(name . Lars-Dominik Braun)(address . ldb@leibniz-psychology.org)(address . 43739@debbugs.gnu.org)
87lfgqq6rf.fsf@gnu.org
Hi,

Lars-Dominik Braun <ldb@leibniz-psychology.org> skribis:

Toggle quote (10 lines)
> as discussed on IRC [1][2] `guix archive --export` is currently broken on
> foreign distributions. It fails with the error message:
>
> guix archive: error: corrupt input while restoring archive from #<closed: file 7f27c396e150>
>
> strace reveals `guix authenticate` prints a message to stderr, which the
> guix-daemon does not expect:
>
> guile: warning: failed to install locale

Specifically, the problem occurs after the change in
64cf660f872fb7aaf0d2b463e45b4c756297f743: on the first call to
‘readAuthenticateReply’, the daemon gets a “g” (from the warning above)
instead of a digit as the protocol expects.

Part of the problem is that ‘Agent’ captures stderr in addition to
stdout, which is useful for ‘guix offload’ but a bad idea for ‘guix
authenticate’.

Toggle quote (2 lines)
Yup, part of the motivation came from this bug report.

Thanks!

Ludo’.
L
L
Ludovic Courtès wrote on 1 Oct 2020 22:16
control message for bug #43739
(address . control@debbugs.gnu.org)
87h7rdn1lm.fsf@gnu.org
severity 43739 important
quit
L
L
Ludovic Courtès wrote on 6 Oct 2020 14:27
Re: bug#43739: guix archive --export broken on foreign distro
(name . Lars-Dominik Braun)(address . ldb@leibniz-psychology.org)(address . 43739-done@debbugs.gnu.org)
87ft6rv8st.fsf@gnu.org
Hi,

Ludovic Courtès <ludo@gnu.org> skribis:

Toggle quote (17 lines)
> Lars-Dominik Braun <ldb@leibniz-psychology.org> skribis:
>
>> as discussed on IRC [1][2] `guix archive --export` is currently broken on
>> foreign distributions. It fails with the error message:
>>
>> guix archive: error: corrupt input while restoring archive from #<closed: file 7f27c396e150>
>>
>> strace reveals `guix authenticate` prints a message to stderr, which the
>> guix-daemon does not expect:
>>
>> guile: warning: failed to install locale
>
> Specifically, the problem occurs after the change in
> 64cf660f872fb7aaf0d2b463e45b4c756297f743: on the first call to
> ‘readAuthenticateReply’, the daemon gets a “g” (from the warning above)
> instead of a digit as the protocol expects.

This is fixed by 880fe019ae64df37815bbdb1a22305f99dae759d from

Closing.

Thanks,
Ludo’.
Closed
?
Your comment

This issue is archived.

To comment on this conversation send an email to 43739@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 43739
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch