bug#59489: bug#57292: [PATCH] WIP: gnu: propagate inputs for gdm and rework gdm-service-type.
Am Sonntag, dem 04.02.2024 um 08:53 + schrieb Dariqq: > > On 30.01.24 06:27, Liliana Marie Prikler wrote: > > > In my opinion, adding gnome-shell and gnome-control-center to gdm- > > configuration-gnome-shell-assets would be preferable to propagating > > inputs. > > > > WDYT? > > > This is basically my original patch in > https://issues.guix.gnu.org/57292#3. > > If i understand it correctly Maxim wants gdm to take care of all of > dependencies providing functionality and handcrafting the environment > with gdm-shepherd-service and gdm-configuration-gnome-shell-assets > feels like a hacky workaround. Yes, it seems Maxim and I have conflicting goals. Maxim wants to avoid "abusing" gnome-shell-assets whereas I want to avoid propagation, as it pollutes profiles. Perhaps Maxim and I can agree on how to interpret gnome-shell-assets, as IIUC even with packages that aren't "pure data" only the data portion of it ought to be relevant, no? We should do so especially because the newly propagated variables are anyhow propagated by gnome-desktop-service, which could constitute weird behaviour all around. Cheers
bug#68920: Issues with issues.guix.gnu.org (502 Bad Gateway)
Hi Felix, You are welcome to use my Mumi clone at mumi.juix.org. Bookmarked, thanks! Looks like issues.guix.gnu.org is back up again. Kind regards, - Christina On 04/02/2024 05:33, Felix Lechner wrote: Hi Christina, On Sat, Feb 03 2024, Christina O'Donnell wrote: connecting to https://issues.guix.gnu.org/ results in ... a 502 bad gateway. Kind regards Felix
bug#68905: Boot fails when symlink exists
Today my Guix System crashed during the boot process for external reasons. Upon restart, booting a system would drop into the REPL right after the following line: --8<---cut here---start->8--- making '/var/...' the current system... --8<---cut here---end--->8--- complaining that the symlink already exists. I checked gnu/build/activation.scm (activate-current-system), and there is this: --8<---cut here---start->8--- ;; Atomically make SYSTEM current. (let ((new (string-append %current-system ".new"))) (symlink system new) (rename-file new %current-system))) --8<---cut here---end--->8--- And indeed, there was a dangling /run/current-system.new file on my disk. After removing it (from a live USB, didn't know how to do this from the Guile REPL), the system succeeded to boot. The fix should be easy: ensure that (symlink system new) overwrites any potentially existing file. Cheers! Pierre
bug#68853: Guix Hurd - download error
Hello, Guix. I got a error when I was trying to download the file: https://ci.guix.gnu.org/search/latest/image?query=spec:images+status:success+system:x86_64-linux+hurd-barebones.qcow2 The message was: error "Could not find the requested build product." I hope this information will be useful for you. Best regards. Sent with [Proton Mail](https://proton.me/) secure email.
bug#53342: close 53342
Obsolete. -- Best regards, Nicolas Graves
bug#62656: close 62656
Issue fixed. -- Best regards, Nicolas Graves
bug#68853: Guix Hurd - download error
In the meantime you could build the image yourself, while running the following command in a git checkout of Guix: ``` guix system image gnu/system/images/hurd.scm ``` It shouldn't take very long and e.g. even works on my rather slow Laptop :) ~Jonathan
bug#57292: [PATCH] WIP: gnu: propagate inputs for gdm and rework gdm-service-type.
On 30.01.24 06:27, Liliana Marie Prikler wrote: In my opinion, adding gnome-shell and gnome-control-center to gdm- configuration-gnome-shell-assets would be preferable to propagating inputs. WDYT? This is basically my original patch in https://issues.guix.gnu.org/57292#3. If i understand it correctly Maxim wants gdm to take care of all of dependencies providing functionality and handcrafting the environment with gdm-shepherd-service and gdm-configuration-gnome-shell-assets feels like a hacky workaround.
