bug#65832: [PATCH] guix: shell: Don't whitelist / by typo in `shell-authorized-directories'.

Janneke Nieuwenhuizen writes: Hi! > Title says it all... [..] After discussing with the security team, pushed to master as 1ef4974be94d75d935d98399dcda44199a1fca47 Greetings, Janneke -- Janneke Nieuwenhuizen | GNU LilyPond https://LilyPond.org Freelance IT https://www.JoyOfSource.com

bug#65832: [PATCH] guix: shell: Don't whitelist / by typo in `shell-authorized-directories'.

Title says it all... So, i've started using direnv with envrc.el, really great! ...which meant that on top op `guix shell' pestering me with its shell-authorized-directories, I had to also type `direnv allow' all day. Anyway, I found that direnv has a whitelist, prefix even; so I looked into

bug#65740: No fallback to SWH for .guix-channel dependencies

Hi, Simon Tournier skribis: > The main reason is because the channel bimsb contains the file > .guix-channel which reads, > > (channel > (version 0) > (dependencies > (channel >(name guix-past) >(url "https://gitlab.inria.fr/guix-hpc/guix-past;)) > (channel >(name

bug#65056: https://issues.guix.gnu.org/ cannot be accessed through Tor

Hello! Ricardo Wurmus skribis: > I don’t know. I’m on holidays now, but I’ve opened yet another ticket > to get a definitive answer to my more elaborate variant of “WTF?”. Did you eventually get feedback from them? If not, we can start looking for a way to move public-facing services

bug#62784: drascula, lure, lure-de, lure-es, lure-fr, lure-it, sky: non-commercial license

Am Mittwoch, dem 12.04.2023 um 11:35 +0200 schrieb Liliana Marie Prikler: > Hi Denis, > > [...] We have been aware of this for about half a year now (see the > thread in guix-devel following [1]), but as other FSDG-abiding > distributions still include these games (or at least did back then) > we

bug#65720: Guile-Git-managed checkouts grow way too much

Hi! Simon Tournier skribis: > On Tue, 05 Sep 2023 at 16:18, Ludovic Courtès wrote: > >> It would also be pretty bad for closure size: >> >> --8<---cut here---start->8--- >> $ guix size guile-git | tail -1 >> total: 106.6 MiB >> $ guix size guile-git

bug#65720: Guile-Git-managed checkouts grow way too much

Hello! Josselin Poiret skribis: > Right, although I wouldn't necessarily say that the former doesn't have > a proper API, but rather that it has a Unix-oriented API. That leads to > performance issues on e.g. Windows but on Linux I'm not sure there's > much of a difference. [...] > We could

bug#65306: [shepherd] ntpd throws shepherd out of the loop

Timotej Lazar skribis: > Ludovic Courtès [2023-09-02 22:44:03+0200]: >> Liliana, Timotej: could you try the Guix patch I posted at >> ? > > That patch works for my aarch64 board. I encounter the same issue on an > x86_64 system without a functional RTC, but at

bug#65769: greetd-wlgreet-sway-session result is blinking cursor

chris writes: > I support any conclusion from Josselin and unmatched-paren and want to add > these observations, > * wlgreet *does require* the greeter lock file > * wlgreet *does not require* elogind/logind > * not-advanced users like me may want to use wlgreet without elogind I'm not

bug#65769: greetd-wlgreet-sway-session result is blinking cursor

Josselin sent this message intended for the thread and I think they are okay with re-pasting here, > Usually elogind is responsible (through a PAM module) for creating this > runtime directory. If you're not using elogind, you'll need to create this > directory yourself somehow. I don't

bug#65769: greetd-wlgreet-sway-session result is blinking cursor

chris writes: >> The greeter works after creating /run/user/986/wayland-1.lock and changing >> the >> owner of /run/user/986 and /run/user/986/wayland-1.lock to "greeter". wut. I don't remember ever having to do anything like that... > My system config is here > > >

bug#63726: time-machine without options does not get the latest commit

Simon Tournier skribis: > On Thu, 25 May 2023 at 23:03, Ludovic Courtès wrote: > >>> Now, what I am missing. The manual says: >>> >>>As for ‘guix pull’, the absence of any options means that the latest >>> commit on the master branch will be used. The command >>> >>> guix

bug#65769: greetd-wlgreet-sway-session result is blinking cursor

On 9月08日 金, ( wrote: > I believe that may have been moi :) This is really odd. I seem to be > the only person who has ever managed to make it work (though there's a > bit of a reporting bias there in that people who do manage probably > won't bring it up...) > > It would be great if anyone

bug#65769: greetd-wlgreet-sway-session result is blinking cursor

chris writes: > In irc, I messaged the user who created greetd-wlgreet-sway-session and it > seems > other users have encountered the blinking cursor and no one knows of a > solution. If possible, I would like help troubleshoot and resolve the issue. I believe that may have been moi :) This is