On Wed, 2021-03-17 at 19:03 +, Charles Jackson via Bug reports for GNU Guix
wrote:
> I think the system was broken, and I have since deleted the VM.
> This is likely not a bug and can probably be dropped.
For what it is worth now the VM has been deleted: the backtrace
is in the HTTP code of
Sorry about the screen shots, I couldn't copy in the virtual machine.
I think the system was broken, and I have since deleted the VM. This is likely
not a bug and can probably be dropped.
Sorry for the inconvenience.
‐‐‐ Original Message ‐‐‐
On Wednesday, March 17, 2021 8:06 AM, zimoun wrote:
> Hi,
>
> On Wed, 17 Mar 2021 at 01:45, Charles Jackson
> cha
Hi,
On Wed, 17 Mar 2021 at 01:45, Charles Jackson
wrote:
> Sorry about the screen shots, I couldn't copy in the virtual machine.
I am not able to reproduce. The command:
guix pull --commit=15423d38c5 -p /tmp/1542
passes. Idem with time-machine.
Could you retry the command? The one abov
Hi,
On Wed, 17 Mar 2021 at 13:20, Zachary Orlando via web
wrote:
> I had this same issue, I suggest trying to cause the previous commit
> to pull from, 'guix pull --commit=728c908' (the number will be
> different for future readers.) keep in mind that this is not the best
> solution, it could be
I had this same issue, I suggest trying to cause the previous commit to pull
from, 'guix pull --commit=728c908' (the number will be different for future
readers.) keep in mind that this is not the best solution, it could be a
security risk, but it's the fastest until a official fix is issued.
