[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: guix pull error : In procedure make_objcode_from_file: object file t
From: |
tk0 |
Subject: |
Re: guix pull error : In procedure make_objcode_from_file: object file too small (0 bytes) |
Date: |
Tue, 26 Jul 2016 06:27:11 -0400 |
Sent from
ProtonMail, Swiss-based encrypted email.
-------- Original Message --------
Subject: Re: guix pull error : In procedure make_objcode_from_file: object file too small (0 bytes)
Local Time: 25 July 2016 9:49 PM
UTC Time: 25 July 2016 20:49
From: address@hidden
To: address@hidden
CC: address@hidden
Hi,
tk0 <address@hidden> skribis:
> After having to roll back from a weird situation -- in which guix developed a problem mounting my virtual filesystem at boot -- doing a 'guix pull' produces the following error:
Could you send the whole ‘guix pull’ output, so we see the context?
Does the error systematically happen?
Thanks in advance,
Ludo’.
Hi Ludo' ,
Sorry for the delay, it was the somewhat tricky to reproduce what led to the error since the 'guix system' command got disabled and the old vm became useless. Now, I made a new image and experimented a bit.
The initial problem was that I have added the '9p' filesystem (this is used for path sharing between the guest and the host in a kvm setup) to the config file without setting the 'check?' field to #f . On next reboot, the 'fsck' failed to the Bourneish shell since there is no fsck.9p. I have managed login into the system by ',q'-tting my way out of a cascade of Bournish Guile REPLs, however, once i logged in, the guix system command was exiting with the 'command not found' so I could not reconfigure to an operative state.
Interestingly, I have tried to roll-back to a previously functioning state in the grub menu, but despite succeeding to login without errors, the 'system' command of guix was still unavailable. I guess this means that the roll-back wasn't purely functional and state-free. The 'guix pull' problem described initially seems to be only a symptom.
Now that I laid out the full problem, please let me know if you need any more diagnostics.
All the best,
tk