Re: How (not to) deal with upstreams that have _extremely_ toxic maintainership Was: xlibre X11 server

On 2025-08-01 19:03, spacecadet wrote: On 8/1/25 4:42 PM, Ekaitz Zarraga wrote: Just for the record, I don't know if it was the maintainer, but I believe it was, that came to this mailing list and insulted some people (myself included). this mailing list? I'd be surprised, could have been a t

Re: How (not to) deal with upstreams that have _extremely_ toxic maintainership Was: xlibre X11 server

Hello spacecadet, On 2025-08-01 17:03, spacecadet wrote: On 8/1/25 4:42 PM, Ekaitz Zarraga wrote: ... the devs are trying to make good relations with any distros/DEs/DMs they can. I haven't brought up guix to them since I don't consider myself a representative of the distro, but if anyone's

Re: How (not to) deal with upstreams that have _extremely_ toxic maintainership Was: xlibre X11 server

On 8/1/25 4:42 PM, Ekaitz Zarraga wrote: Just for the record, I don't know if it was the maintainer, but I believe it was, that came to this mailing list and insulted some people (myself included). this mailing list? I'd be surprised, could have been a troll or a schizo, there's been a handfu

Re: How (not to) deal with upstreams that have _extremely_ toxic maintainership Was: xlibre X11 server

On 7/31/25 11:09 PM, Denis 'GNUtoo' Carikli wrote: But here we are talking about maintainers specifically discriminating people in very violent ways, during their role as a maintainer, so we probably all agree that this is way too dangerous, and that this is bad, and that it needs to be avoided.

Re: How (not to) deal with upstreams that have _extremely_ toxic maintainership Was: xlibre X11 server

On 2025-08-01 18:34, spacecadet wrote: Most of what you wrote boils down to "what if" the maintainers make some bad decision or yell at a packager. Just for the record, I don't know if it was the maintainer, but I believe it was, that came to this mailing list and insulted some people (myself

Re: How (not to) deal with upstreams that have _extremely_ toxic maintainership Was: xlibre X11 server

packaging or to members of Debian or generally unpleasant to work with. Also, quoting the Debian Reference manual²: If you find that the upstream developers are or become hostile towards Debian or the free software community, you may want to re-consider the need to include the software in Debian. S

Re: GNOME 49’s dependencies on systemd

Rutherther writes: > Hi Noé, > > Noé Lopez writes: > >> >> Hi again, >> >> As I have it working now, there is no dependency on guix-home. Simply, >> on session start an shepherd instance is started for GNOME. Completely >> independently from your home shepherd if you have one. > > Thanks for the

Re: Farewell to the Change-Id: trailer

>ven. 01 août 2025 at 15:02, Maxim Cournoyer wrote: > Hello, > > I'm proposing to remove the automatically added Change-Id git trailers > to our commit messages, for reasons explained in the commit message of > the commit at . In a > nutshell, Codeberg

Re: Farewell to the Change-Id: trailer

On 2025-08-01 08:02, Maxim Cournoyer wrote: Hello, I'm proposing to remove the automatically added Change-Id git trailers to our commit messages, for reasons explained in the commit message of the commit at . In a nutshell, Codeberg makes these mostly i

Re: Merge conflict in etc/git/gitconfig leads to unusable git commands

Hi Tomas, Tomas Volf <~@wolfsden.cz> writes: > Hi, > > so, in guix repository we include ../etc/git/gitconfig in the > .git/config. I get the motivation for that, but I wanted to raise a > down side that I encountered today. I have fetched the upstream Guix > and went on to merge the updates, b

Re: xlibre X11 server

Hi, > X.org is not getting developed further, but Xlibre is trying to > update the codebase. I would also like to note that Wayland is still not a drop-in replacement for Xorg, even with a compatibility layer, and it's not necessary a problem either as long as people can choose. For instance I s

Re: [doc] Overhauling contributing.texi

re of important knowledge it could use some > (re-)structuring, some updates and some extensions. > > I am looking forward to crafting patches in this regard, but first i > would like to hear some opinions. > > > My suggestions can be summarized as follows: > > 1. Hier

Re: GNOME 49’s dependencies on systemd

Hi Noé, Noé Lopez writes: > > Hi again, > > As I have it working now, there is no dependency on guix-home. Simply, > on session start an shepherd instance is started for GNOME. Completely > independently from your home shepherd if you have one. Thanks for the info. I haven't really checked th

Re: Revisiting the "ChangeLog" style.

Hi, Attila Lendvai writes: > On Friday, July 25th, 2025 at 01:46, Gabriel Wicki wrote: > >> that had a sense of: "Oh, this is what hackers used to do in the olden >> days", meaning: doing things the way they make sense. I feel our > > > it made sense when software distribution happened with tar

Re: cross-shells - get a cross compilation environment in your guix shell!

Hi Christoph, Christoph Buck writes: > Rutherther writes: > >> Hi all! > > Hi Rutherther! > >> There seems to be a procedure that is supposed to somewhat take care of >> this, 'package->development-maifest', but this procedure doesn't really >> do everything necessary. First of all, even if t

Re: Alist and serializer backed service configuration?

On 2025-04-02 16:36, Hilton Chain wrote: > Hi Guix, > > (Cc'd the Home Team) > > Lately, Andrew's proposal[1] on using free-style configurations for services > came to my mind again. Ludovic was againt it for potential generation of > invalid config files and obscure error messages. But how abou

Re: Committers: create and share your Codeberg account

Hi Guix, Ludovic Courtès writes: > To avoid problems, I suggest you send your account name as a public > reply to this message, in a signed message. I am pgarlick; https://codeberg.org/pgarlick Best regards, Paul. signature.asc Description: This is a digitally signed message part

Re: Informal Guix 1.4.0 branch and security fixes?

Hi all, I am also a Debian Developer, and I'd really like to try to get this taken care of in time if possible--without getting into my whole spiel, I think being able to support usage of Guix as it is at any given time (rather than HEAD-only) is important. However, when I try to do a minimal

Re: Revisiting the "ChangeLog" style.

On Friday, July 25th, 2025 at 01:46, Gabriel Wicki wrote: > that had a sense of: "Oh, this is what hackers used to do in the olden > days", meaning: doing things the way they make sense. I feel our it made sense when software distribution happened with tarballs and there were no VCS systems.

Re: Informal Guix 1.4.0 branch and security fixes?

On 2025-07-27, Kurt Kremitzki wrote: > I am also a Debian Developer, and I'd really like to try to get this taken > care of in time if possible--without getting into my whole spiel, I think > being able to support usage of Guix as it is at any given time (rather than > HEAD-only) is important.

Re: GitHub hash mismatch?

Noé Lopez writes: > [..] > > So… I have no idea what happened. I would check SoftwareHeritage to see > if they have evidence of a version from that time but it does not load > today. Git tags are not immutable. So the most likely explanation is that the upstream made a git tag for 1.2.0, later

Re: GNOME 49’s dependencies on systemd

Hi, Noé Lopez writes: [...] > As I have it working now, there is no dependency on guix-home. Simply, > on session start an shepherd instance is started for GNOME. Completely > independently from your home shepherd if you have one. Sounds good, thanks for having worked on it! -- Thanks, Maxim

Re: Revisiting the "ChangeLog" style.

Hi Gabriel, Gabriel Wicki writes: > I actually really liked learning to try to write concise, helpful commit > messages when starting to contribute to Guix. It was probably one of > the steeper parts of the learning curve but also one of the few things > that had a sense of: "Oh, this is what h

Re: cross-shells - get a cross compilation environment in your guix shell!

Hi! Here is the missing link to my post: > https://lists.gnu.org/archive/html/help-guix/2024-05/msg00141.html Sorry for the noise! -- Best regards Christoph Buck GnuPG key: https://web.icepic.de/public_key.txt FingerPrint: B43F 4D2B 2017 E715 36C0 03C6 B8BB BCDE CD00 3305

Re: cross-shells - get a cross compilation environment in your guix shell!

Rutherther writes: > Hi all! Hi Rutherther! > There seems to be a procedure that is supposed to somewhat take care of > this, 'package->development-maifest', but this procedure doesn't really > do everything necessary. First of all, even if target is supplied, for > whatever reason the inputs y

Re: irc and potential users

Hi, Cayetano Santos writes: > Hi Guix, > > Our web site guix.gnu.org, under "Help/IRC Chat" redirects to > https://web.libera.chat/, where the nick is pre-filled. People usually > pick the default one, so that different users may have same nicks, > same user different nicks, and so on. O

Re: CI for a new branch

Hi Gabriel, Gabriel Wicki writes: > Howdy! > > Since gaining commit access I took up my work as sole team-audio > member. I added an `audio` branch to our repo and have already 3 > commits which a plethora of packages depend upon. > > Hence here my question: where can I add the cuirass specific

Re: CI for a new branch

On Fri, Jul 25, 2025 at 11:03:35AM +0200, Andreas Enge wrote: > > I know how to create branch evaluations, and have just done so for the > > audio-team branch, with builds on x86_64 and i686. Thank you! > And now I see that you called the branch "audio". I would suggest to > keep with the "audio-t

Re: Branches and other updates

Hi Vincent, Vincent Ambo writes: > Andreas Enge writes: >> Well, sending everything to master seems quite impossible to me, and >> it should be the same in Nix as in Guix. All the time we get patch >> level updates to packages that are deep in the package graph and cause >> enormous rebuilds. >

Re: Committers approving pull requests

Hi Cayetano, Cayetano Santos writes: [...] > So we have committers (=maintainers), groups members and regular users. > Those who are allowed to approve pr are maintainers and group members > (regular users too?). I thought I'd clarify the terminology used in the Guix context: co-maintainers an

Re: cross-shells - get a cross compilation environment in your guix shell!

Hi Gabriel, Gabriel Wicki writes: > Interesting! Do I understand correctly that these are like manifests, > but work for cross-compilation contexts? Yes. You can choose what packages are native inputs (same as packages->manifest), what ones are target (those are runnable on the build system,

Re: cross-shells - get a cross compilation environment in your guix shell!

Interesting! Do I understand correctly that these are like manifests, but work for cross-compilation contexts? So that `gcc` would be linked to a gcc-arm-none-eabi, and the needed libraries also ready to use/link against for the specified architecture? So, kind of like a `guix shell -D u-boot --

Re: CI for a new branch

Hi Gabriel, You need someone to give you a client certificate, which you can configure your web browser to send to CI. That grants you the ability to add and edit cuirass specifications. On July 24, 2025 12:10:03 PM PDT, Gabriel Wicki wrote: >Howdy! > >Since gaining commit access I took up my

Re: GNOME 49’s dependencies on systemd

Noé Lopez writes: > Rutherther writes: > >> Hi Noé, >> >> Noé Lopez via "Development of GNU Guix and the GNU System distribution." >> writes: >> >>> Secondly, gnome-session (responsible for starting user services) is >>> going to use systemd too. So we need to replace it with a Shepherd >>> imp

Re: Commit Access for gabber

Hi Gabriel, Gabriel Wicki writes: Hi there! As of earlier today I was granted Commit Access to our Guix repositories, allowing me—as the only `audio` team member—to not just review but also merge Pull Requests. Congratulations and welcome! — Ian

Re: Introducing Guixotic, a Guix/Guile worker cooperative

Ludovic Courtès writes: > 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

Re: Committers approving pull requests

>lun. 21 juil. 2025 at 23:57, "nomike (they/them)" wrote: > Hi > > On 17.07.25 11:52, Cayetano Santos wrote: >> So, ... what is the conclusion regarding approvals ? >> Do we have a policy about this ? I feel like approved changes get >> committers away from them, as there is no need for a review

Re: GitHub hash mismatch?

Liam Hupfer writes: > Hi Guix, > > The Aporetic hash in Guix is > 1bb7js8lxa4f5kcjjvn587m4hd92qkydr5dbcjmimq2r8mimn75j: > > > But: > > ┌ > │ $ guix download --commit=1.2.0 https

Re: Committers approving pull requests

Hi On 17.07.25 11:52, Cayetano Santos wrote: So, ... what is the conclusion regarding approvals ? Do we have a policy about this ? I feel like approved changes get committers away from them, as there is no need for a review, already I work at Paysafe, a >4k online payments company and my role i

Re: Commit Access for gabber

On Sun, Jul 20, 2025 at 11:26 AM, Gabriel Wicki wrote: > Hi there! > > As of earlier today I was granted Commit Access to our Guix > repositories, allowing me—as the only `audio` team member—to not just > review but also merge Pull Requests. > Congrats and welcome! Great to have you on the team.

Re: Informal Guix 1.4.0 branch and security fixes?

On 2025-07-15, Vagrant Cascadian wrote: > On 2025-07-11, Denis 'GNUtoo' Carikli wrote: >> On Tue, 8 Jul 2025 21:01:58 +0200 >> Denis 'GNUtoo' Carikli wrote: > I applied your patches, but nix/libutil/seccomp.cc was not able to > compile on Debian: > > g++ -DHAVE_CONFIG_H -I. -I./nix -I./nix -Wdate

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: Branches and other updates

Hey Andreas, 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. This isn't quite correct. nixpkgs development almost always targe

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

> Andreas Enge andr...@enge.fr writes: > > > Am Sun, Jul 13, 2025 at 10:14:16PM + schrieb Attila Lendvai: > > > > > this is somewhat tangential, but guix is the first project in my entire > > > programmer career where it's not only allowed to commit changes that will > > > break > > > things

Re: Branches and other updates

ter 15 jul 2025 às 17:13:38 (1752610418), l...@gnu.org enviou: > 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 buil

Re: Branches and other updates

Andreas Enge writes: > Well, sending everything to master seems quite impossible to me, and > it should be the same in Nix as in Guix. All the time we get patch > level updates to packages that are deep in the package graph and cause > enormous rebuilds. Agree, let me rephrase: I think most thing

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

Andreas Enge writes: > Am Sun, Jul 13, 2025 at 10:14:16PM + schrieb Attila Lendvai: >> this is somewhat tangential, but guix is the first project in my entire >> programmer career where it's not only allowed to commit changes that will >> break >> things, but it's straight out demanded (the

Re: Welcome gabber as a new committer!

On Sun, Jul 20, 2025 at 12:45:58PM +0900, Maxim Cournoyer wrote: > Hello Guix, > > I'm happy to share that Gabriel Wicki has been provided with commit > access to the repository, having been vouched for by Andreas, Steve and > Leo F. > > Congratulations and welcome as a committer, Gabriel! (...)

Re: Branches and other updates

Hi Andreas, Andreas Enge writes: > [..] > > This should not be confounded with a merge train. If I understand it > correctly, a merge train of n commits consists in letting the ci system > run in parallel all 2^n-1 combinations of including a commit or not; > then out of the succeeding runs, it

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

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

Re: Welcome gabber as a new committer!

Maxim Cournoyer writes: > Hello Guix, > > I'm happy to share that Gabriel Wicki has been provided with commit > access to the repository, having been vouched for by Andreas, Steve and > Leo F. > > Congratulations and welcome as a committer, Gabriel! > > -- > Thanks, > Maxim Congratulations Gabr

Re: `search-input-file` and readability

> I may be missing something, and would love to hear your thoughts. i'm no authority in this, but i also had the same impression when the SEARCH-INPUT-FILE based solution showed up. on a related note, it also bothered me that i think SEARCH-INPUT-FILE really should be called FIND-INPUT-FILE. i

Re: Enhancement idea for --with-input transform

Hello Kurt, On July 18, 2025 12:14:12 PM GMT+08:00, Kurt Kremitzki wrote: >Hello all, > >I'd like to float an idea for an improvement to what's possible with package >transformations. This seems like it would be a good beginner contribution for >me (or anyone who might want to tackle it sooner

trying-guix blog post (was Re: New bordeaux mirror available in Russia)

Hi, Simon Tournier writes: [...] > PS: BTW, thank you for your post « Trying Guix: A Nixer's Impressions ». > Very nice read. :-) > > https://tazj.in/blog/trying-guix I just read it, and one thing that I'd like to bring to your attention is the way Emacs packages are handled. There's n

Re: `search-input-file` and readability

Hi Kurome, Kurome writes: > Hi Guix, > > 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-packag

Re: Introducing Guixotic, a Guix/Guile worker cooperative

Hi, > Rather, this is a way to allow us to work full-time contributing. The > idea is that paid projects, training, support, etc., will help > improve Guix and Guile for everyone, while also supporting us to do > more of the work we already love to do. As I understand it, there is a lot of potent

Re: Enhancement idea for --with-input transform

Hi, Kurt Kremitzki writes: [...] > Proposal > === > > I would like to amend the `--with-input` syntax to allow for both addition > and > removal, for example in the case of testing optional behavior or seeing if a > dependency can be removed (imagine a `foo-minimal` variant.) I don't hav

Re: Branches and other updates

Hi Andreas, Andreas Enge writes: > Am Tue, Jul 15, 2025 at 05:13:38PM +0200 schrieb Ludovic Courtès: >> How are these commits dropped, concretely? Do they get reverted by the >> person in charge of this staging branch? > I like the idea, this seems a faster way to iterate and similar to how we

Re: Introducing Guixotic, a Guix/Guile worker cooperative

Hi Luis! [...] > Excellent! Great to see it go live :) > > Good luck everyone! And thanks to you for having accepted to produced the Guixotic artwork! We're very happy about it! :-) -- Maxim

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 ? This >> would need discussion but I’d personally be fine listing at least >> cooperati

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

Am Tue, Jul 15, 2025 at 05:13:38PM +0200 schrieb Ludovic Courtès: > How are these commits dropped, concretely? Do they get reverted by the > person in charge of this staging branch? That is what I understood. In the Guix context, I would rather rebase interactively and drop the commits, but the e

Re: New bordeaux mirror available in Russia

Hi, On Thu, 10 Jul 2025 at 13:46, "Vincent Ambo" wrote: > we've set up a mirror of bordeaux.guix.gnu.org in Russia, available > here: https://mirror.yandex.ru/mirrors/guix/ Really cool! Thank you. > We decided not to backfill proactively, as the rolling release model of > Guix seems to reduce

Re: Committers approving pull requests

> I have recently been surprised by committers approving pull requests, > wondering why they did not instead push them themselves. It might make > sense when reacting to other committers (we never discussed whether it > would be more polite to let committers push their own commits, or okay > to pu

Re: Tagging issue?

Simon Tournier writes: > Hi, > > On Mon, 07 Jul 2025 at 12:26, Noé Lopez wrote: > >> For future reference, tagging is now available to all team members, it >> was simply a configuration issue where the teams had to be added to the >> repository to gain the permissions. > > Cool! Thank you. > >

Re: Introducing Guixotic, a Guix/Guile worker cooperative

Hi, On Mon, 14 Jul 2025 at 12:47, Ludovic Courtès wrote: >> If nobody has an objection to it, I think this could really help >> with the discovery of commercial services related to GNU Guix. > > Maybe you can draft a pull request together with Édouard and leave a bit > of time for others to comm

Re: GNU Shepherd 1.0.6 released

Hi, Ludovic Courtès writes: > 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 resul

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: Introducing Guixotic, a Guix/Guile worker cooperative

Hi Denis, Thanks for sharing your thoughts, ideas. I agree there are lots of possibilities/areas where Guix can be improved, and that's something we'll be trying to work on at Guixotic, ideally with funding, or in-between paid jobs :-). -- Thanks, Maxim

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

Hi Attila, Attila Lendvai writes: >> My work on Guix is dominated by bulk upgrades of hundreds of R >> packages. There is no point in submitting the upgrades >> individually. In fact, my work on Guix has become so dominated by > > > this is somewhat tangential, but guix is the first project in m

Re: Introducing Guixotic, a Guix/Guile worker cooperative

Hi Ludovic, Ludovic Courtès writes: > Hey, > > Long live, Guixotic! You’ve assembled a beautiful team and a lovely > project! I wish you success!! Yay, thank you for the kind words and for having been an inspiration throughout the years :-). -- Thanks, Maxim

Re: New bordeaux mirror available in Russia

Hi! Simon Tournier writes: > Well, maybe it could be helpful to backfill for some specific commits as > v1.4.0, and maybe the older ones too. I'd have to think about how to best do that (some combination of the mechanism of `guix weather` + our importer?). The nar-herder endpoint we're using to

Re: Tagging issue?

Hi, On Mon, 07 Jul 2025 at 12:26, Noé Lopez wrote: > For future reference, tagging is now available to all team members, it > was simply a configuration issue where the teams had to be added to the > repository to gain the permissions. Cool! Thank you. Can I be a member without having commit

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

Hilton Chain writes: I appreciate your work and I think it would be valuable if you can share what can be improved in [1] based on your experience. [1]: https://guix.gnu.org/manual/devel/en/html_node/Bulk-Updates.html Running `guix refresh` is only the first step. In almost every upgrade

Re: Introducing Guixotic, a Guix/Guile worker cooperative

Hi Edouard, On 9/07/25 11:37, Edouard Klein wrote: [...] 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. For what it's worth, I already knew about your service and it seems pretty good to

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: Introducing Guixotic, a Guix/Guile worker cooperative

Hi, On Wed, 09 Jul 2025 at 16:51, Maxim Cournoyer wrote: > It is a great pleasure to introduce you to Guixotic, our new worker > cooperative specializing in GNU Guix and Guile: > > https://guixotic.coop/ Cool! All the good vibes in the Guix motto [1] spirit: “error in finalization thread:

Re: Introducing Guixotic, a Guix/Guile worker cooperative

Hi Reza, reza writes: [...] > Can you share hourly rates for your services, e.g. for sys admin or > packaging work? We do not have rates to publish, as they vary depending on the nature of the project, its size, etc. You are welcome to reach us at cont...@guixotic.coop; we can continue the co

Re: Introducing Guixotic, a Guix/Guile worker cooperative

On 9/07/25 7:51, Maxim Cournoyer wrote: Hi, Guixers and Guilers! It is a great pleasure to introduce you to Guixotic, our new worker cooperative specializing in GNU Guix and Guile: https://guixotic.coop/ We are currently three people that you may already be familiar with: Maxim Cournoyer (apte

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

Am Sun, Jul 13, 2025 at 10:14:16PM + schrieb Attila Lendvai: > this is somewhat tangential, but guix is the first project in my entire > programmer career where it's not only allowed to commit changes that will > break things, but it's straight out demanded (the one commit per package > poli

Re: Introducing Guixotic, a Guix/Guile worker cooperative

Hi Edouard, Edouard Klein writes: > Congrats on the launch ! Thank you! > I'm very happy to read that more people are trying to use guix > commercially. > > I'm also very happy that you chose a cooperative as a setup, I think > many problems would be solved if every company in the world was a

Re: Informal Guix 1.4.0 branch and security fixes?

On 2025-07-11, Denis 'GNUtoo' Carikli wrote: > On Tue, 8 Jul 2025 21:01:58 +0200 > Denis 'GNUtoo' Carikli wrote: > >> Given the current status I gave a quick and dirty try at "backporting" >> the patches and so far I have something that compiles and I will try >> to test it soon[4] > > I had to in

Re: Introducing Guixotic, a Guix/Guile worker cooperative

Hi, Ludovic Courtès writes: [...] > Which makes me thing: should we have a “Commercial Support” section on > the web site, maybe linked from ? This > would need discussion but I’d personally be fine listing at least > cooperatives and single-person organizations

Re: GNU Shepherd 1.0.6 released

Hi, Adding to what I just said earlier: it should at least be possible to check if we're already root, and when we are, provide the completions for root. If we're an unprivileged user, then provide the completion for the Shepherd instance running as that user, if any. -- Thanks, Maxim

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

Attila Lendvai writes: My work on Guix is dominated by bulk upgrades of hundreds of R packages. There is no point in submitting the upgrades individually. In fact, my work on Guix has become so dominated by this is somewhat tangential, but guix is the first project in my entire programmer c

Re: Revisiting the "ChangeLog" style.

Hi Ludovic, Ludovic Courtès writes: > 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

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

> My work on Guix is dominated by bulk upgrades of hundreds of R > packages. There is no point in submitting the upgrades > individually. In fact, my work on Guix has become so dominated by this is somewhat tangential, but guix is the first project in my entire programmer career where it's not o

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

Hi Hilton, Hilton Chain writes: > I have sent out mails that are really unhelpful. No matter what effect they > can > achieve, it’ll be against my intention on discussing this topic, and I can’t > undo that. Probably I need to rest my mind before writing anything again. > > I’m open to critic

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

Liam Hupfer writes: > Hi Hilton, > > Hilton Chain writes: > >> I have sent out mails that are really unhelpful. No matter what effect they >> can >> achieve, it’ll be against my intention on discussing this topic, and I can’t >> undo that. Probably I need to rest my mind before writing anythi

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

I'll try to write a more constructive follow up on this topic some time later and explain every point, whether they are reasonable or not. I have sent out mails that are really unhelpful. No matter what effect they can achieve, it'll be against my intention on discussing this topic, and I can't u

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

Ricardo Wurmus writes: > Liam Hupfer writes: > >> Ricardo Wurmus writes: >> >>> My work on Guix is dominated by bulk upgrades of hundreds of R >>> packages. There is no point in submitting the upgrades >>> individually. In fact, my work on Guix has become so dominated by >>> R upgrades that I

Re: Revisiting the "ChangeLog" style.

Ludovic Courtès writes: > It seems doable, yes. (I’d personally miss the ability to search for an > identifier in the commit log, but the overall tradeoff on a social level > seems favorable to me.) I mentioned some additional log filtering options in [my reply to Tomas]. Not a drop-in replacem

Re: Informal Guix 1.4.0 branch and security fixes?

On Tue, 8 Jul 2025 21:01:58 +0200 Denis 'GNUtoo' Carikli wrote: > Given the current status I gave a quick and dirty try at "backporting" > the patches and so far I have something that compiles and I will try > to test it soon[4] I had to install slirp4netns and recompile Guix from scratch, but t

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

Liam Hupfer writes: Ricardo Wurmus writes: My work on Guix is dominated by bulk upgrades of hundreds of R packages. There is no point in submitting the upgrades individually. In fact, my work on Guix has become so dominated by R upgrades that I barely ever get to do much else. This mea

Re: Revisiting the "ChangeLog" style.

Ekaitz Zarraga writes: > On 2025-07-09 23:34, Tomas Volf wrote: >> >> The commit message’s purpose isn’t to enable people to avoid reading the >> diff; that’s an impossible goal. It’s to contextualize the diff. (aside: seems the quoting got wonky here) > Which, btw, most of the Guix commits DO

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

Ricardo Wurmus writes: > My work on Guix is dominated by bulk upgrades of hundreds of R > packages. There is no point in submitting the upgrades > individually. In fact, my work on Guix has become so dominated by > R upgrades that I barely ever get to do much else. This means I’m > unlikel

Re: Introducing Guixotic, a Guix/Guile worker cooperative

Hi Guixotic > Hi, Guixers and Guilers! > > It is a great pleasure to introduce you to Guixotic, our new worker > cooperative specializing in GNU Guix and Guile: Very cool initiative! > https://guixotic.coop/ > > We are currently three people that you may already be familiar with: > Maxim Cournoy

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've seen this > pattern before fo

Re: GNU Shepherd 1.0.6 released

Hi Tobias, Tobias Geerinckx-Rice writes: >> On 10 Jul 2025, at 19:14, Maxim Cournoyer wrote: >> Maybe i could run this once and cache the result? I think I've seen this >> pattern before for bash completion. > > With sudo? I'd find it surprising to the point of annoying if hitting > popped up

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

  1   2   3   4   5   6   7   8   9   10   >