Emacs and Gnome branches are merged now

Hey Guix, I've now pushed the merge commits for both emacs-team and gnome-team. If you have a weak machine, PLEASE DO NOT PULL IMMEDIATELY AND WAIT FOR CI TO CATCH UP! Despite efforts to prebuild things on the respective branches, the merge commit carries with it a rebuild of the most nasty pack

Re: Losing signing keys for custom Guix channel

If commit i adds a new signing key to the channel’s authorisations file and commit i+1 is signed with that signing key, then commit i+1 can be used in channel intro. You can’t add a signing key to the authorisations in a commit and sign that same commit with the new key. Is that issue here? Jake

Re: Status of ‘core-updates’

Hi Ludo, Ludovic Courtès writes: > What’s the status of ‘core-updates’? What are the areas where help is > needed? Disclaimer: I've been quite busy with work recently and haven't been able to work on core-updates that much (having to build the world locally doesn't help). Currently, the deskt

Re: Emacs and Gnome branches are merged now

Liliana Marie Prikler writes: > I've now pushed the merge commits for both emacs-team and gnome-team. Thank you to everyone involved in getting these changes through :D > If you have a weak machine, PLEASE DO NOT PULL IMMEDIATELY AND WAIT FOR > CI TO CATCH UP! Despite efforts to prebuild thin

Re: Emacs and Gnome branches are merged now

Am Samstag, dem 30.03.2024 um 14:20 + schrieb Christopher Baines: > I think the last merge of master in to gnome-team was pushed on the > 20th of March, with the merge of gnome-team in to master being pushed > today on the 30th. Good catch, I should have merged to gnome-team first and then merg

Re: Backdoor in upstream xz-utils

Tomas Volf <~@wolfsden.cz> writes: > On 2024-03-29 13:39:59 -0700, Felix Lechner via Development of GNU Guix and > the GNU System distribution. wrote: >> > Is there a way we can blacklist known bad versions? >> >> Having said all that, I am not sure Guix is affected. >> >> On my systems, the 'd

Recent security issues (guix-daemon and xz)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 -BEGIN PGP SIGNATURE- iQJRBAEBCgA7FiEEpCB7VsJVEJ8ssxV+SZCXrl6oFdkFAmYIhx0dHGpvaG4ua2Vo YXlpYXNAcHJvdG9ubWFpbC5jb20ACgkQSZCXrl6oFdmOLw//dXLjX82YYaQeEpbp a0xNswh4OyHKDpMwy8rE2sWbQ7Ckivu79e+0m8wGbzf1+K4SB37CaxT2g9/98uRB Vm5XiztOmnx83aqin4DS141

Re: Shepherd timers

Hi Ludovic, I want to give my suggestion for the timer support in the Shepherd: Could the Shepherd depend on mcron for the timer functionality? Since mcron already handles scheduling commands to run at a certain time, there would be no need to reimplement it again. Mcron would just need to sup

Re: Shepherd timers

Hi Adam, On Sun, Mar 31 2024, Adam Faiz wrote: > Could the Shepherd depend on mcron for the timer functionality? Since > mcron already handles scheduling commands to run at a certain time, > there would be no need to reimplement it again. I don't wish to speak for the Mcron maintainer Dave, who

Re: Shepherd timers

Hi Dale, On Sun, Mar 31 2024, Adam Faiz wrote: > Could the Shepherd depend on mcron for the timer functionality? I know you your name isn't Dave. Sorry! Kind regards Felix