Re: ‘core-updates’ is gone; long live ‘core-packages-team’!

Christopher Baines writes: [cc: Efraim] > Janneke Nieuwenhuizen writes: > >> Maxim Cournoyer writes: >> >>> Sorry for reviving a 14 weeks old thread, I'm still catching up >>> post-move :-). >> >> Ah that explains why I missed this... >> >>> Christopher Baines writes: [..] >> We've been seeing

Re: ‘core-updates’ is gone; long live ‘core-packages-team’!

Well, since the thread was revived anyway... Ludovic Courtès writes: > Hi again! > > Over the years, consensus emerged that ‘core-updates’, as a branch where > we lump together all sorts of rebuild-the-world changes, is no longer > sustainable. So, uh, how should I sent patches for that? Befo

Re: Using Pipewire for PulseAudio and JACK in Guix

Hi, di...@subvertising.org writes: [...] > Just for the record, jack-mixer has been added to the repository: > > https://git.qa.guix.gnu.org/guix-patches/commit/gnu/packages?h=issue-74251&id=bf62681bf2fe7a61a07aa0ef05262a6dd39819c6 Well done! -- Thanks, Maxim

Re: Use and abuse of ‘computed-origin-method’: the ‘rust-ring’ case

Hi! Efraim Flashner skribis: >> Anyway, the ‘computed-origin-method’ hack prevents input rewriting from >> working as expected because the inputs of that big gexp aren’t visible >> by just traversing the package graph. That’s a problem. > > Are we talking about the inputs used for the computed-

work-in-progress team branches (was: Re: ‘core-updates’ is gone; long live ‘core-packages-team’!)

Hi, Christopher Baines writes: [...] >>> Hm. So is the intention that the moment a branch is created, it is >>> expected to be in a good shape to be merged? >> >> [..] >> >>> For multi-people team endeavours (e.g., GNOME, although Liliana has been >>> doing most of the work (thanks!)), it seem

Re: ‘core-updates’ is gone; long live ‘core-packages-team’!

Maxim Cournoyer writes: > Sorry for reviving a 14 weeks old thread, I'm still catching up > post-move :-). Ah that explains why I missed this... > Christopher Baines writes: > > [...] > >>> The manual currently says it goes to 'staging' [1], and that this will >>> be merged within six weeks. Is

Re: Guix (and Guile's) promise, and how to (hopefully) get there

Maxim Cournoyer writes: > Hey, > > "Thompson, David" writes: > >> On Sun, Oct 27, 2024 at 3:13 PM Ekaitz Zarraga wrote: >>> >>> Many people on this project have tried to change GNU from the inside and >>> are very critical with the FSF (see the https://gnu.tools/). I think >>> that's also a goo

Re: ‘core-updates’ is gone; long live ‘core-packages-team’!

Maxim Cournoyer writes: > Hi Chris, > > Sorry for reviving a 14 weeks old thread, I'm still catching up > post-move :-). No worries, I hope move things are going well. > Christopher Baines writes: > > [...] > >>> The manual currently says it goes to 'staging' [1], and that this will >>> be mer

Re: [PATCH 1/2] teams: Add hurd team.

Ludovic Courtès writes: > Janneke Nieuwenhuizen skribis: > >>> Am Tue, Dec 03, 2024 at 02:34:10PM +0100 schrieb Janneke Nieuwenhuizen: * etc/teams.scm (hurd): New team. >>> >>> I think you should simply push these two patches :) >> >> Pushed as 38bbed33a28524c26ca794117f6dfed1529e2807, thank

Re: On the quest for a new release model

On Fri, Dec 13, 2024 at 01:03:05PM +0100, Ricardo Wurmus wrote: > Hi, > > Thanks for moving this discussion forward. I do think we need much more > regular releases. > > > - devel as the branch for developments, master for releases and > > security/bug fixes > > Changing the branching model i

Re: ‘core-updates’ is gone; long live ‘core-packages-team’!

Janneke Nieuwenhuizen writes: > Christopher Baines writes: > > [cc: Efraim] > >> Janneke Nieuwenhuizen writes: >> >>> Maxim Cournoyer writes: >>> Sorry for reviving a 14 weeks old thread, I'm still catching up post-move :-). >>> >>> Ah that explains why I missed this... >>> Christ

Re: Use and abuse of ‘computed-origin-method’: the ‘rust-ring’ case

Thanks for bringing this up! rust-ring, while an interesting experiment in how to package software which doesn't play well with rebuilding sources, is certainly not something we want to have be the norm. On Sat, Dec 14, 2024 at 11:37:53PM +0100, Ludovic Courtès wrote: > Hello Guix, > > ‘rust-rin

Re: Including code in a non-Guile language into Guix

Hello, Simon Tournier writes: > Hi, > > On Thu, 31 Oct 2024 at 17:15, Ricardo Wurmus wrote: > >>> by rewriting some of the >>> code in a more performance-oriented language like C? >> >> No. >> >> Guile is not the bottleneck. > > For what it is worth, some months ago I gave a look to ’sort’. > >

Re: gnus debbugs searches?

Hi! Christopher Howard writes: > Hi, I am trying now to troubleshoot some of the emacs-guix bugs I had > reported, but got hung up on something else: It seems that none of the > gnus bug searching functions from emacs-debbugs are working for me. If > I know the bug number already, I can run debb

Re: bug#74715: Request for merging "python-team" branch

Hi, Maybe we may put some news about changes in pyproject build system? Thanks Oleg

Re: ‘core-updates’ is gone; long live ‘core-packages-team’!

Janneke Nieuwenhuizen writes: > Maxim Cournoyer writes: > >> Sorry for reviving a 14 weeks old thread, I'm still catching up >> post-move :-). > > Ah that explains why I missed this... > >> Christopher Baines writes: >> >> [...] >> The manual currently says it goes to 'staging' [1], and tha

Re: packages.guix.gnu.org down

Hi Christopher, On Sun, Dec 15, 2024, at 6:10 PM, Christopher Baines wrote: > "Ian Eure" writes: > >> Hi Guixers, >> >> Looks like https://packages.guix.gnu.org/ has been returning 504 errors for >> a few weeks. >> >> Any idea when it'll be back? > > Looks like it's working currently. > Indeed

Re: On the quest for a new release model

Suhail Singh writes: > Ricardo Wurmus writes: > >> I've only ever signed off on one release (0.13.0?) and I'd be happy to >> help get another one out of the door. > > What does making a release entail? Is this documented somewhere? It is documented: https://git.savannah.gnu.org/cgit/guix/main

Re: On the quest for a new release model

Ricardo Wurmus writes: >> What does making a release entail? Is this documented somewhere? > > It is documented: > > https://git.savannah.gnu.org/cgit/guix/maintenance.git/tree/doc/release.org Thank you. Should this be linked from the Guix manual? Or is the omission intentional? -- Suhail

Re: Guix (and Guile's) promise, and how to (hopefully) get there

Divya Ranjan writes: > Similarly, I would suggest the thoughts on improving Guix/Guile to > look at aspects of the project where we might not be doing the best > job, or if we can take different steps in terms of reachout. But as an > user and contributor, please don’t take steps to separate Guix

Re: bug#74715: Request for merging "python-team" branch

Hi Lars-Dominik, On Sun, Dec 15, 2024, at 6:28 AM, Lars-Dominik Braun wrote: > Hi Ian, > >> Since this merge landed, the builds for several Python packages in my >> personal channel broke. Any package using pyproject-build-system for a >> Python project using setuptools seems to be affected. >

Re: bug#74715: Request for merging "python-team" branch

>dim. 15 déc. 2024 at 17:53, "Ian Eure" wrote: > Would it be helpful to open a bug about this? I confirm, this line (inputs (list python-setuptools python-wheel)) fixes the issue for me. However, ‘guix lint’ complaints about python-setuptools not necessary. -- Cayetano Santos GnuPG Key:

Re: packages.guix.gnu.org down

"Ian Eure" writes: > Hi Guixers, > > Looks like https://packages.guix.gnu.org/ has been returning 504 errors for a > few weeks. > > Any idea when it'll be back? Looks like it's working currently. I noticed some issues with data.guix.gnu.org (which packages.guix.gnu.org uses) and cleaned things

Re: On the quest for a new release model

Efraim Flashner writes: > Since, IMO, the major uses of the actual guix package is for the daemon > and the installer, I think we could tag a minor release just about every > time we bump the guix package. > > Lets make releases boring :) I'm a very boring person, so this deeply resonates with m

Re: ‘core-updates’ is gone; long live ‘core-packages-team’!

Tomas Volf <~@wolfsden.cz> writes: >> Over the years, consensus emerged that ‘core-updates’, as a branch where >> we lump together all sorts of rebuild-the-world changes, is no longer >> sustainable. > > So, uh, how should I sent patches for that? Before, I was able to mark > patches as intended

Re: GNU Manuals in Info/HTML format via Guix?

Jeremy Bryant writes: > The GNU Project's documentation format is Texinfo. How about > distributing some or many Texinfo manuals through Guix, is this > something that is consistent with previous norms in Guix? Guix has had SICP available via Info format since 2016:

Re: work-in-progress team branches

Maxim Cournoyer writes: > Hi, > > Christopher Baines writes: > > [...] > Hm. So is the intention that the moment a branch is created, it is expected to be in a good shape to be merged? >>> >>> [..] >>> For multi-people team endeavours (e.g., GNOME, although Liliana has been

packages.guix.gnu.org down

Hi Guixers, Looks like https://packages.guix.gnu.org/ has been returning 504 errors for a few weeks. Any idea when it'll be back? Thanks, -- Ian

Re: bug#74715: Request for merging "python-team" branch

On Sun, Dec 15, 2024 at 10:29:03AM +, Sharlatan Hellseher wrote: > Hi, > > Maybe we may put some news about changes in pyproject build system? I think that's a great idea.

Re: gnus debbugs searches?

Maxim Cournoyer writes: > Hi! Hi Maxim, >> Hi, I am trying now to troubleshoot some of the emacs-guix bugs I had >> reported, but got hung up on something else: It seems that none of the >> gnus bug searching functions from emacs-debbugs are working for me. If >> I know the bug number already,

Make a riscv iso for Guix

It would be nice to have a fully libre distro for riscv cpus.

Re: 01/04: gnu: libtorrent-rasterbar: Update to 2.0.10.

> PAGER= git log --author=felix.lechner | wc -l > 823 $ PAGER= git log --oneline --author=felix.lechner | wc -l 62 -- • attila lendvai • PGP: 963F 5D5F 45C7 DFCD 0A39 -- “I believe that education, therefore, is a process of living and not a preparation for future living.” — John Dewey (1

Re: bug#74715: Request for merging "python-team" branch

Hi, > Would it be helpful to open a bug about this? there is https://issues.guix.gnu.org/69997, which includes patches to add initial pyproject.toml support to `guix import pypi`. Lars

Re: On the quest for a new release model

Ricardo Wurmus writes: > Efraim Flashner writes: > >> Since, IMO, the major uses of the actual guix package is for the daemon >> and the installer, I think we could tag a minor release just about every >> time we bump the guix package. That's a sensible approach. How should the discussion proc