Re: G-Golf in Guix - G-Golf pkg(s) name(s)

Hi Ian, On Sun, Feb 16 2025, Ian Eure wrote: > Your purported authorization is irrelevant, as the name is within the > Guix project, not g-golf; and even if Guix had renamed the project, > such changes are explicitly permitted by g-golf’d LGPLv3 license. > > Since you seem to be more devoted to m

Re: none

Z572 writes: > My main concern is whether it will affect guix time-machine. > Will the master branch be removed after the migration to the main > branch on some time, or will it just stay there? Even if the 'master' branch is removed, which to avoid confusion I think should be done, we still hav

Re: none

Hi Z572, Z572 writes: Liliana Marie Prikler writes: ## Repository Update Path For a complete list of repositories associated with the Guix project, see GCD 002 ‘Migrating repositories, issues, and patches to Codeberg’. Most repositories can rename their main branch with no issue (see a

Re: G-Golf in Guix - 1 G-Golf (only) pkg, 1 pkg per lib examples per major version number

I have sent v2 https://issues.guix.gnu.org/76246#5 https://bugs.gnu.org/76246#20 of these patches gnu: guile-cairo: Remove expat from inputs. gnu: Add guile-cairo-next. gnu: guile-g-golf: Document --no-grafts requirement. gnu: Add G-Golf's GTK-4 examples. gnu: Add G-Golf's Adw-1 exampl

Re: none

Liliana Marie Prikler writes: > ## Repository Update Path > > For a complete list of repositories associated with the Guix project, see > GCD 002 ‘Migrating repositories, issues, and patches to Codeberg’. Most > repositories can rename their main branch with no issue (see also Cost of > Revertin

Re: G-Golf in Guix - G-Golf pkg(s) name(s)

On Sun, Feb 16, 2025 at 1:49 PM David Pirotte wrote: > > Hello Ian, > > > I'll submit a patch: please allow me to send the patch to this list, > > I not a guix-patches list member. > > Attached. Please review and apply asap. > > Thanks, > David Hi, As a guix user (I'm not a core dev nor have com

Re: G-Golf in Guix - G-Golf pkg(s) name(s)

Hello all, David Pirotte ezt írta (időpont: 2025. febr. 16., V, 20:49): > > Hello Ian, > > > I'll submit a patch: please allow me to send the patch to this list, > > I not a guix-patches list member. > > Attached. Please review and apply asap. I am sorry that we got to this point. I am sorry on

Re: G-Golf in Guix - G-Golf pkg(s) name(s)

Hi David, David Pirotte writes: Hi Inan, Ultimately, this kind of decision is a judgement call on the part of the committers reviewing the patches. In this case, the concensus is clear that the Guix convention should be upheld. Sorry to hear that [1], but I do not authorize guix to pic

Re: G-Golf in Guix - G-Golf pkg(s) name(s)

Hello Ian, > I'll submit a patch: please allow me to send the patch to this list, > I not a guix-patches list member. Attached. Please review and apply asap. Thanks, David From cd3e10080b68f11e1027f5bc9b1b11226393139b Mon Sep 17 00:00:00 2001 From: David Pirotte Date: Sun, 16 Feb 2025 16:45:08

Re: G-Golf in Guix - G-Golf pkg(s) name(s)

Hi Inan, > Ultimately, this kind of decision is a judgement call on the part > of the committers reviewing the patches. In this case, the > concensus is clear that the Guix convention should be upheld. Sorry to hear that [1], but I do not authorize guix to pick a different name, for its g-gol

Re: Trying out Codeberg

I have not follow the entire thread about this migration. Will the mail-patch workflow still available? On Sun, 16 Feb 2025, Ludovic Courtès wrote: > Hello Guix, > > I’ll be formally posting GCD #002 soon (“Migrating repositories, issues, > and patches to Codeberg”), perhaps even before GCD #0

Re: Cuirass: Use (%current-system) in %default-jobset-options-systems

Hi Ludo, Ludovic Courtès writes: > Hi Roman, > > r0man skribis: > >> From 1522da763a3dde5cbf6657e873fee2d71b6abf15 Mon Sep 17 00:00:00 2001 >> Message-ID: >> <1522da763a3dde5cbf6657e873fee2d71b6abf15.1739309136.git.ro...@burningswell.com> >> From: Roman Scherer >> Date: Tue, 11 Feb 2025 22:2

Re: Trying out Codeberg

Hello Ludo' > 1. try and look at pull requests, but only for trivial packaging > changes (I will close pull requests that don’t fit the bill); Please pull this one: https://codeberg.org/civodul/guix/pulls/3 That's an ideal candidate. It's just a silly Emacs package that "displays a buffer

Trying out Codeberg

Hello Guix, I’ll be formally posting GCD #002 soon (“Migrating repositories, issues, and patches to Codeberg”), perhaps even before GCD #001 is committed (not sure what’s going on here :-)), but before I do, and as a followup to our discussions at the Guix Days, here’s an offer for those who want

Re: Large rebuilds, nss, and QA

Hi Chris, Christopher Baines skribis: > I think more fundamentally there's a lack of interest/buy-in, at least > to support a system as ambitious as QA currently is. I'm obviously > biased but when QA has been able to provide information on patches in > the past, I've found that really useful. I

Re: Cuirass: Use (%current-system) in %default-jobset-options-systems

Hi Roman, r0man skribis: > From 1522da763a3dde5cbf6657e873fee2d71b6abf15 Mon Sep 17 00:00:00 2001 > Message-ID: > <1522da763a3dde5cbf6657e873fee2d71b6abf15.1739309136.git.ro...@burningswell.com> > From: Roman Scherer > Date: Tue, 11 Feb 2025 22:23:37 +0100 > Subject: [PATCH] gnu: forges: Use %

Re: [GCD] Rename “main” branch

Simon Tournier skribis: > Well, Liliana, count on me as one Sponsor for this GCD! I’m happy to be a sponsor too. Ludo’.

Re: Is `guix gc --references FOO` expected to require a writable store?

Hi, Leo Famulari skribis: > For example, I create and run a VM from the bare-bones template: > > `guix system vm --no-grafts doc/os-config-bare-bones.texi` > > Within the VM, I try the command: > > -- > # guix gc --references > /gnu/store/cbzabyh8kdks7ip1hk4cycldq1wiflg3-automake-skip-amhel

Re: Numerical problem (compiling python-numba package)

Hello, Sharlatan Hellseher skribis: > We may limit the test suite to bare minimum For the record, I reported the issue at . This appears to be an upstream problem with one specific test: https://github.com/numba/numba/issues/8282 Ludo’.

Re: The next release

Hi Efraim, Efraim Flashner skribis: > The short version: > > * We need a tagged release so we can update the version in Debian and > other distros, in CI systems, etc. > * We need a newer point-in-time for the installer. > * A new release increases interest in the project. Thanks a lot for ge

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

Tomas Volf <~@wolfsden.cz> skribis: > Ludovic Courtès writes: > >> The Savannah `guix.git` repository would become a mirror of the one at >> Codeberg, with a script periodically updating it, as a way to ease >> migration to the new repository for users. > > Will the mirroring ensure that the guix

Re: bug#55231: [PATCH v6] initrd: Allow extra search paths with ‘initrd-extra-module-paths’

Hi Maxim, Your help is much appreciated! The changes all look good, but there is one thing which is alarming me somewhat. Perhaps I am misunderstanding how the `substitutable-derivation?` function actually operates, but if I apply these patches and then run, say: ``` (use-modules (guix) (gnu)

Re: Understanding #:substitutable? and #55231

Hi Maxime, Some of your replies in this thread are overly aggressive, in clear violation of our Code of Conduct. Please refrain from singling out a group of people and assigning labels to them, or calling out someone specifically in a negative light. Since this is not the first time this has hap

Re: bug#55231: [PATCH v6] initrd: Allow extra search paths with ‘initrd-extra-module-paths’

Hi Morgan, I needed to do some changes and adjust one test, but in v6 the derivations tests now pass, and the regular operation of Guix appears otherwise unaffected, which is good (I don't need to rebuild say, Libreoffice). Could you test? -- Thanks, Maxim

Re: Waylandify all the qt-using packages - need help

Hi dannym, Would it make sense to add qt-wayland to the qt-build-system directly? Thanks, Noé dan...@friendly-machines.com writes: > Hi, > > So I've noticed that my backups haven't been run for several weeks > because vorta didn't start up because wayland. (I should make an > automated check

Re: bug#55231: [PATCH v1] initrd: Allow extra search paths with ‘initrd-extra-module-paths’

Hi Maxim, I found the cause of these failed tests, although unfortunately it doesn't seem to resolve the problem with implicit inputs from `gnu-build-system` being non-substitutable. The failing tests pass a `derivation` as input to the derivations that they construct, rather than a `derivation

Re: bug#55231: [PATCH v1] initrd: Allow extra search paths with ‘initrd-extra-module-paths’

Hi Maxim, > That's probably the GCC implicitly added by gnu-build-system, which is > listed in the %final-inputs variable. I did figure out that this was the GCC implicitly added by `gnu-build-system`, although unfortunately examining this more carefully didn't help me a whole lot with understa

Re: bug#55231: [PATCH v1] initrd: Allow extra search paths with ‘initrd-extra-module-paths’

Hi Morgan, Morgan Arnold writes: > Hi all, > >> I'm not sure if what I'm proposing would actually work. > > How prophetic. > > I did some more testing with the proposed change to `derivation`, and > it seems to be causing a weird issue. I didn't think that propagating > non-substitutability woul

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

Attila Lendvai writes: > i don't > see it acknowledged that this is way less than ideal. including that > too much of guile is written in C, [...] This is even acknowledged in the Guile manual. The commit history and the Guile maintainers own words also show that replacing more of Guile's core