Hi Ludo,
Thanks for explaining.
On Thu, 01 Sep 2022 at 09:42, Ludovic Courtès wrote:
>> It means version 3 is used all the time, right?
>
> Yes.
>
>> Well, I miss when or where version 4 is used then.
>
> Generations that were created with a slightly older Guix have a
> version-4 manifest.
It
Hi,
zimoun skribis:
> On Wed, 31 Aug 2022 at 13:06, Ludovic Courtès wrote:
>
>> I fixed it in 67a6828b2bb821274757f686f7c685b664339a96 using the same
>> trick as earlier.
>
> It means version 3 is used all the time, right?
Yes.
> Well, I miss when or where version 4 is used then.
Generations
> I fixed it in 67a6828b2bb821274757f686f7c685b664339a96 using the same
> trick as earlier.
Works now, thank you!
Hi Ludo,
On Wed, 31 Aug 2022 at 13:06, Ludovic Courtès wrote:
> I fixed it in 67a6828b2bb821274757f686f7c685b664339a96 using the same
> trick as earlier.
It means version 3 is used all the time, right? Well, I miss when or
where version 4 is used then.
--8<---cut here-
Hi,
Arun Isaac skribis:
>> I do not think it is related to guix-daemon and I think it is expected;
>> indeed it could be considered as a bug. The command-line,
>>
>> guix pull --commit=xyz -p /tmp/test
>>
>> writes /tmp/test/manifest using the current Guix (say manifest 4) and
>> not using
Hi,
On Tue, 30 Aug 2022 at 22:12, Arun Isaac wrote:
> I think you mean that bug #56441 should remain closed. Bug #56441 was
> about guix time-machine. Bug #57306 is the current bug about guix pull.
Yes, sorry for the confusion.
Cheers,
simon
Hi zimoun,
> Well, it appears to me easier if bug#57306 remains closed since ’guix
> time-machine’ is fixed; as it was the subject.
I think you mean that bug #56441 should remain closed. Bug #56441 was
about guix time-machine. Bug #57306 is the current bug about guix pull.
Regards,
Arun
Hi,
On mar., 30 août 2022 at 01:07, Arun Isaac wrote:
> Thanks, Josselin! I have asked at #56441 whether it may be reopened.
>From my understanding, it is another side effect of
4ff12d1de7cd617b791996ee7ca1240660b4c20e. Commit
9b8c442b254b82196fe2492142b3c3bbbd891a1b is the parent of 4ff12d.
Hi zimoun,
> I do not think it is related to guix-daemon and I think it is expected;
> indeed it could be considered as a bug. The command-line,
>
> guix pull --commit=xyz -p /tmp/test
>
> writes /tmp/test/manifest using the current Guix (say manifest 4) and
> not using Guix at commit xyz (
Thanks, Josselin! I have asked at #56441 whether it may be reopened.
Hi Arun,
On sam., 20 août 2022 at 15:07, Arun Isaac wrote:
> When I guix pull to 6f75565b4ec3b8a7247699c327a3b3196c787f76, activate
> the profile and run guix describe, it fails with an "unsupported
> manifest format" error.
>
> --8<---cut here---start->8---
>
Hi Arun,
Arun Isaac writes:
> This happens because my guix-daemon writes a version 4 manifest and the
> guix from commit 6f75565b4ec3b8a7247699c327a3b3196c787f76 only
> understands a version 3 manifest.
>From what I can gather from looking at the code, the patch at [1]
should've fixed this iss
Oops, I didn't read the issue properly and assumed it was just a
duplicate of the time-machine unsupported manifest format bug by
someone who doesn't know about the workaround (there have been a
few of those); sorry!
-- (
>> Commit 4ff12d1de7cd617b791996ee7ca1240660b4c20e introduced that bug,
>> which was fixed in c9fbd40785a99e13a59d8e530830ce85220a9871:
The failing commit 6f75565b4ec3b8a7247699c327a3b3196c787f76 is not in
that range, if that's what you are saying.
https://issues.guix.gnu.org/56545#1
> Commit 4ff12d1de7cd617b791996ee7ca1240660b4c20e introduced that bug,
> which was fixed in c9fbd40785a99e13a59d8e530830ce85220a9871:
>
> https://issues.guix.gnu.org/56441
>
> ‘guix describe’ should show that you’re using a commit in that range.
>
> The solutio
When I guix pull to 6f75565b4ec3b8a7247699c327a3b3196c787f76, activate
the profile and run guix describe, it fails with an "unsupported
manifest format" error.
--8<---cut here---start->8---
$ guix pull --commit=6f75565b4ec3b8a7247699c327a3b3196c787f76 -p
/tmp/
16 matches
Mail list logo
