Tobias Geerinckx-Rice <m...@tobias.gr> writes:

Hi Tobias,

> Hi Roman,
>
> On 26 September 2024 15:00:56 UTC, Roman Scherer <ro...@burningswell.com> 
> wrote:
>>the error seems to be gone now. I'm not sure if it is because you
>>updated the commit a while ago
>
> Which commit was updated by Ludo' and when?

This is the commit I was talking about, from a week ago:

80709f1411af2e8f627da2e41791abf085347642

> (I'm responsible for the setuid-* removal and any possible breakage, hence my 
> interest.)
>
>> or because I also cleaned ~/.cache/guix
>>folder while trying to fix this.
>
> So you're not invoking Guix from a local Git checkout?
>

No, I wasn't using a local checkout. I was using the Guix from my user
profile and then I run guix shell (with and without --pure) with the
following guix.scm file:

https://github.com/asahi-guix/channel/blob/main/guix.scm#L46

This guix.scm file has the guix package as a dependency, and my thinking
was that this must pull in old code, because at the time I had the issue
the guix package pointed to a commit before the change to
%ensure-setuid-program-list.

At some point I also deleted ~/.cache/guix and pulled guix multiple
times and the issue went away. But I'm not sure how that happened.

I think all is good now. I haven't seen this issue anymore.

Roman

>
> Kind regards,
>
> T G-R
>
> Sent on the go.  Excuse or enjoy my brevity.

Attachment: signature.asc
Description: PGP signature

Reply via email to