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: 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: 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: 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: [bug#78332] GCD005: Regular and efficient releases (consideration/decision)

releases. ;-) Cheers, simon 1: [bug#78332] GCD005: Regular and efficient releases Simon Tournier Thu, 12 Jun 2025 21:08:54 +0200 id:87y0tw22wp@gmail.com https://lists.gnu.org/archive/html/guix-devel/2025-06 https://yhetil.org/guix/87y0tw22wp@gmail.com

Re: [bug#78332] approximated popcon? (was Re: GCD005: Regular and efficient releases)

Hi Maxim, On Wed, 18 Jun 2025 at 16:01, Maxim Cournoyer wrote: > I suppose it could be done by processing the nginx access logs. Do you think it would be possible to send them? Offlist if required. :-) Cheers, simon

config.scm-builder and content-address?

Hi, Updating: --8<---cut here---start->8--- $ guix pull -p /tmp/new Updating channel 'guix' from Git repository at 'https://git.savannah.gnu.org/git/guix.git'... Authenticating channel 'guix', commits 9edb3f6 to 3bd7d7e (74 new commits)... Building from this c

Re: Moving translations of Guix away from Fedora Weblate

Hi, On Mon, 16 Jun 2025 at 16:13, Julien Lepiller wrote: > I was AFK since last week :) I hope for good stuff. :-) > I'll need permission for myself (roptat) and the translate user. Then > I can setup the repository and switch from framagit completely. Feel free to ping, so then we can updat

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

Hi, On Thu, 15 May 2025 at 18:10, minung...@gmail.com wrote: > Currently guix-daemon is built using GCC 11 with -std=c++11. We are > waiting for guile-daemon [1], but we can have improvements on > guix-daemon right now. > > In nix/libutil/util.cc there are lots of functions related to > copy/dele

Re: Moving translations of Guix away from Fedora Weblate

Hi, CC: Julien :-) On Sat, 14 Jun 2025 at 08:26, "pelzflorian (Florian Pelz)" wrote: > Thanks! There is hold-up (not a problem), because I do not know and > wait for Julien to decide which Codeberg accounts need permission on the > new translations repository and did not include them in the p

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

Hi Ludo, On Thu, 15 May 2025 at 14:21, Ludovic Courtès wrote: > 3. I’m reluctant about using because the few functions > you mention are security-sensitive. We would need to look at the > implementation of libstdc++ and perhaps at the spec to see whether > their counterpart is

Re: How to maintain a multi-version channel?

Hi Hartmut, On Tue, 06 May 2025 at 22:33, Hartmut Goebel wrote: > A common use-case for developers is to have several > profiles/virtual-environments with different version. Somehow, it depends on how the different Tryton ecosystem is between the versions and how the users would use it. •

Re: [PATCH] Add bolt

Hi, On Tue, 06 May 2025 at 18:01, Sergio Pastor Pérez wrote: > It's been two years since this patch series was updated. Is there any > reason why it didn't get merged? [...] > How can we help to push this patch series through the finish line? Maybe close this ticket and reopen a clean PR on

Re: Why are the git submodules not being cloned?

I could be doing wrong? I appears to me the same issue as elsewhere and replied here: bug#78649: (recursive? #t) doesn't seem to be part of the source hash Simon Tournier Fri, 13 Jun 2025 17:46:56 +0200 id:87sek3myof@gmail.com https://issues.guix.gnu

Reducing “guix pull” error reports, toward a plan?

100 72135 upgrade from v1.2.0 72332 v1.4.0 72353 v1.4.0 72563 v1.4.0 72639 v1.4.0 …to be continued… Please note v1.4.0 means the host revision was v1.4.0. Cheers, simon 1: toward a plan? (was Re: Reducing "You found a bug" reports) Si

Re: June update on qa.guix.gnu.org and related things

Hi Chris, On Fri, 13 Jun 2025 at 19:15, Christopher Baines wrote: > There's a diagram here which has some information on how things relate > to each other: > > https://qa.guix.gnu.org/README#orgdc0ae66 Oh, I’ve missed this. Very helpful! Thanks. And thanks for all the explanations. I will

Re: GCD005: Regular and efficient releases

Typo: **not** fulfilled. :-) On Friday, 13 June 2025, Simon Tournier wrote: > Hi Andreas, > > On Fri, 13 Jun 2025 at 21:02, Andreas Enge wrote: > > Am Thu, Jun 12, 2025 at 09:08:54PM +0200 schrieb Simon Tournier: > > >> Instead, I think we need two intermediary st

Re: Setting procedure properties for build-system builders

Hi Nicolas, Ludo, On Tue, 13 May 2025 at 11:38, Nicolas Graves wrote: > I can resubmit a clean 68315 with this change too if this helps. > > In the previous mail response, I made the point that 68315 is probably a > requirement for the following patch to be actually useful. >> attached is the r

Re: [PATCH] build-system: Adding conan-build-system.

Hi Nicolas, This appears to me to have fallen into the cracks. On Wed, 16 Apr 2025 at 16:56, Nicolas Graves wrote: > --- > Makefile.am | 2 + > guix/build-system/conan.scm | 128 + > guix/build/conan-build-system.scm | 232 ++

Re: [PATCH] import: Add conan import.

Hi Nicolas, On Wed, 16 Apr 2025 at 16:57, Nicolas Graves wrote: > Here's also my conan import implementation, if you want to take a look. > > Nicolas > --- > Makefile.am | 2 + > guix/import/conan.scm | 186 ++ > guix/scripts/import.scm

Re: Problem: Installing an Info manual into `share/info/`, but not `share/info/dir`.

Hi, On Sat, 19 Apr 2025 at 07:18, Yuval Langer wrote: > What is happening? I think it’s because the original file srfi-234.org does not have the header #+TEXINFO_DIR_TITLE. > #:install-plan #~'(("srfi-234.info" "share/info/")) > #:phases #~(modify-phases %standard-phases >

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

Hi Andreas, On Fri, 13 Jun 2025 at 21:02, Andreas Enge wrote: > Am Thu, Jun 12, 2025 at 09:08:54PM +0200 schrieb Simon Tournier: >> Instead, I think we need two intermediary steps: >> (1) Clarify what means being a member of a team. >> (2) Clarify the branching model; e

Re: CI is broken

Hi, On Mon, 09 Jun 2025 at 11:14, Ludovic Courtès wrote: > 2025-06-09 06:30:44 guix gc: error: executing SQLite statement: FOREIGN KEY > constraint failed Oh, weird! SQLite and guile-sqlite have not changed since years, right? Well, my SQL skill is very limited. So I’ve just read this web

Moving translations of Guix away from Fedora Weblate

Hi Florian, > * Somebody (Julien?) would open the Weblate at Codeberg. If I understand correctly, the proposal is to move from the Weblate Fedora instance [1] to the Weblate Codeberg instance [2], right? FWIW, it appears to me a good idea! And the plan LGTM. :-) Well, I do not know if it deser

Re: June update on qa.guix.gnu.org and related things

Hi Chris, On Thu, 12 Jun 2025 at 17:06, Christopher Baines wrote: > I've started trying to use Codeberg's issue and project tracking > functionality for the qa-frontpage [3][4], and the related bordeaux > build farm [5]. Cool! Thank you for all this effort over the years. > I would like to se

approximated popcon? (was Re: GCD005: Regular and efficient releases)

Hi, > As we don't have popcon I don't know what's popular with users Once I heard a Debian Developer says: the aim of popcon isn’t to take less care of unpopular packages but the contrary. It allows to know that this package in appearance useless and/or outdated is still used by one user so it’s

Re: GCD005: Regular and efficient releases

Hi Steve, Thanks for this proposal! Well, I’ve not commented yet because I’m very doubtful that releasing more often can be solved with a GCD. I mean, yeah we all would like more releases, and then? :-) Look, on February, we were all in the same room and we all agreed that we had to work on re

Tagging issue?

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! :-) I notice that I cannot apply any lab

Re: Delibaration vs. voting (was: [GCD] Migrating repositories, issues, and patches to Codeberg)

Hi, On Mon, 12 May 2025 at 09:43, Vagrant Cascadian wrote: > To my take on english "deliberation" is usually focused more on the > process of making a decision, though possibly to make it clear and > explicit, we could use "deliberation results" or "results of the > deliberation" ? In French, t

Re: Deliberation period for GCD 003 "Rename the default branch" has technically started

the near future keeping in mind that confrontational discussion is helpless and consensus requires self-discipline [1]. Cheers, simon 1: [bug#76407] About consensus, again (was Re: [bug#76407] [GCD] Rename the default branch) Simon Tournier Wed, 26 Mar 2025 21:20:36 +0100 id:871pujtugb

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

Hi, I accept. Cheers, simon

About GCD process, consensus and derailment (was Re: Deliberation period for GCD 003 "Rename the default branch" has technically started)

name these refinements some “flaws”. :-) IMHO, we need to bound the scope “how to build consensus” and we need to reinforce the positions of « Sponsor » who are the guards against the derailment. WDYT? Although we should discuss that elsewhere. :-) Cheers, simon 1: [bug#76407] About consensus, again

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

Re, On Fri, 18 Apr 2025 at 14:09, Ludovic Courtès wrote: > I adapted a slightly modified variant of this (using ‘jq’ for parsing) > with slightly modified text. LGTM. Thanks. Re-reading all, the sections « User Interfaces » and « Continuous Integration » capture well all the potential of the

Re: [bug#76503] Magit-Forge & Forgejo

Hi, On Thu, 17 Apr 2025 at 15:37, Ludovic Courtès wrote: >> In light of guix potentially moving to codeberg, i've began adding >> forgejo support to magit/forge, see >> https://github.com/magit/ghub/pull/171 and >> https://github.com/magit/forge/pull/770 Why not add these references:

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

Hi, On Fri, 18 Apr 2025 at 08:30, pinoaffe wrote: > I'll probably set it up somewhere, either just as a repo of my own or at > https://github.com/mobid/gitea-forge Cool! Thank you for this work, very helpful! Once this somewhere is defined, IMHO, the best seems to drop it as a comment in

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

Hi Ludo, Ah, I forgot: I would remove the mention to your usual login civodul and instead use classical aubrey or blake or carol or dana or … :-) On Thu, 17 Apr 2025 at 21:48, Ludovic Courtès wrote: >> Last, it appears to me a good idea to also provide the tip for removing >> closed pull reques

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

ot have a setup that fulfills them. Last but not least, I support the outcome of this GCD. I know it’s not yet the Deliberation Period and this will not be taken into account. But I will be offline for some weeks and it appears to me worth to express my plain support. Cheers, simon 1: [bug

Re: [bug#76503] Mirroring the mirror?

Hi, On Sun, 30 Mar 2025 at 21:10, Ludovic Courtès wrote: > I checked with people at Sourceware: they’re unable to to provide any > guarantees around mirroring Guix at the moment, their Forgejo setup > being experimental and with limited capacity (but they do hope to set up > mirrors and federati

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

Hi, On Wed, 16 Apr 2025 at 19:53, pinoaffe wrote: > https://github.com/magit/ghub/pull/171 and > https://github.com/magit/forge/pull/770 Bah news from upstream: https://github.com/magit/forge/pull/770#issuecomment-2812213785 Feel free to share the separate repository, if you do. Cheers,

Re: Slow guix pull? (was Re: Please don't leave GNU)

Hi, On Fri, 11 Apr 2025 at 17:54, Ludovic Courtès wrote: > I noticed something funny (?) with libgit2 when cloning from a local repo: > one of file:///path/to/repo and /path/to/repo is much faster than the > other (I forgot which one). Try it! Well, /path/to/repo is MUCH faster. It’s not the

Re: Emacs dependent package input question

Hi Ian, On Sat, 05 Apr 2025 at 09:38, Ian Eure wrote: > a) Leave it as is. Don’t love it, but if there’s concensus that > this is the right way, then okay. Somehow, the consensus has been to have “maximally” featured packages – roughly speaking – and use -minimal when not. For instance, Al

Re: Setting procedure properties for build-system builders

Hi Nicolas, CC: core-team On Mon, 17 Mar 2025 at 10:53, ngra...@gmx.com wrote: > I would like to make that metadata available at the build-system > level. This would require setting procedure properties on builder > functions, in every build-system, like so: > > (set-procedure-properties! > gnu

Re: [fr] Moment de convivialité Guix@Paris en mars

salut Nicolas, On Thu, 10 Apr 2025 at 10:58, Nicolas Graves wrote: > Dans les prochaines semaines, je vais probablement essayer d'en faire un > article sur le blog Guix, et peut-être même finir par rédiger la doc > pour le manuel. En voilà une bonne idée! 😀 à tantôt, simon

Slow guix pull? (was Re: Please don't leave GNU)

2]. But they require to revamp how it currently works. Good, let’s experiment with that! :-) Cheers, simon 1: bug#65787: time-machine is doing too much network requests Simon Tournier Wed, 06 Sep 2023 18:26:18 +0200 id:87wmx3mfo5@gmail.com https://issues.guix.gnu.org/65787 https://issue

Re: Slow guix pull? (was Re: Please don't leave GNU)

:fetch-options (make-default-fetch-options #:verify-certificate? verify-certificate?))) Therefore, that’s why my guess is about openable-repository? Cheers, simon 1: comparing commit-relation using Scheme+libgit2

Re: Slow guix pull? (was Re: Please don't leave GNU)

Re, On Wed, 02 Apr 2025 at 09:41, 45mg <45mg.wri...@gmail.com> wrote: >> every single time I run `guix >> pull` it appears to do nothing for like 2 minutes, and then the progress >> bars display as it pulls the entire repo instead of using a cached >> chec

Visiting a future of GNU? (was Re: Please don't leave GNU)

Hi Caleb, On Fri, 28 Mar 2025 at 18:26, Caleb Herbert wrote: > I use Guix primarily because of its commitment to user freedom and its > united front with the GNU Project. Cool! As many of us. :-) If I might, I think your message and replies in the thread lock the conversion in some undecidab

Re: “Build daemon drops its privileges” 👈 blog post

Hi, On Mon, 31 Mar 2025 at 14:14, Ludovic Courtès wrote: > New blog post about this newfangled unprivileged guix-daemon: Ouf, it's on 31 march and not the 1rst April. :-D Nice feature! Thanks Ludo, thanks Reepca for the detailed review. Cheers, simon

Re: Scaling issues with forges Was: Trying out Codeberg

Hi, On Tue, 11 Mar 2025 at 13:12, Suhail Singh wrote: > Are the relevent portions of your .emacs or init.el accessible > somewhere? https://gitlab.com/zimoun/my-conf Cheers, simon

Re: Trying out Codeberg

Hi, On Thu, 13 Mar 2025 at 10:36, Adrien 'neox' Bourmault wrote: > the default CI recipes/code depends on > docker.io images Well, Cuirass (one CI tool used by the Guix project) is able to work with Forgejo. > nodeJS and npm. Also, the javascript

Mirroring the mirror? (was Re: [bug#76503] [GCD] Migrating repositories, issues, and patches to Codeberg)

Hi Ludo, I’m just discovering the Forgejo instance of sourceware: https://forge.sourceware.org/explore/organizations Here, mirror of GCC, Glibc and others are already hosted. Therefore, it would make sense to check their willing and capacity to backup Guix; I have in mind to ask for hosting

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

Hi, On Fri, 21 Mar 2025 at 17:04, Ludovic Courtès wrote: > Improving this is among the things that have been on our mind for a > while; it looks better now: > > https://guix.bordeaux.inria.fr/pull-requests > > We’re making progress, at our own pace. :-) Cool! It’s much better. :-) Cheers,

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

Hi Ludo, I have not read yet the updated version… > An incremental move from guix-patches to PRs as you suggest sounds > perfectly reasonable to me > I’ll propose > changes along these lines. …so I will comment elsewhere about how “increm

Next period? (was Re: [GCD] Set search paths without program wrappers)

Hi, On Tue, 18 Feb 2025 at 18:09, Simon Tournier wrote: > This GCD can be now considered as *submitted*. The date for the > submission date will be the one when you will send the announce; see > “Communication Channels” section. Almost one month is over. For the record, the d

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

Hi, On Sun, 23 Feb 2025 at 16:20, Ludovic Courtès wrote: > ## Continuous Integration [...] > In the Guix repository, we will set up webhooks to trigger the creation > of a new jobset at ci.guix.gnu.org (Cuirass) as soon as migration is > complete. While this has been successfully used for sev

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

simon 1: [bug#76503] [GCD] Migrating repositories, issues, and patches to Codeberg Simon Tournier Mon, 10 Mar 2025 13:30:44 +0100 id:87frjl6paj@gmail.com https://issues.guix.gnu.org/76503 https://issues.guix.gnu.org/msgid/87frjl6paj@gmail.com https://yhetil.org/guix/87frjl6paj@gmail.com

Git branch rename? (was Re: [GCD] Migrating repositories, issues, and patches to Codeberg)

Hi, On Wed, 12 Feb 2025 at 15:08, Leo Famulari wrote: > On Wed, Feb 12, 2025 at 05:13:25PM +0100, Liliana Marie Prikler wrote: >> That's why I commented on the Codeberg GCD — so that it can be included >> in a v2 of said GCD. I do expect there will be some revisions before >> the decision is fin

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

Hi Ludo, On Sat, 15 Mar 2025 at 22:22, Ludovic Courtès wrote: > Vagrant Cascadian skribis: > >> From my personal experiences with Debian, it looks to me possible to do >> both systems for a long time, but the extent of the downsides are >> unclear to me. That’s my proposal: having more mileston

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

ge.org/swh:1:cnt:ce7a09543926f7e5717b7a3f8fa3c1f6d5fdb5f1 2: [bug#76503] [GCD] Migrating repositories, issues, and patches to Codeberg Simon Tournier Mon, 10 Mar 2025 13:30:44 +0100 id:87frjl6paj@gmail.com https://issues.guix.gnu.org/76503 https://issues.guix.gnu.org/msgid/87frjl6paj@gma

Re: Numerical problem (compiling python-numba package)

Hi Emmanuel, On Wed, 12 Feb 2025 at 09:42, Emmanuel Medernach wrote: > AssertionError: when comparing [0.60858395 0.54922627 0.57440088] and > [0.60858395 0.54922627 0.57440088]: 0.549226270051226 != 0.5492262700512262 > > More generally this asks the question about reproducibility of numerica

Re: guix build -P not building dependent(s) of django package

Hi jgart, On Thu, 20 Feb 2025 at 17:33, "jgart" wrote: > Also, why not call this flag -l instead of -P like `guix refresh -l foo`? As you read in the three messages starting here [1], this had been discussed. And the rationale is because one accepts an optional argument and the other not. The

Re: Moving ruby@2 packages to guix-past?

Hi Nicolas, On Sun, 19 Jan 2025 at 22:51, Nicolas Graves wrote: > One of them is about the EOL ruby packages. The following packages from > Guix have reached their EOL : ruby@2.6, ruby@2.7, ruby@3.0 > > Since they are packaged but shouldn't be recommended, my solution would > be to move them fro

Re: Scaling issues with forges Was: Trying out Codeberg

r cannot live with for my day-to-day collaboration with Guix. Cheers, simon 1: Re: [GCD] Migrating repositories, issues, and patches to Codeberg Simon Tournier Thu, 30 Jan 2025 14:13:30 +0100 id:87wmec4f7p@gmail.com https://lists.gnu.org/archive/html/guix-devel/2025-01 https://yhetil.org/guix/

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

html/guix-devel/2025-03 https://yhetil.org/guix/8734ftdoq4@gmail.com 4: Re: bug#76503: [GCD] Migrating repositories, issues, and patches to Codeberg Simon Tournier Thu, 06 Mar 2025 18:39:56 +0100 id:87r03a5a8j@gmail.com https://lists.gnu.org/archive/html/guix-devel/2025-03 https://yhe

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

Hi Andreas, On Fri, 07 Mar 2025 at 17:03, Andreas Enge wrote: > Which says nothing about the experience on a forge, logically. If I might, I encourage you to subscribe to all the guix-science channels. This way, you will have an foretaste: The Good, the Bad and the Ugly. :-) Cheers, simon

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

order to be a bit more incremental [1]. And 2. To help in implementing a simple one-way bridge [2]: report the open PR inside Debbugs. Cheers, simon 1: [bug#76503] [GCD] Migrating repositories, issues, and patches to Codeberg Simon Tournier Thu, 06 Mar 2025 17:36:29 +0100 id:874j066rqq@gmai

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

fer avoiding to scatter our attention on another (minor) topic when we already have at least one very deep GCD (about our “workflow”). Therefore, let open this GCD about Amending the 3 open GCDs are in a advanced state. WDYT? Cheers, simon 1: Re: GCDs on info-guix? Simon Tournier Sun, 23 Feb

Re: Guix booth at JDLL in Lyon, France?

Hi Julien, On Tue, 04 Mar 2025 at 11:38, Julien Lepiller wrote: > Thoughts? Volunteers? As said off-list, I’ve put the event in my agenda so if we apply for a booth then I’ll my best to be there in Lyon. Let me know how it’s going for booking the train tickets. :-) Cheers, simon

Re: Blog posts for the most important GCDs (like the GCD 002)?

Hi, On Wed, 26 Feb 2025 at 17:57, Denis 'GNUtoo' Carikli wrote: > In my case I didn't read the mailing list that often (I often do that > in batches), and so I found out quite recently about all that. That’s why the submitted GCD are also announced on info-guix low-traffic mailing list. At le

Posting GCD #002? (was Re: Trying out Codeberg)

Hi Ludo, On Sun, 16 Feb 2025 at 17:41, Ludovic Courtès wrote: > I’ll be formally posting GCD #002 soon (“Migrating repositories, issues, > and patches to Codeberg”) As discussed elsewhere [1], we need a GCD process in order to amend Accepted GCDs without running a complete dance. My question i

Re: GCDs on info-guix?

process (v7) (was: Request-For-Comment, RFC) Arun Isaac Sun, 12 Jan 2025 15:11:50 + id:87tta4nk21@systemreboot.net https://lists.gnu.org/archive/html/guix-devel/2025-01 https://yhetil.org/guix/87tta4nk21@systemreboot.net 3: Re: GCDs on info-guix? Simon Tournier Fri, 21 Feb 2025

Re: example of poor debugging message (follow up Guix Days)

Hi Oleg, On Fri, 21 Feb 2025 at 13:37, Sharlatan Hellseher wrote: > --8<---cut here---start->8--- >> ./pre-inst-env guix build casacore indi libsep libxisf python-asdf \ > python-asdf-astropy python-astrocut python-astropy \ > python-astropy-healpix python-ast

Re: example of poor debugging message (follow up Guix Days)

Hi, On Sat, 15 Feb 2025 at 13:10, 45mg <45mg.wri...@gmail.com> wrote: > Here's a more minimal example from the guile-user mailing list 5 years > ago, that doesn't touch any Guix code at all: > https://lists.gnu.org/archive/html/guile-user/2020-03/msg00030.html Thanks, interesting. The manual re

Re: example of poor debugging message (follow up Guix Days)

Hi Chris, On Fri, 14 Feb 2025 at 11:54, Christopher Baines wrote: >> --8<---cut here---start->8--- >> $ guix build -L foo git2cl-bang >> Backtrace: >> In guix/gexp.scm: >>1218:2 19 (_ #) >>1085:2 18 (_ _) >> 926:4 17 (_ _) >> In guix/store.scm: >>

Re: bug#75552: Non-committers can't keep authenticated forks updated

Hi, On Mon, 03 Feb 2025 at 17:41, Nicolas Graves wrote: > What difference do you make between both? This is indeed an extension ;) Ah cool! I’ve overlooked. :-) Cheers, simon

How to move forward about Rust? antioxidant, cargo2guix, etc.

Hi, Reading this thread: https://social.sciences.re/@alxsim@ecoevo.social/114032640094854151 Let resume this discussion here. :-) Well, I know antioxidant and also that Nicolas did some piece of works but lost it! )-: (see #64904) And Murilo sent ideas [1] some time ago. And cargo2guix [2] doe

Re: GCDs on info-guix?

Hi Tobias, On Fri, 21 Feb 2025 at 12:54, Tobias Geerinckx-Rice wrote: > Could you ask them for a full > copy (with headers) of one of these replies delivered through > info-guix@? I think it’s about this message: https://lists.gnu.org/archive/html/info

Re: GCDs on info-guix?

onths/years). My conclusion: We start with info-guix for the 6 months and if the traffic is too high (define high? ;-)) then we create a dedicated mailing list. WDYT? Cheers, simon 1: Re: [GCD] Set search paths without program wrappers Simon Tournier Thu, 20 Feb 2025 19:28:13 +0100 id:caj3okz

Re: Trying out Codeberg

Hi Efraim, On Fri, 21 Feb 2025 at 09:01, Efraim Flashner wrote: >What parts of codeberg do you find slow? Is it loading the > website or navigating between different pages or a different workflow? Somehow loading the website and then navigate between different pages. But that’s not

Re: [GCD] Set search paths without program wrappers

Hi Tobias, On Thu, 20 Feb 2025 at 19:08, Tobias Geerinckx-Rice wrote: > The only drawback is that these posts don't look like the other info-guix@ traffic—release announcements and other rare & highly targeted broadcasts. I agree. Somehow, I expect that the traffic of GCD will be low. I mean,

Re: Re: [GCD] Rename “main” branch

Hi, On Tue, 18 Feb 2025 at 22:15, Sharlatan Hellseher wrote: > This thread reminds me RFC1925 https://www.rfc-editor.org/rfc/rfc1925 > "The Twelve Networking Truths" <1996-04-01>. That’s a good read! Thanks for sharing. Cheers, simon

Re: Trying out Codeberg

Hi, On Tue, 18 Feb 2025 at 13:39, Rostislav Svoboda wrote: > People, I find codeberg to be slow :-/ It’s “slow“ on my side too but not slower than gitlab.com or gitlab.inria.fr or etc. :-) My main annoyance isn’t “slow” but I cannot locally cache. It’s impracticable when you have a poor netw

Re: [GCD] Set search paths without program wrappers

Hi Tobias, 宋文武, all, (Since I do not parse 宋文武 – only copy/paste – so I hope it makes sense to say “Hi 宋文武” :-)) On Thu, 20 Feb 2025 at 07:56, Tobias Geerinckx-Rice wrote: >> Should I send an announce email to info-g...@gnu.org? > > I'm not sure, but go ahead. That’s one step [1] of the GCD (s

Re: Trying out Codeberg

Hi Olivier, On Sun, 16 Feb 2025 at 13:51, Olivier Dion wrote: > I have not follow the entire thread about this migration. > > Will the mail-patch workflow still available? The mail-patch workflow is still available. It will be available until a GCD changing is accepted. And such GCD will expl

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

Hi Ludo, On Tue, 28 Jan 2025 at 15:33, Ludovic Courtès wrote: > title: Migrating repositories, issues, and patches to Codeberg > id: 002 > status: draft > discussion: https://issues.guix.gnu.org/ > authors: Ludovic Courtès > sponsors: Tobias Geerinckx-Rice, Ricardo Wurmus > date-submitted: > d

Re: Trying out Codeberg

Hi Ludo, On Sun, 16 Feb 2025 at 17:41, Ludovic Courtès wrote: >perhaps even before GCD #001 is committed > (not sure what’s going on here :-)) Probably because I’m lagging… Well, now it’s ready from my side. :-) Feel free to tweak, if it’s not clear enough. Cheer

Re: [GCD] Rename “main” branch

Hi Liliana, On Sat, 15 Feb 2025 at 09:42, Liliana Marie Prikler wrote: > title: Rename "main" branch > id: 003 > status: draft > discussion: https://issues.guix.gnu.org/ > authors: Liliana Marie Prikler > sponsors: > date: > SPDX-License-Identifier: CC-BY-SA-4.0 OR GFDL-1.3-no-invariants-only

Guix Consensus Document: Git repo and workflow

Hi all, Please consider the Git repository hosting the GCDs: https://git.savannah.gnu.org/cgit/guix/guix-consensus-documents.git/ And the README file proposes a workflow. It’s up to changes. :-) Feel free to drop new GCDs. However, please consider that it takes time to read and forge an o

Re: [GCD] Set search paths without program wrappers

Hi 宋文武, On Sun, 02 Feb 2025 at 12:57, 宋文武 via "Development of GNU Guix and the GNU System distribution." wrote: > title: Set search paths without program wrappers > id: 003 > status: draft > discussion: https://issues.guix.gnu.org/ > authors: 宋文武 > sponsors: Maxim Cournoyer > date-submitted:

Re: [GCD] Rename “main” branch

Hi Liliana, all, On Sat, 15 Feb 2025 at 09:42, Liliana Marie Prikler wrote: > title: Rename "main" branch Just to notice that I’m lagging behind and the GCD Git repository is not yet ready. However, it already supports ’main’ as the default branch. ;-) https://git.savannah.gnu.org/cgit/guix/

example of poor debugging message (follow up Guix Days)

Hi, Some of us are not always happy with the Guix/Guile error reporting. As discussed at the Guix Days, maybe the best strategy to improve the situation is to report small examples that we can work on. Therefore, here one that I have just hit today when working on Julia. Here a minimalist examp

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

Hi, On Sat, 08 Feb 2025 at 17:57, Ludovic Courtès wrote: >> Now you mention it, shouldn't we have some people there to vote if we >> are doing some heavy use of their infrastructure? > > The GCD draft I sent mentions creating ties with Codeberg e.V., possibly > through financial support, definit

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

Hi Leo, On Thu, 06 Feb 2025 at 14:39, Leo Famulari wrote: > On Thu, Feb 06, 2025 at 04:40:03PM +0100, Simon Tournier wrote: >> Sorry if my understanding is incorrect, but if we do not increase the >> number of people with specific/dedicated/controlled write access, the >>

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

cdd9c 37730 --8<---cut here---end--->8--- 2: Re: hard dependency on Git? (was bug#65866: [PATCH 0/8] Add built-in builder for Git checkouts) Simon Tournier Mon, 11 Sep 2023 19:52:34 +0200 id:871qf4ha1p@gmail.com https://lists.gnu.org/archive/html/guix-dev

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

Hi Ludo, On Sat, 08 Feb 2025 at 17:43, Ludovic Courtès wrote: >> Sorry if my understanding is incorrect, but if we do not increase the >> number of people with specific/dedicated/controlled write access, the >> move to Codeberg is useless. Provocative on purpose. ;-) > > As I mentioned in the G

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

Hi, On Sun, 09 Feb 2025 at 12:43, Tomas Volf <~@wolfsden.cz> wrote: >> Maybe this is semantic nitpicking, but people who are able to merge are >> effectively committers, if only potentially limited to some parts of >> the code. > > Given that Guix is (effectively) just a large Scheme program, doe

Re: HTTP redirect for the Git repository

Hi, On Sat, 08 Feb 2025 at 18:13, Ludovic Courtès wrote: > To be more concrete, do you have something like this in mind: > > git.guix.gnu.org/guix.git > git.guix.gnu.org/maintenance.git > git.guix.gnu.org/build-coordinator.git > … > > ? I’m not Tobias but I had that in mind when reading

Re: Discussion with Codeberg volunteers

Hi, On Fri, 07 Feb 2025 at 16:22, Ludovic Courtès wrote: > • Scalability (storage): If the Guix repository were to have “tens of > thousands” of forks (I think these were their words), then the > storage requirements for Codeberg could be very high and > problematic, due to lack (o

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

Hi, On Tue, 04 Feb 2025 at 11:11, Ludovic Courtès wrote: >> So, we are not growing our base of committers in proportion to >> contributors, and I think we've lost contributors as a result. > > I believe we want to keep the number of committers relatively small, for > security reasons. Sorry if

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

Hi, On Sat, 01 Feb 2025 at 13:28, Leo Famulari wrote: > On Sat, Feb 01, 2025 at 10:44:40AM +0100, Lars-Dominik Braun wrote: >> > ## Repository Migration Path >> >> do we want to take this opportunity to start off fresh without migrating >> the main repository’s history? It looks like we have acc

  1   2   3   4   5   6   >