bug#35683: wishlist: addessing statefulness of .cache(s)

Hi Guix, AFAIU issues like the two I point below are becoming a common pattern and are *critical* 1. gnome session not starting due to state in $HOME/.cache http://lists.gnu.org/archive/html/guix-devel/2019-04/msg00177.html Message-ID: <87ef68ibfy@elephly.net> Ricardo Wurmus: --8<-

bug#35683: wishlist: addessing statefulness of .cache(s)

Le 11 mai 2019 09:32:43 GMT+02:00, Giovanni Biscuolo a écrit : >Hi Guix, > >AFAIU issues like the two I point below are becoming a common pattern >and are *critical* > >1. gnome session not starting due to state in $HOME/.cache > http://lists.gnu.org/archive/html/guix-devel/2019-04/msg00177.html

bug#35683: wishlist: addessing statefulness of .cache(s)

Giovanni Biscuolo writes: > AFAIU issues like the two I point below are becoming a common pattern > and are *critical* linked bug report: - bug#35669: Mesa is failing an assertion [...] -- Giovanni Biscuolo Xelera IT Infrastructures signature.asc Description: PGP signature

bug#35519: librsvg broken on i686-linux

Hi Danny, Danny Milosavljevic writes: > But when I use our separate package definitions it fails when building libcore > (which is the first library for the target compiler). > Invoke seems to swallow the output, so I have no idea where or why it failed > (grr). Hmm. What makes you think that

bug#35586: GNOME

Hello Guix Folks! Any update on this bug please? Regards, RG.

bug#35606: Gajim

Hello Guix Folks! Any update on this bug please? Regards, RG.

bug#35606: Gajim

Raghav Gururajan writes: > Any update on this bug please? I’ve sent an update on Tuesday where I pointed out the likely culprit. Have you attempted to confirm my findings? What do you think about changing the phase I pointed out to be incorrect? -- Ricardo

bug#35606: Gajim

> I’ve sent an update on Tuesday where I pointed out the likely culprit. > Have you attempted to confirm my findings? What do you think about > changing the phase I pointed out to be incorrect? Oops! I missed to read that email. My bad. Regarding empty menu, it same for me too. Regarding the path

bug#35586: GNOME

Hi Raghav, > Any update on this bug please? not all of the GNOME applications have been packaged. Would you like to try to package some of the missing applications? This bug has a lower priority to me than others, so I’m unlikely to work on this soon. -- Ricardo

bug#35586: GNOME

> not all of the GNOME applications have been packaged. Would you like to > try to package some of the missing applications? Sure, I will give it a try :) > This bug has a lower priority to me than others, so I’m unlikely to work > on this soon. I see. Regards, RG.

bug#35683: wishlist: addessing statefulness of .cache(s)

ehlo Giovanni, Giovanni Biscuolo wrote: AFAIU unfortunately we have application/library state all over .cache(s) that sometimes crashes software *and* trying to fix this upstream it's _not_ an option [1] Oh. That's… disappointing to say the least, since these are both upstream bugs that Gu

bug#35683: wishlist: addessing statefulness of .cache(s)

Julien, Julien Lepiller wrote: I wonder if we could mount a tmpfs on .cache? Would that be enough? Seems a shame to waste RAM like that, when we could (ab)use FUSE: . ;-) T G-R signature.asc Description: PGP signature

bug#35519: librsvg broken on i686-linux

Hi, > Hydra failed to build librsvg on i686-linux, because it depends on Rust > which is still broken on i686-linux in Guix. Danny opened a bug report with the mrustc upstream: https://github.com/thepowersgang/mrustc/issues/108 The last message there tells us to try again with current HEA

bug#35683: wishlist: addessing statefulness of .cache(s)

Hello Tobias, Tobias Geerinckx-Rice writes: > Giovanni Biscuolo wrote: >> AFAIU unfortunately we have application/library state all over >> .cache(s) >> that sometimes crashes software *and* trying to fix this >> upstream it's >> _not_ an option [1] > > Oh. That's… disappointing to say the le

bug#35519: librsvg broken on i686-linux

Hi Mark, On Sat, 11 May 2019 04:03:41 -0400 Mark H Weaver wrote: > Hmm. What makes you think that 'invoke' swallowed the output? You > might be right, but 'invoke' is used quite widely by now in Guix, > including to invoke 'make' in gnu-build-system, and I haven't seen > reports of it swallowi

bug#35519: librsvg broken on i686-linux

Extra info: guix mrustc seems to be compiled with gcc 8 but guix rust-1.19 with gcc 5.5. How did that happen? Doesn't sound like a good idea since one loads compiler plugins compiled using the other into the same process. pgpbp3YRpnpCn.pgp Description: OpenPGP digital signature

bug#35670: guix package --roll-back message in Spanish is missing a line break

As a translator, I think these kinds of newlines should be left out of the translation strings, though, so that the probability of messing up the formatting is lower. --- https://sirgazil.bitbucket.io/

bug#35623: FW: bug#35623: guix pull failed on RHEL7

Hello, Karrick McDermott skribis: > 1. Glad you identified why `HOME` was unset, due to the > `with-clean-environment` function. I am surprised a few environment variables > are not conveyed through the code path, as `ssh` does for variables it deems > safe, including `HOME`, `LOGNAME`, `TZ`,

bug#35550: Installer: wpa_supplicant fails to start

Ludovic Courtès skribis: > Ludovic Courtès skribis: > >> I’m proposing the addition below to be on the vey safe side. > > Pushed as Shepherd commit 1ebea0a6e4c6ff11212eda348072acf9c379e7b2. > > Unless something goes wrong, I’ll make Shepherd commit > fbb9c3fac745552eaf0f354bd0134cca7027bf17

bug#35551: guix search

Hi Bruno, Bruno Haible writes: > Mark H Weaver wrote: >> If we add functionality that calls out to the network in response to a >> package search, e.g. to query popularity ratings or package file >> listings, we should make sure the user knows it's happening, and provide >> a way to disable it.

bug#35551: guix search

Hi Tobias, Tobias Geerinckx-Rice writes: > Bruno Haible wrote: >> Mark H Weaver wrote: >>> If we add functionality that calls out to the network in response >>> to a >>> package search, e.g. to query popularity ratings or package file >>> listings, we should make sure the user knows it's happeni

bug#35623: FW: bug#35623: guix pull failed on RHEL7

Ludo', Ludovic Courtès wrote: Commit 48d498c2c3984784336b27ba5e261319f3ac6a3a lets HOME pass through, which should sidestep the problem you encountered. This breaks ‘guix pull’, but I can't for the life of me see how HOME is being applied here. Could you enlighten me? Kind regards, T G-R

bug#35623: FW: bug#35623: guix pull failed on RHEL7

Tobias Geerinckx-Rice wrote: Ludovic Courtès wrote: Commit 48d498c2c3984784336b27ba5e261319f3ac6a3a lets HOME pass through, which should sidestep the problem you encountered. This breaks ‘guix pull’, but I can't for the life of me see how HOME is being applied here. I've reverted the chang

bug#35691: [bug-guix] remote configure failure due to bad pathnames for crt*.o

I built a new virtual machine (VM) on 2-May-2019 from the newly-announced GUIX 1.0 release in the guix-system-install-1.0.0.x86_64-linux.iso image file. The VM runs on VirtManager (QEMU/KVM) on CentOS 7. I initially tried to select 3 desktop managers, but later in the installation, one