bug#39318: [core-updates] 'make-desktop-entry-file' is not exported

My bad I guess :p Should I just export it? -- Pierre Neidhardt https://ambrevar.xyz/ signature.asc Description: PGP signature

bug#39281: gdm doesn't start

> Indeed, my system does have a really slow disk, so it would not surprise me > if that contributed to > it. Of course that shouldn't matter, but that's the only thing I can think > it. It would be nice to > hear if sirgazil can reproduce the fix since I think they were having the > same problem

bug#39324: GNOME Weather doesn't start

Clicking the GNOME Weather icon doesn't start the application. Trying to run it from a terminal doesn't work either, and I get the following message: $ gnome-weather Unsatisfied dependency: GWeather I'm using this Guix in the GNU system: $ LANG=C guix describe Generation 12 Jan 27 2020 16:50

bug#39318: [core-updates] 'make-desktop-entry-file' is not exported

Hello, On the 'core-updates' branch, emacs-exwm, tome4 and drascula fails to build because 'make-desktop-entry-file' is not available. signature.asc Description: PGP signature

bug#38135: Mate: missing gio-launch-desktop

Diego Nicola Barbato writes: > Hi Guix, > > Launching a program from the start menu of the Mate desktop (as provided > by the ‘mate-desktop-service-type’) currently (commit: 41ee209) fails. > The error message complains about a missing ‘gio-launch-desktop’ (found > in the “bin” output of ‘glib’).

bug#39313: artanis's guile-json in conflict with guix

Hi David, > Tried to install artanis today. It's kida ok to have conflicting package > but maybe not with guix itself? Not sure whether it's an issue to > address. Whenever there are conflicts you should do as the hint says and upgrade packages together. Not doing so would result in a mixed en

bug#35248: Monero fails to build and is outdated

This issue seems to be solved now, at least on x86_64: https://ci.guix.gnu.org/search?query=monero signature.asc Description: PGP signature

bug#39281: gdm doesn't start

On Mon, 27 Jan 2020 15:29:05 -0500 Danny Milosavljevic wrote > Patch applied to guix master as commit > 4fc4e5fdd9da6320aa94eeec61cbb84a7dc9460e > for now. > Problem solved for me :)

bug#39172: SElinux guix-daemon.cil file

Hello, Ricardo Wurmus skribis: > Could we also do this in one expression? > > (typeattributeset file_type (or guix_profiles_t > guix_daemon_conf_t > guix_daemon_exec_t > guix_daemon_so

bug#39209: Guix-commits digest settings

Hi Christopher, Christopher Howard skribis: > Hello, would it be possible for the Guix-commits list administrator to > tune the Digest settings, so as to reduce the numbers of Digest emails > sent each day? I'm using Digest mode, but still receive about 8-15 > emails per day. One thing that migh

bug#39288: Wrong keyboard layout to decrypt hard drive

Hi, Tobias Geerinckx-Rice skribis: > Could you check whether your system configuration's > bootloader-configuration actually contains a keyboard-layout field? > > (bootloader (bootloader-configuration > (bootloader grub-efi-bootloader) > (target "/bo

bug#39281: gdm doesn't start

On Mon, 27 Jan 2020, Danny Milosavljevic wrote: Hi, hmm, if you want to find out whether we could fix it, could you invoke: useradd gnome-initial-setup I added gnome-initial-setup to my operating system config and reconfigured with 94600c3960d7e2f12a3a9b6d2ed0d98ddacdd055 (the commit before

bug#39281: gdm doesn't start

Patch applied to guix master as commit 4fc4e5fdd9da6320aa94eeec61cbb84a7dc9460e for now. pgprund5UBkYj.pgp Description: OpenPGP digital signature

bug#39313: artanis's guile-json in conflict with guix

Le 27 janvier 2020 13:18:41 GMT-05:00, David Dashyan a écrit : >-BEGIN PGP SIGNED MESSAGE- >Hash: SHA512 > > >Tried to install artanis today. It's kida ok to have conflicting >package >but maybe not with guix itself? Not sure whether it's an issue to >address. > >substitute: guile: warning

bug#39281: gdm doesn't start

Hi, hmm, if you want to find out whether we could fix it, could you invoke: useradd gnome-initial-setup (on the console via ctrl-alt-f1) and then reboot? If that doesn't fix it I'm all for removing gnome-initial-setup for the time being... pgpXmPIn6zNdT.pgp Description: OpenPGP digital sign

bug#39281: gdm doesn't start

On Mon, 27 Jan 2020, sirgazil wrote: Was the patch already applied? Because I just pulled, reconfigured and I have the same problem: After a message like this No, the patch wasn't applied, as we're still not sure if there is a better fix. I applied it to my local copy of guix [0] to test. If

bug#38422: Bug status? '.png' files with executable permissions

close 38422 stop

bug#39281: gdm doesn't start

On Mon, 27 Jan 2020 14:08:44 -0500 Jack Hill wrote > On Mon, 27 Jan 2020, Raghav Gururajan wrote: > > >> so I removed gnome-initial-setup from the propagated-inputs with the > >> following patch, and, indeed, > >> that resolved the problem with gdm on my system. > > > > That's

bug#39289: Can't use i3: status_command not found

Damien Cassou writes: > It seems i3status should be installed as well to make i3 work with the > automatically generated i3 configuration. This is already fixed on the master branch, since commit 676eb5880ec2fae03752513c2442aae0bda9bfc4. Sorry for the inconvenience! We should get that 1.1 rele

bug#39310: MariaDB reproducibility issue

Josh writes: > Hi Guix, > > > > I ran into this issue when building mariadb 10.1.38. I've attached the >

bug#39281: gdm doesn't start

On Mon, 27 Jan 2020, Raghav Gururajan wrote: so I removed gnome-initial-setup from the propagated-inputs with the following patch, and, indeed, that resolved the problem with gdm on my system. That's strange. Both our system share similar configuration. But for me gdm works fine with gnome-i

bug#39313: artanis's guile-json in conflict with guix

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Tried to install artanis today. It's kida ok to have conflicting package but maybe not with guix itself? Not sure whether it's an issue to address. substitute: guile: warning: failed to install locale The following package will be installed: art

bug#39294: Can't run ./configure

Hi Damien, Thank you for reporting the issue. Which Guix version do you use (command "guix describe")? Against which Git commit? Because I am not able to reproduce. :-( I am using a fresh checkout with the Git commit 5e61de242156cdb3314abac168d9682ca7a4c28f. And I have tried the old Guix versio

bug#39310: MariaDB reproducibility issue

Hi Guix, I ran into this issue when building mariadb 10.1.38. I've attached the last 300 lines of the log.

bug#39298: re-exporting local variable: iota

Ludovic Courtès writes: > Fixed in 5e61de242156cdb3314abac168d9682ca7a4c28f. Thank you for the quick fix!

bug#39298: re-exporting local variable: iota

Hello! clem...@lassieur.org (Clément Lassieur) skribis: > Ricardo Wurmus writes: > >> Since the upgrade to Guile 3.0 I can no longer upgrade my profile. The >> module-import-compiled derivation can no longer be built. It fails with >> a backtrace involving only Guile modules, no Guix modules.

bug#39297: guix repl loads Guild 3.0.0 despite dependency is guile@2.2.6

Hi, Moritz Lell skribis: > When I invoke `guix repl`, I get: > > GNU Guile 3.0.0 > Copyright (C) 1995-2020 Free Software Foundation, Inc. > > Guile comes with ABSOLUTELY NO WARRANTY; for details type `,show w'. > This program is free software, and you are welcome to redistribute it > under certa

bug#38350: Building libsignal-protocol-c on armv7l fails while test phase

On Mon, 27 Jan 2020 00:26:09 +0100 Marius Bakke wrote: > This appears to be fixed now: Thanks!

bug#39298: re-exporting local variable: iota

Ricardo Wurmus writes: > Since the upgrade to Guile 3.0 I can no longer upgrade my profile. The > module-import-compiled derivation can no longer be built. It fails with > a backtrace involving only Guile modules, no Guix modules. > > The error is: > > ice-9/boot-9.scm:752:25: In procedure di

bug#39281: gdm doesn't start

> I believe that I've found the problem! Nice! > Using the technique that Ludo’ described in > , I was > able to grab an strace of gdm (attached) while it was failing to start > properly. I was suspicious > of the following line: > > """ > 418 22:46: