chezmoi

2023-01-01 Thread jgart
Hi Guixers Happy GNU Year 2023, Should we remove the chezmoi package since it is 103 version releases behind current? I think it might be a maintenance burden currently to maintain it given the amount of dependencies needed to be packaged. Or, should we leave the package in until someone decid

Re: All updaters are broken

2023-01-01 Thread Hartmut Goebel
Hi Ricardo, my fault, I missed running the tests again after the latest changes. I'll work on fixing this tomorrow (Monday). -- Regards Hartmut Goebel | Hartmut Goebel | h.goe...@crazy-compilers.com | | www.crazy-compilers.com | compilers which you thought are impossible

mumi tag team

2023-01-01 Thread jgart
Hi Guixers, What do you think if mumi had support for team or language tags?

Re: Suggest improve emacs setting in 'The Perfect Setup'

2023-01-01 Thread Feng Shu
Joshua Branson writes: > Feng Shu writes: > >> Hello: >> >> In 'The Perfect Setup', we suggest user to use the below emacs config: >> >> ``` >> ;; Assuming the Guix checkout is in ~/src/guix. >> (with-eval-after-load 'geiser-guile >> (add-to-list 'geiser-guile-load-path "~/src/guix")) >> ``` >

Re: Suggest improve emacs setting in 'The Perfect Setup'

2023-01-01 Thread jbranso
January 1, 2023 2:54 PM, "Feng Shu" wrote: > Joshua Branson writes: > >> Feng Shu writes: >> >>> Hello: >>> >>> In 'The Perfect Setup', we suggest user to use the below emacs config: >>> >>> ``` >>> ;; Assuming the Guix checkout is in ~/src/guix. >>> (with-eval-after-load 'geiser-guile >>>

Re: Suggest improve emacs setting in 'The Perfect Setup'

2023-01-01 Thread Feng Shu
jbra...@dismail.de writes: > That's a good idea! I think there is/was a guix developer trying to write an > emacs configuration specifically to hack on guix... The below is my current guix emacs config, I do not know whether it is suitable for an example, maybe someone can try it :-) If suitab

Re: All updaters are broken

2023-01-01 Thread Hartmut Goebel
Hi Ricardo, I managed working on this this evening already. Am 31.12.22 um 15:27 schrieb Ricardo Wurmus: Commit 8aeccc6240ec45f0bc7bed655e0c8149ae4253eb seems like the problem here. Hartmut, can you please fix this? Otherwise I’d like to revert this and related commits ASAP. I fixed he test