Re: `search-input-file` and readability

Hello, Kurome writes: > I see search-input-file and search-input-directory used to specify file paths > of > input packages, like this: > > (search-input-file inputs "bin/foo") > > From my observation, this can also be rewritten as: > > (string-append #$(this-package-input "package-

Re: Introducing Guixotic, a Guix/Guile worker cooperative

Hi, Maxim Cournoyer writes: > Ludovic Courtès writes: > > [...] > >> Which makes me thing: should we have a “Commercial Support” section on >> the web site, maybe linked from <https://guix.gnu.org/en/help/>? This >> would need discussion but I’d

Re: New bordeaux mirror available in Russia

Hi, "Vincent Ambo" writes: > we've set up a mirror of bordeaux.guix.gnu.org in Russia, available > here: https://mirror.yandex.ru/mirrors/guix/ > > This mirror is hosted on Yandex infrastructure, and should be very well > reachable from Russia and surrounding countries (CIS, Asia, ...). Nice, t

Re: Branches and other updates

Hi! Andreas Enge writes: > Apparently they do not work with feature or team branches, as we had > decided to do during Guix Days 2024, but instead all commits go to a > separate staging branch, which is continually built. If this works out > well, then the branch is pushed to master. If not, the

Re: Revisiting the "ChangeLog" style.

Hi, Maxim Cournoyer writes: >> I don’t think that’s related, is it? I think few of us care whether >> people use two spaces in commit messages, but I’d personally be more >> picky in text snippets because I find it clearer… > > It's related in that we're discussing contributing guidelines that

Re: GNU Shepherd 1.0.6 released

Hi, Maxim Cournoyer writes: > Ludovic Courtès writes: > > [...] > >> Yes, ‘sudo herd status TAB’ cannot work because it would need to run >> ‘sudo herd status’ to get the list of available services. > > Maybe i could run this once and cache the result? I think I

Re: Thoughts on setting a minimum requirement for committing changes, and the contribution model in general.

Hello, Hilton Chain writes: > These thoughts began as an attempt to think if there's a possibility to > develop > Guix without committers[1]. I agree with this principle; I think it is a goal for several of us and the motivation for some of the tooling, in particular QA. That is compatible wi

Re: Introducing Guixotic, a Guix/Guile worker cooperative

Hey, Long live, Guixotic! You’ve assembled a beautiful team and a lovely project! I wish you success!! Ludo’.

Re: Introducing Guixotic, a Guix/Guile worker cooperative

Hello, Edouard Klein writes: > I run guix-hosting.com which does not have enough clients to sustain me, > and because I hate myself everytime I do any form of marketing, it does > not grow. Heh. :-) (I’ve looked again at the web site and at the API you’ve developed, with the threading macro,

Re: GCD005: Regular and efficient releases (Accepted)

Hey, Steve George writes: > The collated results from the decision on GCD 005 are that it's *Accepted*. This is good news! Time to roll up our sleeves to make the November release a reality. Thanks for your work on this GCD! Ludo’.

Re: Revisiting the "ChangeLog" style.

Hello, Maxim Cournoyer writes: > Thanks for taking the time to research and write this reply. I think you > bring good and well researched points, including our current odd > convention to use double spaces. > > What do other think? I would tend to also think going through a GCD to > be overkill

Re: GNU Shepherd 1.0.6 released

Hello, Kaelyn writes: > I just checked in a convenient terminal, and it does appear there is > bash-completion for Shepherd. 'herd TAB' gets completions for me, as > well as 'herd status TAB' showing my user Shepherd service names. The > one thing that doesn't seem to work is 'sudo herd status T

GNU Shepherd 1.0.6 released

We are glad to announce version 1.0.6 of the Shepherd, the next bug-fix release in the 1.0.x series. Check out the web site to learn more about the Shepherd 1.0.x series: https://gnu.org/software/shepherd/news/2024/12/the-shepherd-1.0.0-released/ • About The Shepherd is a service manager wr

Re: Committers: create and share your Codeberg account

Hi Oleg, Oleg Pykhalov writes: > My account https://codeberg.org/wigust Added to guix/guix. Let us know if anything isn’t working as intended. Thanks, Ludo’.

Re: Committers approving pull requests

Hello, Maxim Cournoyer writes: > Thanks, I'm sure the .patch suffix (ala Github) will come in handy. I think I shared it before, but I have this alias in ~/.gitconfig: --8<---cut here---start->8--- [alias] merge-pull-request="!m() { for id in $(git c

Re: Committers approving pull requests

Hello, Andreas Enge writes: > I have recently been surprised by committers approving pull requests, > wondering why they did not instead push them themselves. I occasionally do this to express approval right away when I know I won’t be able to push it before some time (for instance because my w

Re: Shepherd load guix packages

Hi Thijs, Sorry for the late reply. Thijs writes: > I am wondering if it possible for Shepherd to load services using a > guix package. > `herd load root ` > > I tried variations on > ``` > (define-module (testd) >   #:use-module (guix gexp) >   #:use-module (shepherd service) >   #:use-module

Re: Shepherd: flaky self tests

Hi Simon, Simon Josefsson writes: > Below is the log file. > + shepherd --version > ;;; WARNING: loading compiled file > /usr/lib/x86_64-linux-gnu/guile/3.0/site-ccache/fibers.go failed: > ;;; In procedure load-thunk-from-memory: incompatible bytecode version > ;;; WARNING: loading compiled fi

Re: Shepherd: flaky self tests

Hi Simon, Simon Josefsson writes: > Ludovic Courtès writes: [...] >> ++ wc -l >> + test 22 -le 18 >> >> This is the same as <https://issues.guix.gnu.org/77132>. >> >> Could you instrument it as I suggested there? > > I'm still seein

Re: xlibre X11 server

Hello, Ekaitz Zarraga writes: > So yeah, spacecadet, if you really want to continue to package it, we > would add it to Guix, I don't think there's any policy in Guix against > it (unless their documentation or so is also part of the package and > includes political messages that promote any kin

Re: [bug#78332] GCD005: Regular and efficient releases (submitted)

Hi Greg, Greg Hogan writes: > My opinions on the project release cadence are of no greater > consequence than the update frequency or inclusion of any individual > package by a contributor or team. Most of this GCD can simply be > merged into the project documentation, which can then be updated

Re: bug#78047: WiFi stops working if managed with NetworkManager after migration to unprivileged guix daemon

Hi, Danny Milosavljevic writes: > Your change LGTM! Pushed as 436a00be92c53f5054885eebd200153933b63a1d. > P.S. I also found an extra spot in man/NetworkManager.xml : > > > NetworkManager will execute scripts in the > /etc/NetworkManager/dispatcher.d directory or subdirectories in

Re: [bug#78332] GCD005: Regular and efficient releases (submitted)

Hello, Steve George writes: > -- >8 -- >8 > > * %system_packages: packages required to boot and install a minimal Guix > System > or install Guix on a foreign distribution. This only includes default > options **required** by the installer which **must** work for a release > since > the

Re: Problems with grafts and Gtk (and probably with most other dynamic things)

Hi Maxim and all, Maxim Cournoyer writes: > Ludovic Courtès writes: [...] >> I believe this was discussed in <https://issues.guix.gnu.org/75157>. >> Perhaps we should start from there, possibly considering a revert or >> change of strategy of commit 482fda2729c3e

Re: config.scm-builder and content-address?

Hello, Simon Tournier writes: > Here the difference comes from config.scm-builder which stores the URL. > >(define %channel-metadata > (quote > (repository >(version 0) >(url "https://git.guix.gnu.org/guix.git";) >(branch "master") >

Re: GNOME 49’s dependencies on systemd

Hello, Noé Lopez via "Development of GNU Guix and the GNU System distribution." writes: > I started a thread on GNOME discourse[1], to create direct discussion with > the developers on their side. > > The author of the blog post responded, it seems they are willing to > collaborate and help us

Re: Guile needs your help

Hello, Olivier Dion writes: > I know that Guix has decided to move to CodeBerg. Maybe Guile could do > the same. This was briefly discussed at the Guix Days, and I think Andy and I agree that this would be a good move. I’m still digesting the previous migration :-) but I’m happy to help other

Re: GNOME 49’s dependencies on systemd

Hello, Liliana Marie Prikler writes: > Seeing how we're currently stalled on 48 already (mostly due to GTK > failing, but there are some more issues closer to core packages), I > think we should take our time and directly go towards a working userdb > replacement. Either we can strip out userdb

Re: Milestones on CodeBerg

Hi Oleg, Sharlatan Hellseher writes: > I accidentally found this next to issues, it looks like a nice way > to group some related issues and merge requests. > > Some draft https://codeberg.org/guix/guix/milestone/20775 Yes, milestones look like a useful feature to get a high-level view of goals

Continuous integration for pull requests

Hello, Christopher Baines writes: > Say ci.guix.gnu.org did start doing builds based off of Pull Requests > and sending that data to data.qa.guix.gnu.org, […] I don’t think that’s a reasonable plan. Cuirass works well for Guix-Science & co. on a single architecture, but I suspect it would not

Re: GCD005: Regular and efficient releases (submitted)

Hi Steve, Steve George writes: >> Perhaps I overlooked it, but it’s not clear to me how package sets >> affect the release process. >> >> I would expect things like “package set X must successfully build on all >> Primary Architectures at time of release”, “package set Y is provided on >> a bes

Re: GCD005: Regular and efficient releases (submitted)

Hello, Efraim Flashner writes: >> > • “Core” packages that anyone may wish to install on any of the >> > architectures supported by Guix (not Guix System). >> > >> > This was ‘%base-packages’ in >> > >> >

Re: Issues and pull requests labels on Codeberg.

Hilton Chain writes: > Hilton Chain writes: > >> For label proposals, please reply to this mail, with name, color and >> description. > > I propose to add labels as a way to communicate deprecations: > > https://guix.gnu.org/manual/devel/en/html_node/Deprecation-Policy.html > > * Prefix: depreca

Re: GCD005: Regular and efficient releases (submitted)

Hi Steve, Thanks for the hard work on this crucial aspect of the project. Some wondered about the indented audience of releases. To me it’s quite clear that it’s manifold: there’s public relation, yes, but also downstream packagers as mentioned, and perhaps more importantly, any new person insta

Re: CI is broken

Hi John, John Kehayias writes: > Seems to be happening again :( > > E.g. the current evaluation of mesa-updates > https://ci.guix.gnu.org/eval/2063113 with log > https://ci.guix.gnu.org/eval/2063113/log/raw and the issue in there I > see is > > uncaught throw to %exception: (#<&store-protocol-er

Re: Impossible to push patches to codeberg

Hi, Guillaume Le Vaillant writes: > Ludovic Courtès skribis: > >> After a fruitless debugging session with Vagrant on IRC, I opened this >> issue: >> >> https://codeberg.org/Codeberg/Community/issues/1974 >> >> Ludo’. > > Hi. > Gusted'

Re: bug#78047: WiFi stops working if managed with NetworkManager after migration to unprivileged guix daemon

Hi, Danny Milosavljevic writes: > Maybe for a really really paranoid way we could replace the check by a > check whether geteuid() == st_uid, no ? The idea being that the check > wouldn't change behavior if it's actually run as root and would change > behavior if it's run as your real user. Bu

Re: bug#78047: WiFi stops working if managed with NetworkManager after migration to unprivileged guix daemon

Hello, Ludovic Courtès writes: > So I’m tempted to just remove the check, but I’d rather have more > eyeballs on this: > > diff --git a/src/core/nm-core-utils.c b/src/core/nm-core-utils.c > index 895a991..738f8c7 100644 > --- a/src/core/nm-core-utils.c > +++ b/src

Re: issue on postgresql

Hi, Antonio Carlos Padoan Junior writes: > I saw today that the ticket is already closed and the solution is a kind > of dummy loopback service. Thanks. Yes, it should work now. > I think it would be nice to update guix cookbook as well (the system > container section). I would like to help wi

Re: Extra commits pushed on Savannah

"Leo Famulari" writes: > On Thu, Jun 5, 2025, at 07:59, Ludovic Courtès wrote: >> (Ideally we the Savannah folks would install pre-receive hooks to >> prevent accidental pushes, but I suspect they’re not too keen on doing >> that sort of thing.) > > We coul

Re: Moving translations of Guix away from Fedora Weblate

Hello, "pelzflorian (Florian Pelz)" writes: > Now Ekaitz, Gabor, Ludovic discussed if this needed to involve community > in a GCD with ≥1-month discussion period and decision. I believe this > mere announcement and guix-devel discussion is more suitable, since none > of the other teams’ members

Re: Extra commits pushed on Savannah

Hi Leo, "Leo Famulari" writes: > While the details are being handled, can we remove more people from > the Guix Savannah group? Or is the current membership already the > minimum possible? As I wrote back then, I left everyone who was marked as “admin” of the project. We can strip it further,

Re: Extra commits pushed on Savannah

Hi, Ludovic Courtès writes: > Ludovic Courtès writes: > >> I’ve joined #savannah on Libera.Chat asking for help. > > Update: they’re looking into it. The ‘master’ branch on Savannah is now in sync with Codeberg, thanks to the Savannah volunteers. Ludo’.

Re: CI is broken

Ian Eure writes: >uncaught throw to %exception: (#<&store-protocol-error message: >"reading file >`/gnu/store/9kqd85xgbgdng03nia2q12nl05w5b6yi-sbm-0.9.tar.gz.drv': >No such file or directory" status: 1>) >In thread: >uncaught throw to %exception: (#<&store-protocol-err

Re: Impossible to push patches to codeberg

After a fruitless debugging session with Vagrant on IRC, I opened this issue: https://codeberg.org/Codeberg/Community/issues/1974 Ludo’.

Re: codeberg migration: fj.el guidance please

Hi, Christopher Howard writes: > Hi, I'm trying to use fj.el to interact with codeberg, as indicated in > the migration GCD. I am able to view my own repos and issues, but I'm > confused as to which command allows me to view the guix repo and > issues. Can somebody help me out? Try ‘M-x fj-list

Re: Extra commits pushed on Savannah

Ludovic Courtès writes: > I’ve joined #savannah on Libera.Chat asking for help. Update: they’re looking into it. Ludo’.

Re: Impossible to push patches to codeberg

Guillaume Le Vaillant writes: > I still get the same error message: > > --8<---cut here---start->8--- > Énumération des objets: 37, fait. > Décompte des objets: 100% (37/37), fait. > Compression par delta en utilisant jusqu'à 32 fils d'exécution > Compression d

Re: Migration of the translation platform

This is now being discussed at: https://codeberg.org/guix/guix/issues/406 (Please avoid duplicating discussions across platforms.) Thanks for bringing it up! Ludo’.

Re: issue on postgresql

Hi, Antonio Carlos Padoan Junior writes: > I need some help, please. I’m having trouble with the PostgreSQL service > in a Guix System container. A few months ago, I had issues with the > system-log service (see my previous post below). I tried again today, > and I think the issue with system-lo

Re: Issues and pull requests labels on Codeberg.

Hello, Hilton Chain writes: >> Could you add a user-reviewed tag, color #006400 (same as qa’s >> reviewed-looks-good)? Since team members can review and formally approve pull requests (when doing a review from the web UI at least, one can click on “approve”; ‘fj.el’ doesn’t support it yet it se

Re: Extra commits pushed on Savannah

Hi Danny, Those 4 commits mean that someone pulling right now from a pre-migration Guix will end up in a branch that only exists there, and the next ‘guix pull’ will error out due to non-fast-forward update. Danny Milosavljevic writes: > I think the best course of action would be to force push

Re: Impossible to push patches to codeberg

Hello, Guillaume Le Vaillant writes: > I tried removing myself from the lisp team to check your hypothesis. > However it looks like I'm not a collaborator either anymore. I do see you among “collaborators” at https://codeberg.org/guix/guix/settings/collaboration (visible to “owners” I presume).

Re: CI is broken

Ian Eure writes: > Noticed that I was building an awful lot of stuff on a `guix system > reconfigure', so I went to look at CI, and, it’s badly broken. It > hasn’t successfully evalutated Guix since #2060816[1] on May 28th. > Since #2061131 on May 29th[2], all evaluations have failed with: > > >

Re: Impossible to push patches to codeberg

Hello! Vagrant Cascadian writes: > > git push --set-upstream origin vagrantc-test > Enumerating objects: 44, done. > Counting objects: 100% (44/44), done. > Delta compression using up to 8 threads > Compressing objects: 100% (10/10), done. > Writing objects: 100% (35/35), 6.10 KiB |

Re: Committers: create and share your Codeberg account

Hi, "pelzflorian (Florian Pelz)" writes: > Could you add me as a contributor to > the artwork.git repo, because I would want to sync translations each > month. Done. Apologies for getting it wrong! Thanks, Ludo’.

Re: Broken pull requests

Hey, Noé Lopez via "Development of GNU Guix and the GNU System distribution." writes: > It’s fixed now! The pull requests can be accessed again, only the > requested team reviews have been lost. Great! Thanks for following up on this and apologies for breaking things! Ludo’.

Re: Problems with grafts and Gtk (and probably with most other dynamic things)

Hi Danny, I think you’re describing the problem that others pointed out earlier (there’s an open bug report IIRC) which is that grafting derivations do not necessarily produce all the outputs of the original derivation (so in one case you get a grafted ‘glib’ with just “out”, and in the other case

Re: Team members: create and share your Codeberg account

Hello, Ludovic Courtès writes: > Yes, definitely: if you’re a team member and not a committer, please > share your Codeberg account name here! I committed <https://issues.guix.gnu.org/78568> and added Codeberg account names for people who gave it here. So for instance Noé is now

Re: Committers: create and share your Codeberg account

Hi jgart, Could you sign your message? https://lists.gnu.org/archive/html/guix-devel/2025-05/msg00072.html Thanks in advance, Ludo’.

Spring cleanup: cut some branches!

Hello Guix, There are currently 109 branches in the repo: https://codeberg.org/guix/guix/branches I suspect that the previous mirroring job (from Savannah to Codeberg) would create branches but never propagate deletions. Anyway, that’s a lot of branches, so please take a look and delete those

Re: Migration to Codeberg effective on May 25th

Ludovic Courtès writes: > The main Guix repository will migrate to <https://codeberg.org/guix> in > a few days, on Sunday May 25th, 2025. > > At that point, its canonical URL will become: > > https://git.guix.gnu.org/guix.git The migration completed yesterday. Ple

Team members: create and share your Codeberg account

Hello, Noé Lopez writes: > Is it possible to do a similar thread for non-committers to get added to > our teams? Yes, definitely: if you’re a team member and not a committer, please share your Codeberg account name here! > AFAIK, getting added to a team on Codeberg does not necessarily give >

Re: Codeberg migration complete

Ludovic Courtès writes: > Definitely. We could take inspiration from the default sets of labels > they propose and tweak it? Hilton added labels, see <https://codeberg.org/guix/guix/issues/33>. Ludo’.

Re: I already broke master :)

Hello, Ian Eure writes: >> I temporarily disabled branch protection on ‘master’ so I could >> force-push and then re-enabled it; I also clicked on “require signed >> commits” there: >> >> https://codeberg.org/guix/guix/settings/branches/edit?rule_name=master > > Thank you very much for cleanin

Re: Committers: create and share your Codeberg account

Hello, John Kehayias writes: > Arg, this is a ProtonMail bridge issue, it drops the signature to use my > ProtonMail key. I've been meaning to go back to this issue to see what > the problem was with some encrypted emails in the past, but just now > found out this detail of rewriting messages (s

Re: Codeberg migration complete

Hi, Ian Eure writes: > Do we want to add some labels for the issue/PR types? Semes like > "security" and "bug" are two we’d want. Definitely. We could take inspiration from the default sets of labels they propose and tweak it? https://forgejo.org/docs/latest/user/labels/ https://codeberg

Re: I already broke master :)

Hi, Ian Eure writes: > Well, I managed to push an unsigned commit > (ea779f0b6bf7954327671b98bb93482a28fad668) to master, since the > pre-push hook doesn’t work yet[1]. > > Ludo’, could you remove that commit and force-push? Or rebase and > sign it, then force-push? I temporarily disabled bran

Re: Problems with grafts and Gtk (and probably with most other dynamic things)

Hi Danny, Danny Milosavljevic writes: > There are multiple definitions (same package version) of the packages glib > (and gobject-introspection and python-pygobject), in the same Guix repo. So > far okay. > > But if you aren't very very careful [so basically always], you end up with > differ

Re: Committers: create and share your Codeberg account

Hi John, John Kehayias writes: > Mine is I can’t verify the signature on this message. Could you use a different method, for instance by using ‘gpg -s --clear-sign’ on the message? Thanks in advance, Ludo’.

Codeberg migration complete

Group memberEric Bavier View Skills Watch partner Group memberGiovanni Biscuolo Set to private Watch partner Group memberChristopher Baines Set to private Watch partner Group administrator Ludovic CourtèsSet to private --- Group memberChristine L

Re: Codeberg migration check list

Hi, Cayetano Santos writes: > Not directly related to guix maintained infra, but I think we need a > collaborative effort towards pining ancillary sites still referring to > former guix.savannah. Repology [0] is one of them, but I’m sure there > are many others around. I think this can be a dis

GNU Shepherd 1.0.5 released

We are glad to announce version 1.0.5 of the Shepherd, the next bug-fix release in the 1.0.x series. Check out the web site to learn more about the Shepherd 1.0.x series: https://gnu.org/software/shepherd/news/2024/12/the-shepherd-1.0.0-released/ It is also the first release made from its new

Re: Codeberg migration check list

Ludovic Courtès writes: > Tomas Volf <~@wolfsden.cz> writes: > >> I think before the import, you should remove write permissions from >> everyone (except you), to make sure people do not push to savannah by >> mistake. Sorry if that was already planned somewhere

Re: Codeberg migration check list

Hello, Noé Lopez writes: > Is it possible instead to rename guix-mirror to guix instead, as that > would create an http redirection? Yes! I had that thought overnight too, and indeed, that’s much better. I’ll do that. Thank you! Ludo’.

Re: Codeberg migration check list

Ricardo Wurmus writes: > Ludovic Courtès writes: > >> - [ ] Git repository imported *Sunday* >> - [ ] git.guix.gnu.org redirect changed to codeberg.org/guix >> *Sunday* > > I'm a little confused about this. We currently have > https://codeberg.or

‘guix_mirror_bot’ account on Savannah

Hello, I’ve created the ‘guix_mirror_bot’ account on Savannah and added it to the ‘guix’ group. On Sunday, once the repo has migrated, I’ll set up SSH-based mirroring on Codeberg so that it pushes to Savannah as ‘guix_mirror_bot’: https://forgejo.org/docs/latest/user/repo-mirror/#mirror-via-ss

Re: Codeberg migration check list

Hi, Tomas Volf <~@wolfsden.cz> writes: > I think before the import, you should remove write permissions from > everyone (except you), to make sure people do not push to savannah by > mistake. Sorry if that was already planned somewhere and I have just > missed that. I guess I’ll do that, but ke

Codeberg migration check list

Hello Guix! Ludovic Courtès writes: > The main Guix repository will migrate to <https://codeberg.org/guix> in > a few days, on Sunday May 25th, 2025. Here’s the check list I came up with for the main repository migration, based on <https://codeberg.org/guix/guix-consensus-docum

Migration to Codeberg effective on May 25th

As a reminder, migration of the Guix repositories to Codeberg as described by the Guix Consensus Document (GCD) 002 was accepted on May 7th: https://codeberg.org/guix/guix-consensus-documents/src/branch/main/002-codeberg.md The main Guix repository will migrate to i

Re: bug#76296: [PATCH maintenance] hydra: bayfront: Set up ‘git.guix.gnu.org’ as a redirect to Savannah.

Hello, Ludovic Courtès writes: > If we choose to install this patch, we should IMO do it as before > guix.git is migrated to Codeberg (presumably on May 25th). That way, we > can use git.guix.gnu.org in (guix channels) instead of > codeberg.org/guix/guix.git. We had a bunch of i

Re: 504 Gateway Time-out on https://qa.guix.gnu.org/

Hi, "nomike (they/them)" writes: > qa.guix.gnu.org is unreachable for at least 18+ hours, probably longer. > Could someone have a look at what's up? There have been troubles with bayfront, the server hosting this service and a few others, including guix.gnu.org. However I believe qa.guix.gnu.o

Re: branch master updated (a98cd5a6bd -> 57ea6d3d59)

Hello, Danny Milosavljevic writes: > Ok, guix time-machine with local directory ran through successfully. > > Can you confirm that it works for you, too? It’s all good, thank you! It’s a massive rebuild though, ~20k builds: https://ci.guix.gnu.org/eval/2059220 Any idea what causes this?

Re: branch master updated (a98cd5a6bd -> 57ea6d3d59)

Hi Danny, guix-comm...@gnu.org writes: > dannym pushed a change to branch master > in repository guix. > > from a98cd5a6bd gnu: emacs-org-node: Update to 2.4.2. [...] > new 7ba6e6f090 gnu: Add rust-gix-worktree@0.39.0. > new a80e6deb7d gnu: Add rust-gix-worktree-state@0.17.0. >

Re: bug#78047: WiFi stops working if managed with NetworkManager after migration to unprivileged guix daemon

Hello, Ludovic Courtès writes: >>> 2025-04-24 10:34:15 localhost NetworkManager[852]: >>> [1745483655.8537] plugin: skip invalid file >>> /gnu/store/agadky1p0ba367avf524sh5wmcdxcxb1-network-manager-1.52.0/lib/NetworkManager/1.52.0/libnm-device-plugin-wwan.so: >>

Re: branch master updated: gnu: rlottie-for-telegram-desktop: Do not inherit.

Hey Oleg, guix-comm...@gnu.org writes: > commit 475e8802c3d2c67c84cedfda4e66b6b59d8a9e36 > Author: Sharlatan Hellseher > AuthorDate: Sun May 18 20:32:37 2025 +0100 > > gnu: rlottie-for-telegram-desktop: Do not inherit. The other option (probably more common and preferable) is to move the pa

Re: [bug#76296] [PATCH maintenance] hydra: bayfront: Set up ‘git.guix.gnu.org’ as a redirect to Savannah.

I wanted to deploy this patch now so we can start testing it and since the goal was to migrate guix.git next Sunday (May 25th). Unfortunately, we seem to be unable to connect to the machine hosting our DNS service (bayfront) so I’m not sure when we’ll be able to deploy it. Bad timing. :-/ Ludo’.

Re: [bug#76296] [PATCH maintenance] hydra: bayfront: Set up ‘git.guix.gnu.org’ as a redirect to Savannah.

Hello, Ahmad Draidi writes: > I guess this would make switching, in case of disasters, seamless for > the user, which is probably something we want. The URL doesn't > change. On Guix project's side, it's a relatively quick change. The > extra load is probably negligible also. No need to proxy th

Re: Preparing for Git repository migration

Hello, Rutherther writes: > see > https://blog.codeberg.org/new-storage-limits-on-codeberg-what-you-need-to-know.html > for news on codeberg storage usage - 750 MB for git repos per user/org. I hadn’t realized this was also per-org. I filed a request for more storage, as the blog post suggests

Re: guix.vim repository

Hello, Efraim Flashner writes: > Currently I'm the only contributor to guix.vim. Seeing how much action > the emacs-guix plugin has been getting over the past few days now that > it's at codeberg I think it would be good if we were to move the > upstream repo to be under the guix organization.

Re: Improve guix-daemon by new C++ features

Hi, Congcong Kuo writes: > For path manipulating function they are not related to read/write > files and path is just a kind of data structure. In > nix/libutil/libutil.cc, paths are simply represented and processed as > string. I think it can be easily replaced using C++ standard library > with

Re: Improve guix-daemon by new C++ features

Hi, Congcong Kuo writes: > In nix/libutil/util.cc there are lots of functions related to > copy/delete files and manipulate file paths. In C++ 17 the standard > library’s provides the same functionality which is more > reliable. > > guix-daemon uses Boost.Format to generate formatted string. Th

The 🐑 Shepherd on Codeberg

Hello Guix, I have migrated the Shepherd repositories to Codeberg, where they’re now in good company: https://codeberg.org/shepherd I restored commit rights for the handful of people who had commit rights on Savannah, and also updated the web site. Let me know if you spot any issues! Ludo’.

Re: bug#76296: [PATCH maintenance] hydra: bayfront: Set up ‘git.guix.gnu.org’ as a redirect to Savannah.

Hi, Ricardo Wurmus writes: > Noé Lopez writes: > >> I guess its for style points, which I’m all for. I do think it would >> be >> better to set the URL to git.guix.gnu.org/guix/guix.git and just a >> DNS >> redirect to codeberg to avoid the extra connection. > > I second this. > > I think a DNS

Re: Preparing for Git repository migration

Arun Isaac writes: >> I’m also happy to add your account to the “owners” team; let me know >> when you have one. > > I already have an account. Here it is: https://codeberg.org/arunisaac Added, thanks!

Resource usage on Codeberg

For the record, I reached out to Codeberg e.V. regarding storage and bandwidth usage induced by Guix, to which they replied that they “expect this to be fine”: https://codeberg.org/Codeberg-e.V./requests/issues/784 Ludo’.

Re: [bug#76503] [GCD] Migrating repositories, issues, and patches to Codeberg

Hi Steve, Steve George skribis: > Reflecting things that we agree on: I will try and avoid the word 'vote'. > I'll rename to 'deliberation-record' (1). And, will use 'Deliberation record' > elsehwere. Sounds great to me. > Things we don't agree on: I don't see a way to avoid the verb "vote"

Re: Preparing for Git repository migration

Hello, Arun Isaac writes: >> Looking at , there’s one >> repository I forgot to mention (shame on me): mumi. >> >> Arun, should I let you migrate it? Let me know what you prefer. > > Since you're already familiar with the process, it might be easier for

Re: Preparing for Git repository migration

Hello, Efraim Flashner writes: > Can we also ask the Savannah admins to change the cgit clone URIs for > the repos that have been moved over? Is it feasible? I would think that Cgit has those hardcoded, no? Ludo’.

Re: Preparing ungrafts

Greg Hogan writes: > On Mon, May 12, 2025 at 11:34 AM Ludovic Courtès wrote: [...] >> Also, once ‘core-packages-team’ is merged (or with a tweak to exclude >> the glibc graft), I’d like to resume my experiment in auto-ungrafting: >> >> https://issues.guix.gnu

  1   2   3   4   5   6   7   8   9   10   >