cuirass manual not found
on the cuirass web page, https://guix.gnu.org/cuirass/ the link to the cuirass manual, https://guix.gnu.org/cuirass/manual/, leads to a 404 not found error
Re: Mumi Feature Request: Easier way to apply patches from web interface
宋文武, That's an great idea! Reminds me of tissue, the text based issue tracker, written in Guile by Arun Isaac: https://git.systemreboot.net/tissue/ I think it would be amazing for the guix CLI to have integration with issues/debbugs. January 29, 2023 7:31 PM, "宋文武" wrote: > "jgart" writes: > >> Note that I realize that this is possible: >> >> https://man.sr.ht/~whereiseveryone/wiki/tipsandtricks.md#applying-patches-from-issuesguixgnuorg >> >> or >> >> wget -O- https://issues.guix.gnu.org/issue/48364/patch-set/2 | git am >> >> What this feature is is to generate the appropriate command for the >> respective patch series that >> you'd like to apply from https://issues.guix.gnu.org > > Maybe add a guix command for issues/patches? > > guix issues new > guix issues open nnn > guix issues reply nnn > guix issues apply nnn > guix issues close nnn
Re: Mumi Feature Request: Easier way to apply patches from web interface
"jgart" writes: > Note that I realize that this is possible: > > https://man.sr.ht/~whereiseveryone/wiki/tipsandtricks.md#applying-patches-from-issuesguixgnuorg > > or > > wget -O- https://issues.guix.gnu.org/issue/48364/patch-set/2 | git am > > What this feature is is to generate the appropriate command for the > respective patch series that you'd like to apply from > https://issues.guix.gnu.org Maybe add a guix command for issues/patches? guix issues new guix issues open nnn guix issues reply nnn guix issues apply nnn guix issues close nnn
typo in Guix QA web page
For example: https://qa.guix.gnu.org/issue/61134 Yet to process revivion, job queued revivion probably is revision
Re: Resurrecting top-notch continuous integration for Guile
Hello, > (Speaking of which, I hereby ask fellow Guix hackers to voice any > concerns they may have regarding this use of project resources.) Please use project resources. Thank you. Kind regards, T G-R Sent on the go. Excuse or enjoy my brevity.
Re: Resurrecting top-notch continuous integration for Guile
Hi Ludo' On Sun, Jan 29, 2023 at 9:37 AM Ludovic Courtès wrote: > > I hereby ask fellow Guix hackers to voice any > concerns they may have regarding this use of project resources. I am not a Guix hacker (although maybe every user is one too) and, as a newbie, I cannot speak for the group but the Guix project is built on Guile and depends on Guile functioning properly. I cannot imagine any opposition whatsoever. The way I see it, Guixers are more likely to celebrate your proposal as a welcome milestone in the continuous evolution of Guix and Nix. > If there are no objections, I’ll merge this > branch into “main”. As it stands, Guix owes a profound debt of gratitude to Guile and its developers. There is no reason to wait. Thank you for your expert stewardship in designing the OS we all love so much! Kind regards Felix
Resurrecting top-notch continuous integration for Guile
Hello Guilers! (And hello Guix—that’s about an interesting use case. :-)) Back in 2009, together with Rob Vermaas of NixOS, we set up continuous integration for Guile (among other GNU packages), using Nix coupled with Hydra, its continuous integration (CI) system: https://lists.gnu.org/archive/html/guile-devel/2009-11/msg00084.html The CI jobs still exist although they’ve been bitrotting for ~10 years: https://hydra.nixos.org/jobset/gnu/guile-2-0 https://git.savannah.gnu.org/cgit/hydra-recipes.git/tree/guile/release.nix Ten years ago is when I embarked on this side project *cough* called Guix (Guix = Guile + Nix, see?). To close the loop, it’s natural to reinstate CI, but this time with Guix and Cuirass, its companion CI tool—Guile code all the way down! You can see these new CI jobs on the build farm of the Guix project: https://ci.guix.gnu.org/jobset/guile (Speaking of which, I hereby ask fellow Guix hackers to voice any concerns they may have regarding this use of project resources.) Code for these jobs is currently in a Guile branch: https://git.savannah.gnu.org/cgit/guile.git/log/?h=wip-cuirass-ci This branch brings several things: 1. The ‘guix.scm’ file at the top can be used to spawn a shell with a development environment for Guix: guix shell It can also be used to (cross-)build Guile, as in: guix build -f guix.scm --target=x86_64-w64-mingw32 2. ‘build-aux/manifest.scm’ defines a Guix “manifest” for several Guile builds we may want to test: building with Clang, cross-compiling to MinGW and RISCV and whatnot, building with ‘--disable-threads’, etc. 3. There’s a ‘.guix-channel’ file at the top, meaning that Guile can be used as a Guix “channel” providing additional packages. You’d do that by having something as following in ~/.config/guix/channels.scm and then running ‘guix pull’: (cons (channel (name 'guile) (url "https://git.savannah.gnu.org/git/guile.git;) (branch "wip-cuirass-ci")) %default-channels) This is arguably the weirdest part, but that’s how we get Cuirass to consume Guile. There’s still much tweaking we can do, but the basics are in place, and I find it pretty cool. :-) If there are no objections, I’ll merge this branch into “main”. It’s going to be nice to have a dashboard to look at before the next release! Feedback welcome! Ludo’. signature.asc Description: PGP signature
Re: Mumi Feature Request: Easier way to apply patches from web interface
Note that I realize that this is possible: https://man.sr.ht/~whereiseveryone/wiki/tipsandtricks.md#applying-patches-from-issuesguixgnuorg or wget -O- https://issues.guix.gnu.org/issue/48364/patch-set/2 | git am What this feature is is to generate the appropriate command for the respective patch series that you'd like to apply from https://issues.guix.gnu.org
Mumi Feature Request: Easier way to apply patches from web interface
Hi Guixers, This is a feature request for mumi. What do you think if mumi had a feature that gives the user a generated command like this one (the following url is probably not correct) and shows it in the web interface for each patch series? curl -s https://issues.guix.gnu.org/issue/61036/raw/1 | git am -3 The new user can then just copy paste the above command to apply the patch and review it. sr.ht's mailing list service implements the feature: https://lists.sr.ht/~whereiseveryone/bangs/patches/38520 See on the right in the html where it says "How do I use this?": https://lists.sr.ht/~whereiseveryone/toys/patches/38089 The code for that implementation is here: https://git.sr.ht/~sircmpwn/lists.sr.ht/tree/master/item/listssrht/templates/patchset.html#L174 It looks like they are using their graphql API to get that information for the jinja template: https://git.sr.ht/~sircmpwn/lists.sr.ht/tree/master/item/listssrht/blueprints/api/lists.py#L41
