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: 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: 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 per

Re: Package shared library Rawspeed for use via CMake

Nico Rikken via "Development of GNU Guix and the GNU System distribution." writes: > Hi all, > > I recently contributed the Ansel photo editor in gnu/packages/photo.scm > https://codeberg.org/guix/guix/pulls/85 > > Ansel is a fork of Darktable, and both use the rawspeed library: > https://github.

Re: Tagging issue?

Simon Tournier writes: > Hi, > > Since the migration from Savannah/Debbugs to Codeberg, I am not part of > “Collaborators“, neither “Member” and I do not have “commit access” > (although I’m in the authorized list). This way, I share the same > experience as a regular contributor. Anyway! :-) >

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

Hilton Chain writes: > Hi Guix, > > This email starts as a follow-up to #695 (doc: Document bulk updates.[1]), > since > it brought this topic to the surface. To be clear, I'm not against the > automation. I even want to mark out all packages that are not working with > ‘guix refresh’ :) > > >

Re: Revisiting the "ChangeLog" style.

Liam Hupfer writes: > Hi Guix, > > Maxim Cournoyer writes: > >> Maybe a GCD proposing modernizing what we put in our git commit >> messages could be devised; there are lots of good guidelines out >> there, such as those used by the Linux kernel and Git projects. > > I emphatically support this.

Re: Implementing the XDG Autostart Specification

Sergio Pastor Pérez writes: > Noé Lopez writes: >> Sergio Pastor Pérez writes: >>> What I do to solve this problems, is to create a shepherd service to >>> manage the desktop environment[1], Plasma in my case, and I augment the >>> plasma-workspace[2]

Re: Implementing the XDG Autostart Specification

Sergio Pastor Pérez writes: > Hello! My 2 cents. > > Hilton Chain writes: >> Services can depend on its symbol, graphical-session and explicitly >> x11-display >> or wayland-display. The service will fail to start when starting Shepherd in >> TTY environment and block dependent services. >> >>

Re: xlibre X11 server

Aviva writes: > On 7/2/25 11:20 AM, Noé Lopez wrote: >> “WW1 was clearly *NOT* started by >> Germany”[1]. > > > > WWI was CLEARLY *NOT* started by Germany.  It was started with the > assination of the Arch Duke Ferdenand?   > > >  28 June 1914, when Gavril

Re: xlibre X11 server

Samuel Christie via "Development of GNU Guix and the GNU System distribution." writes: > I'm not sure I understand the reactions to the Xlibre project. > > The quote from their website is: > >> This is an independent project, not at all affiliated with BigTech or >> any of their subsidiaries or

Re: Issues and pull requests labels on Codeberg.

Hilton Chain writes: > Hi Noé, > > Hilton Chain writes: > >> Ludovic Courtès writes: >> >>> 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 r

Re: Implementing the XDG Autostart Specification

Andrew Wong writes: > Hello Guix, > > How would Guix/Shepherd implement the XDG Autostart specification[1]? > > I looked into how systemd does it[2], and it appears that implementation > is done by having a service generate other services based on the > .desktop files in the correct directory.

Re: Package with multiple source repositories

Konrad Hinsen writes: > Hi everyone, > > A package I am working on has the unusual property of having its source > split into two repositories, for historical reasons. Building it > requires a checkout of both these repositories. Is this possible in a > Guix package? E.g. having two source reposi

Re: GCD005: Regular and efficient releases (consideration/decision)

Steve George writes: > Hi all, > > After a good long discussion I'm moving GCD005 to Deliberation. > > The final version is below and can be found on Codeberg: > > > https://codeberg.org/guix/guix-consensus-documents/src/branch/main/005-regular-releases.md > > This means that team members ha

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

Danny Milosavljevic writes: >> I think we should revert that commit until we can revisit. It has >> caused enough long-standing issues and the gain of having it appears small. > > I agree. > > Though if the store key of grafts is good enough so that we could just > fine-grain ALL grafts that wo

Re: Teams migration on Codeberg

Gabriel Wicki writes: > Hi Y'all > > It could well be that I missed the memo - otherwise I guess this is > either a WIP or a topic to be discussed and implemented, for which this > message could be a starting point. > > I am member of several teams (as per etc/teams.scm), but since our move > to

Re: Guix Booth at Capitole du Libre in Toulouse, France

Julien Lepiller writes: > Hi Guix! > > No answers so far. Is anyone interested? > > Le 28 mai 2025 09:15:09 GMT+02:00, Julien Lepiller a > écrit : >>Hi Guix! >> >>We're coming back from JdLL in Lyon where we had a very good time. >> >>I'm writing again to suggest we ask for a stand at Capitole

Re: Issues and pull requests labels on Codeberg.

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

Re: Issues and pull requests labels on Codeberg.

Hilton Chain writes: > Hi Guix, > > An initial set of labels were added in > https://codeberg.org/guix/guix/issues/33. > > Documentation for labels are available here: > https://forgejo.org/docs/latest/user/labels/ > > Once created, an id will be assigned > e.g. https://codeberg.org/guix/guix/iss

Re: Willing to contribute to guix as part of FSF40 Hackathon

Tobias Alexandra Platen writes: > I have been using the Guix System for a long time and I am willing to > improve the system. For example there is still much work needed to get > the complete Guix System running on a Talos II or the big endian > PowerPC notebook or its 2025 desktop version. I hav

Re: Team members: create and share your Codeberg account

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

Re: Committers: create and share your Codeberg account

Ludovic Courtès writes: > Hello Guix! > > If you’re a committer, please consider creating an account on Codeberg. > > To avoid problems, I suggest you send your account name as a public > reply to this message, in a signed message. > > You will be given rights on Codeberg according to the “Rights

Re: Codeberg migration check list

Ludovic Courtès writes: > 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.org/guix/g

Re: GCD005: Regular and efficient releases (submitted)

Steve George writes: > Hi all, > > Thanks for all the feedback on the initial proposal. > > I've integrated it into the GCD so attached is a revised version. I think > it's ready to move to the Discussion Period (minimum 30 days from today). > > A short summary of the changes in this version: >

Re: Guix booth at JDLL in Lyon, France?

Julien Lepiller writes: > Le Tue, 20 May 2025 17:05:01 +0200, > Noé Lopez a écrit : > >> Julien Lepiller writes: >> >> > Hi Guix! >> > >> > There is a regular event in Lyon, called JDLL (journées du logiciel >> > libre): <https://j

Re: Guix booth at JDLL in Lyon, France?

Julien Lepiller writes: > Hi Guix! > > There is a regular event in Lyon, called JDLL (journées du logiciel libre): > . It will happen end of may this year. > > We have until march 16 to submit a proposal for a talk or a booth. If we can > gather at least three more people (ot

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

Ludovic Courtès writes: > Hello, > > Now that GCD 002 has been accepted, I’d like to restart discussions > around this patch, which adds the git.guix.gnu.org DNS entry and HTTP(S) > redirects to codeberg.org/guix: > > https://issues.guix.gnu.org/76296 > >> This patch implements that; technicall

Re: Preparing for Git repository migration

Ludovic Courtès writes: > Hello Guix, > > Key dates defined in GCD 002 are: > > • By June 5th, all Git repos are migrated to Codeberg; > > • On a flag day between May 21st and June 5th, guix.git is migrated > (meaning that nobody pushes to Savannah after that date). > > How about Sunday M

Re: How to maintain a multi-version channel?

Hartmut Goebel writes: > Hi, > > I'm thinking about creating a channel for Tryton providing packages for all > major versions supported upstream. > For this I'm seeking advice on how to manage this easily (and automatically, > if possible). > > Background: > > Tryton upstream supports several

Re: [bug#78052] [PATCH] gnu: ungoogled-chromium: Fix WebRTC.

Andreas Enge writes: > Hello, > > Am Tue, Apr 29, 2025 at 10:45:44AM +0200 schrieb Noé Lopez: >> IMO its important that we have one of webkit, chromium and gecko in our >> repos for when those pesky websites refuse to work with X browser. > > I concur. In particular,

Re: [bug#78052] [PATCH] gnu: ungoogled-chromium: Fix WebRTC.

Maxim Cournoyer writes: > Hello, > > Danny Milosavljevic writes: > >> * gnu/packages/patches/ungoogled-chromium-fcntl-fix.patch: New file. >> * gnu/packages/chromium.scm (%guix-patches): Add reference to it. >> * gnu/local.mk (dist_patch_DATA): Add reference to it. > > Ouch, the last time ungoog

Re: Problem with hidapi and new prusa-slicer@2.9.2

"nomike (they/them)" writes: > On 24.04.25 03:46, nomike (they/them) wrote: >> I will keep you posted tomorrow, and if I don't find enough time >> during the day, I will hopefully be able to write you in the evening >> (I'm located in Europe/Vienna (UTC+01:00)). > > Hi! > > I just managed to ha

Re: Problem with hidapi and new prusa-slicer@2.9.2

"nomike (they/them)" writes: > On 24.04.25 00:24, Noé Lopez wrote: >> "nomike (they/them)" writes: >> >> Hi nomike! >> >> Thanks for your efforts, here are my thoughts but please note that I am >> not too experienced with Guix so feel fr

Re: Problem with hidapi and new prusa-slicer@2.9.2

"nomike (they/them)" writes: > Hi! > > prusa-slicer is currently at versionb 2.7.4 in guix which is > ridiculously outdated. > I'm currently working on upgrading it to the latest version 2.9.2 and > I've already made quite some progress, but it looks like I'm stuck right > before the finish li

Re: Patched version of broken offlineimap3

Gary Johnson writes: > Hi Guix, > > The offlineimap3 package is broken in the current version of Guix due > to a longstanding bug in offlineimap3 that makes it incompatible with > Python 3.11 (which is now the default python version in Guix). > > For reference, my current Guix version is: > > g

Re: [GCD] Deliberation on: Migrating repositories, issues, and patches to Codeberg

Ludovic Courtès writes: > Hello Guix, > > It’s been two months since we started discussing GCD 002, entitled > “Migrating repositories, issues, and patches to Codeberg”. Its final > version is attached below. > > In accordance with the GCD process, team members have until May 6th to > participat

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

Ludovic Courtès writes: > Hello Guix! > > We have just 9 days left to discuss and improve this GCD. > > Please do read the document in its current form: > > > https://git.savannah.gnu.org/cgit/guix/guix-consensus-documents.git/tree/002-codeberg.md > > If you brought up ideas or concerns, or if

Re: Applying Patches for Review

Gabriel Santos writes: > Greetings, > > I found an interesting patch, viz. 76910, and I want to > help it out with a review by trying the patch out. > > I tried looking into how this is done but couldn't find > anything in the manual. > > So, the question is: how can one apply a patch submitted >