bug#55707: bug#55488: GDM, GNOME: Can't start desktop session after upgrade

2022-06-02 Thread Luis Felipe via Bug reports for GNU Guix
Salut, On Thursday, June 2nd, 2022 at 21:02, Ludovic Courtès wrote: > In the meantime, could you try the following config, which disables > logging on tty12, to see if it boots quicker? The config changes is > twofold; first, after the ‘use-modules’ form of your OS config, add: > > [...] >

bug#55488: GDM, GNOME: Can't start desktop session after upgrade

2022-06-02 Thread Ludovic Courtès
Hola, Luis Felipe skribis: >> Could it be https://issues.guix.gnu.org/55707? At boot time, if you >> switch to tty12 (by pressing alt-f12) as soon as it’s available, do you >> see messages that get printed pretty slowly, like 4–5 lines per second? > > Maybe? I recorded a video. Image is low

bug#54786: Installation tests are failing

2022-06-02 Thread Ludovic Courtès
Howdy! Maxim Cournoyer skribis: > I tried capturing the issue in the commit message, but I'll provide > another more hands-on view: the Jami service was broken due to changes > in Shepherd 0.9.0 that caused the blocking sleeps + concurrent > make+forkexec-constructor/container and

bug#55488: GDM, GNOME: Can't start desktop session after upgrade

2022-06-02 Thread Luis Felipe via Bug reports for GNU Guix
Hello again, On Wednesday, June 1st, 2022 at 19:55, Ludovic Courtès wrote: > So it has to do with elogind taking too long to start. Same with > polkit: Timeouts are common here... > --8<---cut here---start->8--- > > 854:May 31 12:24:10 localhost

bug#54786: Installation tests are failing

2022-06-02 Thread Maxim Cournoyer
Hi Ludovic, Ludovic Courtès writes: > Hi Maxim, > > Maxim Cournoyer skribis: > >> Ludovic Courtès writes: > > [...] > >>> Before going further, I’d like to understand: this does more than just >>> fix the Jami system tests, right? >>> >>> It would have been nice to have surgical changes to

bug#55765: [mumi] Xapian SWIGy issue

2022-06-02 Thread Ludovic Courtès
Hello, Arun Isaac skribis: > That doesn't immediately ring a bell, but I could investigate. Do you > have any way to reproduce this issue? Of course not, it’d be too easy. :-) > Also, which version of mumi and guile-xapian is this? It’s this one: --8<---cut

bug#55552: frama-c should probably be wrapped

2022-06-02 Thread raingloom
On Thu, 2 Jun 2022 07:57:19 +0200 Julien Lepiller wrote: > Le Fri, 20 May 2022 13:36:54 +0200, > raingloom a écrit : > > > Sorry, can't debug this further right now. > > > > ``` > > $(guix build frama-c)/bin/frama-c > > [kernel] User Error: [findlib] package 'ocamlgraph' not found > >

bug#55765: [mumi] Xapian SWIGy issue

2022-06-02 Thread Arun Isaac
Hi Ludo, > --8<---cut here---start->8--- > 2022-06-02 15:04:45 GET /issue/54065/raw/12 > 2022-06-02 15:04:45 GET /issue/43096/raw/2 > 2022-06-02 15:04:45 GET /issue/45676/raw/10 > 2022-06-02 15:09:09 GET In procedure delete-Database: Wrong type argument in >

bug#55765: [mumi] Xapian SWIGy issue

2022-06-02 Thread Ludovic Courtès
Hello! Earlier today, I caught mumi in the middle of what I think we can call: a bug. Specifically, a Xapian or SWIG bug. --8<---cut here---start->8--- 2022-06-02 15:04:45 GET /issue/54065/raw/12 2022-06-02 15:04:45 GET /issue/43096/raw/2 2022-06-02 15:04:45

bug#55723: Full disk encryption with grub-efi and LUKS2

2022-06-02 Thread Giovanni Biscuolo
Hello Josselin and Lars-Dominik Josselin Poiret via Bug reports for GNU Guix writes: [...] >> Supposedly there are also patches for grub-mkimage, but maybe we can >> include a workaround like the above by default until then or remove the >> section about LUKS2 entirely? > > Thank you for

bug#55709: R texinfo documents are not showing up for me

2022-06-02 Thread Ludovic Courtès
Hi, Kyle Andrews skribis: > For me it gave: > > 0 > /gnu/store/vncwfb53kbnyflyc1jyd2xv9sifpw202-gtk+-3.24.30/lib/libgdk-3.so.0 > > Does this mean I have some store corruption as Maxime suggested? Yes, that sounds likely. Ludo’.

bug#53225: shepherd freezes if wireguard is started with dns config enabled

2022-06-02 Thread Ludovic Courtès
Hi Nathan, Nathan Dehnel skribis: > Just tested and Shepherd 0.9 does not fix this issue. Could you be more specific? Specifically, could you share /var/log/messages for the parts related to Wireguard? > On Mon, Jan 17, 2022 at 7:48 AM Ludovic Courtès wrote: [...] >> One command sent to

bug#54786: Installation tests are failing

2022-06-02 Thread Ludovic Courtès
Hi Maxim, Maxim Cournoyer skribis: > Ludovic Courtès writes: [...] >> Before going further, I’d like to understand: this does more than just >> fix the Jami system tests, right? >> >> It would have been nice to have surgical changes to “just” fix the >> tests, along the lines of

bug#54760: import: hackage: Internal libraries are not filtered out of dependency list

2022-06-02 Thread Philip Munksgaard
Hi again, On Thu, 2 Jun 2022, at 13:57, Lars-Dominik Braun wrote: > Hey, > >> Indeed, that seems to work for those packages, but it still doesn't seem to >> work for OneTuple, as mentioned here: > I’m attaching a patch for that, please have a look. I’ll merge these > into master, since they

bug#54760: import: hackage: Internal libraries are not filtered out of dependency list

2022-06-02 Thread Lars-Dominik Braun
Hey, > Indeed, that seems to work for those packages, but it still doesn't seem to > work for OneTuple, as mentioned here: I’m attaching a patch for that, please have a look. I’ll merge these into master, since they don’t change any builds. > Aha! The upgrade to GHC 9.0.0 caused ghc-hashable to

bug#54760: import: hackage: Internal libraries are not filtered out of dependency list

2022-06-02 Thread Philip Munksgaard
On Thu, 2 Jun 2022, at 11:59, Philip Munksgaard wrote: > On Thu, 2 Jun 2022, at 11:53, Philip Munksgaard wrote: >> Also, attoparsec still won't build with result of the import, but for >> different reasons. > > Actually, that's weird. Didn't attoparsec used to build? Aha! The upgrade to GHC

bug#54760: import: hackage: Internal libraries are not filtered out of dependency list

2022-06-02 Thread Philip Munksgaard
On Thu, 2 Jun 2022, at 11:53, Philip Munksgaard wrote: > Also, attoparsec still won't build with result of the import, but for > different reasons. Actually, that's weird. Didn't attoparsec used to build?

bug#54752: import: hackage: `elif` conditionals not supported

2022-06-02 Thread Philip Munksgaard
On Sun, 22 May 2022, at 11:55, Lars-Dominik Braun wrote: > Hi Philip, > > thank you! > >> Unfortunately, building raaz still fails (first because of the description, >> then because some internal libraries are added as external dependencies, and >> then for... other reasons I haven't figured

bug#54760: import: hackage: Internal libraries are not filtered out of dependency list

2022-06-02 Thread Philip Munksgaard
Hi Lars, On Sun, 22 May 2022, at 11:37, Lars-Dominik Braun wrote: >> The attoparsec package on hackage defines multiple internal libraries inside >> one package, named "attoparsec" and "attoparsec-internal", with the first >> depending on the latter. Importing attoparsec using `guix import

bug#55709: R texinfo documents are not showing up for me

2022-06-02 Thread Liliana Marie Prikler
Am Dienstag, dem 31.05.2022 um 10:37 +0200 schrieb Maxime Devos: > (Is there a method to verify and repair a _single_ store item instead > of the whole store?). I think the syntax for that'd be ‘[sudo] guix build --repair STORE_ITEM’. Cheers