Re: Meetup in Nice on 22/06/2024

Hi, On Mon, 27 May 2024 at 21:25, nat-418 wrote: > I am organising a meetup for folks from the Guix, Nix, Aux, Lix, etc. > communities at Foam in Nice on Saturday, June 22nd. The address is 1 > Place du Pin, and I will be there from lunch until evening. The venue is > a family-friendly

Re: Are 'guix gc' stats exaggerated?

Hi, On Sun, 26 May 2024 at 13:13, Felix Lechner via "Development of GNU Guix and the GNU System distribution." wrote: > By my math, about 65.8 GiB were recovered. > > When 'guix gc' was done, it announced: > > [184389 MiB] deleting '/gnu/store/...' > deleting `/gnu/store/trash' >

Extension for improving Guix search?

rg/archive/html/help-guix/2019-06 https://yhetil.org/guix/CAOOOohSzUezKvm=ro0bxrgh3m0eo2x0cotvd--varxwoqtc...@mail.gmail.com 7: https://guix.gnu.org/en/blog/2021/outreachy-guix-git-log-internship-wrap-up/ 8: Re: Mechanism for helping in multi-channels configuration (and Xapian index) Simon Tournier

Re: Guix pull: avoiding "Computing Guix derivation"

Hi Richard, On lun., 13 mai 2024 at 20:52, Richard Sent wrote: > You're correct. This solution wouldn't be sufficient to avoid "Computing > Guix Derivation" for every possible A or B. To my understanding it could > reduce the frequency this occurs. [...] > Assuming D changes significantly

Re: Guix pull: avoiding "Computing Guix derivation"

Hi, On lun., 13 mai 2024 at 17:11, Richard Sent wrote: > Instead of A and B building C directly, A and B download the > substitutable Guix package D, then use D to build C. Because D is a > reproducible package, it should be substitutable from both A and B. > Then, because D->C is the same for

Re: Guix pull: avoiding "Computing Guix derivation"

Hi, On lun., 13 mai 2024 at 17:04, Edouard Klein wrote: > - Why is this step not substitutable ? The inputs are known, a hash can > be derived, a substitute server could be queried for an output of that > hash ? What am I missing ? Does the guix derivation not end up in the > store ? What makes

Re: Changing the defaults for --localstatedir and --sysconfdir?

Hi, On jeu., 02 mai 2024 at 11:00, Ludovic Courtès wrote: > Richard Sent skribis: > >> As everyone who's built Guix from source knows, when running ./configure >> on a system with an existing Guix installation you must remember to >> specify --localstatedir=/var and --sysconfdir=/etc. I think

3 kinds of bootstrap (was Re: backdoor injection via release tarballs combined with binary artifacts)

Hi, I am late to the party… On mer., 10 avril 2024 at 15:57, Ludovic Courtès wrote: >> That has happened to me too. >> Why not use Git directly always? > > Because it create{s,d} a bootstrapping issue. The > “builtin:git-download” method was added only recently to guix-daemon and > cannot be

Re: Mechanism for helping in multi-channels configuration (and Xapian index)

Hi, Sorry for the long delay. On lun., 18 mars 2024 at 16:05, Christina O'Donnell wrote: >> 2: https://issues.guix.gnu.org/issue/39258 > As I said above, [2] is a fairly long thread, but I think I get the > general idea. It seems that Xapian was implemented but didn't have the > desired

Re: Scheduling a new release?

Re, On lun., 06 mai 2024 at 13:12, Simon Tournier wrote: > Although these days I do not have much free time, let make a new release > as soon as possible. WDYT? > > Who’s in? Well, the patch review sessions could be helpful. Maybe we could run some online hackathons. IMHO, havin

Scheduling a new release?

Hi all, Here or there, we have bugs as: https://issues.guix.gnu.org/70659 https://issues.guix.gnu.org/70726 And our answer looks like: > Additionally, I strongly advise upgrading guix-daemon, as noted in the > bug report above. Well, the bugs appear because the user is

time-bomb and CI? (was bug#69800: kcalendarcore time-bomb)

Hi, Reading this message [1]: Start of forwarded message Subject: bug#69800: kcalendarcore is a time bomb To: 69...@debbugs.gnu.org Date: Thu, 14 Mar 2024 20:20:43 +0100 From: Vivien Kraus via Bug reports for GNU Guix Dear Guix, Kcalendarcore does

Re: Guile CSE elimination of record accessor?

Hi Andy, Thanks for the explanations. On mar., 30 avril 2024 at 16:43, Andy Wingo wrote: >> The first question is: is it still correct? Because this module had >> been implemented before many Guile compiler improvements. > > No, the comment is incorrect. The type check on whatever accessor

Guile CSE elimination of record accessor?

Hi, In Guile module (ice-9 vlist), one reads: --8<---cut here---start->8--- ;; Asserting that something is a vlist is actually a win if your next ;; step is to call record accessors, because that causes CSE to ;; eliminate the type checks in those accessors.

Re: Adding plumbing subcommand 'derivation'?

Hi, On ven., 19 avril 2024 at 16:02, Ludovic Courtès wrote: > We should see how that fits into the set of tools we already have, in > particular the (guix derivations) interface and the REPL meta-commands. > > My gut feeling, with a Schemer bias, is that we’d rather enrich the > Scheme API

Re: bug#63267: gcc-toolchain is missing libstdc++.so

Hi, On mer., 17 avril 2024 at 05:21, John Kehayias via Bug reports for GNU Guix wrote: > I've just pushed, as b47ae1ecc43baaf726701ab2d2f810ecfaa75428, Cool! Thank you for crossing the finish line. Cheers, simon

Adding plumbing subcommand 'derivation'?

Hi Leo, On ven., 12 avril 2024 at 20:04, Leo Famulari wrote: >> Do you think it would be useful to package it? Or maybe to include it >> as another subcommand (or part of some subcommand)? > > I'd love for this to be built in to Guix. I'm often struggling to read > derivations while debugging

Guix extension to display derivation (and rewrite fixed-output)

Hi, As an Emacs user, exploring Derivation (the .drv files) is easy since there is an Emacs mode. However, I have been annoyed with some pipe through ’sed’ and friends. Therefore, I wrote a very simple Guix extension [1] that outputs derivation content using recutils format.

Re: Concerns/questions around Software Heritage Archive

Hi, On lun., 18 mars 2024 at 12:38, Ian Eure wrote: > They appear to be violating free software licenses on large scale. > They are in violation of SWH’s own positions. [...] > [1]: https://arxiv.org/html/2402.19173v1 > [2]: > https://huggingface.co/spaces/HuggingFaceH4/starchat2-playground

Re: Concerns/questions around Software Heritage Archive

Hi MSavoritias, On lun., 18 mars 2024 at 16:00, MSavoritias wrote: > I think you have misunderstood that here we are talking about > I think you have misunderstood that here we are talking about What if? Maybe it’s you. Maybe you, “you have misunderstood that here we are talking about […]”.

Re: Concerns/questions around Software Heritage Archive

oint #1. About “rewrite history”, see point #2 > 4. > > > This language is not acceptable on Guix channel of communication. > > Calling out transphobia it is very much accepted here actually :) No it is not. Because it is a bold conclusion. I am asking that the Guix project

Re: rewriting history; Was: Concerns/questions around Software Heritage Archive

Hi, On lun., 18 mars 2024 at 12:10, MSavoritias wrote: > The right of a trans person to ask a project to not advertise their > deadname was never in question. > > Guix is a place that supports trans people and anybody else that wants > to change their name. There is a difference between

Please hold your horses

Hi MSavoritias, Could you please stop to propagate tangential or opinionated views? Please hold your horses. You wrote several times, about Software Heritage: > being also transphobic. […] > I would go a step further actually. Software Heritage

Re: Concerns/questions around Software Heritage Archive

Hi, On sam., 16 mars 2024 at 08:52, Ian Eure wrote: > They appear to be using the archive to build LLMs: > https://www.softwareheritage.org/2024/02/28/responsible-ai-with-starcoder2/ About LLM, Software Heritage made a clear statement:

Content-Addressed system and history?

Hi, On sam., 16 mars 2024 at 08:52, Ian Eure wrote: > I was also distressed to see how poorly they treated a developer > who wished to update their name: > https://cohost.org/arborelia/post/4968198-the-software-heritag > https://cohost.org/arborelia/post/5052044-the-software-heritag This

Re: Helping with abandoned patches

Hi Greg, On mer., 17 janv. 2024 at 12:17, Greg Hogan wrote: > What is the preferred process for when a patch review is provided > (often by a committer) but no response is received from the submitter > (for many weeks or months)? > > Is it appropriate to make the recommended changes and submit

Re: Check for ANSI compliance

Hi, On lun., 29 janv. 2024 at 17:44, Ludovic Courtès wrote: > That used to be the case until commit > 672d3d4a87839b0692c307df0edb66cd16bcbf1a, which enabled colors even when > ‘INSIDE_EMACS’ is set. > > Pierre, do you remember what the rationale was? I am not Pierre. :-) The context seems:

Re: Request to add a go-team branch and set it on CI.

Hi, CC: guix-maintainers CC: guix-sysadmin On lun., 22 janv. 2024 at 19:58, Sharlatan Hellseher wrote: > May I ask someone with admin rights to the build farm to set up > go-team branch, please? What is the status of this request? Is it doable? I do not see the specification on

Re: Building container images with nix2container

Hi Antoine, Reading this blog post: https://lewo.abesis.fr/posts/nix-build-container-image/ and from my understanding, “guix pack” is currently something similar to ’dockerTools.buildImage’ [1] On lun., 26 févr. 2024 at 18:33, Simon Tournier wrote: > Well, I have not followed on wh

Re: Introduce Cuirass and remove Hydra on https://www.gnu.org/software/devel.html

Hi, Well, I do not see if there is a reply. If no, sorry! If yes, I am just adding my own curiosity. :-) CC: guix-maintainers and guix-sysadmin CC: Mark Weaver On lun., 08 janv. 2024 at 13:19, Jing Luo wrote: > I am Jing Luo, a new member from the GNU webmaster team. I noticed that >

Re: Building container images with nix2container

Hi lewo, On lun., 26 févr. 2024 at 11:09, Antoine Eiche wrote: > Does your built images contains several layers? This had recently been introduced. 0cf75c9b2f23869201144917cea7f6ad49683d3d AuthorDate: Tue Dec 26 03:54:12 2023 +0300 CommitDate: Mon Jan 8 21:04:44 2024

Re: Mechanism for helping in multi-channels configuration

Hi Attila, On mar., 06 févr. 2024 at 17:16, Attila Lendvai wrote: >> The wishlist is: provide a machine-readable description on guix-science >> channel side in order to help in finding the good overlap between >> commits of different channels. > > i wrote about a missing abstraction here: > >

Re: Guix Days: Patch flow discussion

Hi Clément, If read correctly, you answered about Gnus (debbugs.el): >>> --8<---cut here---start->8--- >>> (with-current-buffer gnus-original-article-buffer >>> (message-fetch-field "Message-ID")) >>> --8<---cut

Re: Guix Days: Patch flow discussion

re, open a feature request is low on my list of TODO. ;-) Cheers, simon 1: Re: Guix Days: Patch flow discussion Simon Tournier Wed, 14 Feb 2024 16:48:07 +0100 id:87mss3kpxk@gmail.com https://lists.gnu.org/archive/html/guix-devel/2024-02 https://yhetil.org/guix/87mss3kpxk@gmail.com

Re: Golang check phase skipping some tests?

Hi, On jeu., 15 févr. 2024 at 10:10, Sharlatan Hellseher wrote: > I would push go-team branch to check some lower level modifications to > go-build-system which are queued right now. I need someone with admin access > to > set the branch on CI as well ;-) Cool! Thank you. Cheers, simon

Re: Mechanism for helping in multi-channels configuration

Hi Christina, On sam., 03 févr. 2024 at 15:27, Christina O'Donnell wrote: >  1. Have a script that scrapes all the define-public symbols in every > file in >     every package. I think you mean ’fold-packages’. >  2. Have a script that determines the symbols needed by each file. (Macros >

Re: Guix Days: Patch flow discussion

Hi Josselin, On jeu., 15 févr. 2024 at 12:07, Josselin Poiret wrote: > I think b4's ML is more active than the GitHub issues, I have already > sent some bug reports and patches there that were picked up quite fast. Yeah, Kyle pointed me that out months ago. Then I have never taken the time to

Re: Guix Days: Patch flow discussion

Hi Clément, On jeu., 15 févr. 2024 at 12:45, Clément Lassieur wrote: >>> 'b4 shazam' is probably the most trouble-free way to apply patches; >> >> I agree*! > > I don't agree (both Gwene + Gnus or Emacs Debbugs work perfectly too and > allow to apply a range of n patches at once) but I don't

Re: Guix Days: Patch flow discussion

Hi, On dim., 11 févr. 2024 at 11:38, Maxim Cournoyer wrote: > 'b4 shazam' is probably the most trouble-free way to apply patches; I agree*! > it > even selects the latest revision it finds in the issue thread. To make >

Re: Guix Days: Patch flow discussion

Hi Steve, ( On a side note, the triage of old bugs is a similar problem. They are easy to find [2], read, check and send an email to 12...@debbugs.gnu.org does not appear to me an issue with any tool. For what it is worth and without any willing of being harsh, I am able

Re: Git-LFS or Git Annex?

Hi Timothy, On sam., 27 janv. 2024 at 10:59, Timothy Sample wrote: > https://git.ngyro.com/git-annex-remote-clouda/tree/git-annex-remote-clouda/remote.scm Oh cool, thanks. Bookmarked. Cheers, simon

Re: Golang check phase skipping some tests?

Hi, Late to the party. :-) Processing my backlog… On jeu., 18 janv. 2024 at 10:25, Sharlatan Hellseher wrote: > I'm currently in review and split some packages from (gnu packages golang) > into > (gnu packages golang-crypto) to simplify the maintenance. I try to play with > that option and

Re: Committers available for Patch hacking/review meet-up?

Hi, On mar., 13 févr. 2024 at 14:48, Steve George wrote: > At Guix Days we said we'd organise some patch review sessions. Cool! > Anyone available? If you are and can put your name down for a particular > date that would be brilliant! I will do. Thanks for the initiative! > Q2: Does

Google Season of Docs 2024

Hi, ( It is when my plate is full that I add more in. :-) ) Google is announcing the Season of Docs. Somehow, it is similar of Google Summer of Code but for… wait for it… documentation! https://opensource.googleblog.com/2024/02/announcing-google-season-of-docs-2024.html I would like that the

Re: bug#63775: git describe on current master says: v1.3.0-38775-g6192acf8b7

Hi, On sam., 03 févr. 2024 at 19:43, Giovanni Biscuolo wrote: > This is a git bug, not an issue with our repo, and for this reason (I > hope) I'm closing this bug; please see below. Here the explanation of the bug of “git describe”:

Re: ice-9 match penalty depending on pattern?

Hi, On mer., 07 févr. 2024 at 10:41, Carlo Zancanaro wrote: >> Why not? Do I miss something in the implementation of ’match’? > > The only reason I can think of would be if these matches are sometimes > provided improper lists, which need to fail these match conditions. That > seems unlikely

ice-9 match penalty depending on pattern?

Hi, >From Ludo’s mastodon message [1]: Re ‘match’ penalty: when using ellipses in patterns, the generated code checks for “proper lists”, which is O(n). The trick is to instead match a pair: ✔ (match lst ((head . tail) …)) ❎ (match lst ((head tail ...) …)) Therefore I have

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

salut, On jeu., 01 févr. 2024 at 20:51, Tanguy LE CARROUR wrote: > Ce jeudi 8 février 2024 à 19h, se tiendra la cinquième édition de Guix@Paris > ouverte au public. > Comme les fois précédentes, il sera possible de participer à distance > (*cf* ci-dessous). Chouette ! Ayant raté la journée de

[post Guix Days] Guix Common Document (was: Request-For-Comment process)

Hi all, I hope that the discussion we had yesterday (Friday 2nd) in Guix Days has clarified the idea behind this proposal. I am waiting Ludo’s notes in order to refine this proposal, integrate many comments and/or ideas, and polish. Thanks all participants. The aim of the proposal is to have

Mechanism for helping in multi-channels configuration

Hi, Well, using Guix bdab356 from a little bit more than one month old, then associating the channel guix-science 0b3d4a2f last week, I get the failure: --8<---cut here---start->8--- $ guix build /gnu/store/g3aa5rh7bs5pyxd3q1gvhwz1s9z1vh3z-guix-science.drv The

Re: Request-For-Comment process: concrete implementation

Hi Ricardo, On mer., 20 déc. 2023 at 12:49, Ricardo Wurmus wrote: > I just got back from travels and finally caught up with important email. > I read the proposal and it looks good to me. Thank you for working on > this! > > This would be the first project I contribute to that has an RFC

Re: Git-LFS or Git Annex?

Hi Kyle, On jeu., 25 janv. 2024 at 21:20, Kyle Meyer wrote: > Fwiw I think someone could do that outside Haskell, if they preferred, > via a custom backend: > > https://git-annex.branchable.com/design/external_backend_protocol/ > > Special remotes can also be written in other languages: > >

Re: Git-LFS or Git Annex?

Hi Ludo, all, On mer., 24 janv. 2024 at 16:22, Ludovic Courtès wrote: > The question boils down to: Git-LFS or Git Annex? Some months ago, I gave a look for managing some datasets. My conclusion is Git-Annex. The main drawback of Git-LFS is that the server needs to support the protocol. On

Re: Collecting Guix talks at FOSDEM

Hi Steve, On mer., 17 janv. 2024 at 21:16, Steve George wrote: > Hi - initial draft of the post went to Ludo today for review (and commit > as I don't have the rights). We'll see what his reaction is to my > British English and random punctuation! ;-) Cool! Thank you. For the next time, in

Re: Collecting Guix talks at FOSDEM

Hi, On Tue, 16 Jan 2024 at 15:35, Steve George wrote: > We're planning to put up a blog post about Guix (and Guix-related) talks > at FOSDEM [0]. I've collected all the talks that that are about Guix (or > connected areas). If I've missed any Guix related talks please tell me > so I can add

Re: Using the pyproject-build-system

Hi, On Tue, 16 Jan 2024 at 00:19, Troy Figiel wrote: > Although not fully PEP 517-compliant according the documentation, the > pyproject-build-system does seem to fall back to setuptools.build_meta > if the pyproject.toml is missing. Contrary to what the name implies to > me, it can therefore

Re: An update on ‘core-updates’

Hi, On Thu, 11 Jan 2024 at 16:10, Ludovic Courtès wrote: > Long story short: I’d like us to freeze and merge the branch ASAP, > notably because the glibc graft on ‘master’ leads to a bad user > experience. I’m happy with the current state of the branch and wouldn’t > mind postponing remaining

Re: Proposition to streamline our NAR collection to just zstd-compressed ones

Hi, On Tue, 09 Jan 2024 at 21:32, Maxim Cournoyer wrote: > What do you think? Should we go ahead and effect the following simple > change for the Berlin build farm? > > --8<---cut here---start->8--- > modified hydra/modules/sysadmin/services.scm > @@

Re: Golang check phase skipping some tests?

Hi, CC: $ ./etc/teams.scm list-members go Katherine Cox-Buday Sharlatan Hellseher On Sun, 14 Jan 2024 at 22:12, Troy Figiel wrote: > --8<---cut here---start->8--- > (define* (check #:key tests? import-path #:allow-other-keys) > "Run the

Re: Commit Access: Sharlatan Hellseher

Hi Oleg, On Thu, 11 Jan 2024 at 19:56, Sharlatan Hellseher wrote: > I am happy to have been granted commit access Cool! Welcome. > If anyone has a good patch review workflow using Emacs, Gnus, and Magit, > I would appreciate it ;-) Well, nothing more than what had been already suggested.

Re: $EDITOR and “guix edit”

On Fri, 12 Jan 2024 at 20:46, Liliana Marie Prikler wrote: > PS: I should probably just write the patch myself at this point, but I > feel like it'll be misunderstood either way. Sorry but I do not understand how your proposal would work in tandem with the current "guix edit". So yes, please

RE: [swh-devel] Call for public review - SWH Nix/GNU Guix stack

Hi, > The initial NixGuix loader (currently in production) lists and loads > origins from a manifest, ignoring the specific origins mentioned above. The > new stack will be able to ingest those origins. It will also optionally > associate, if present, a NAR hash (specific intrinsic identifier to

Re: $EDITOR and “guix edit”

Hi, On Fri, 12 Jan 2024 at 18:39, Liliana Marie Prikler wrote: > > Well, I see how to write specific Scheme wrapper around $EDITOR; as I > > did in [1]. > > > > Or, I see how to tweak guix/scripts/edit.scm for running specific > > launcher depending on $EDITOR. > > > > Liliana, could you

Re: $EDITOR and “guix edit”

Hi, On Mon, 20 Nov 2023 at 20:33, Liliana Marie Prikler wrote: >>  2. Do we put this code in some etc/vscode-wrapper that user can >>  install?  (or that we could automatically installl) Or maybe revamp >> it >>  for calling this code via some shell function? > > With VSCode et al. not being

Re: Building and caching old Guix derivations for a faster time machine

Hi Maxim, On Thu, 30 Nov 2023 at 08:28, Maxim Cournoyer wrote: > I'd like to have a single archive type as well in the future, but I'd > settle on Zstd, not lzip, because it's faster to compress and > decompress, and its compression ratio is not that different when using > its highest level

Re: Request-For-Comment process: concrete implementation

Hi, Well, more than 7 weeks later… Hum, does it mean that the Guix project is not interested in formalizing some RFC? WDYT about the proposal? On Tue, 31 Oct 2023 at 12:14, Simon Tournier wrote: > Hi, > > This is a proposal for implementing Request-For-Comment process. > Comment

RFC (was Re: Shutting down qa.guix?)

such move. Why not some Request-For-Comment? Request-For-Comment process: concrete implementation Simon Tournier Tue, 31 Oct 2023 12:14:42 +0100 id:87h6m7yrfh@gmail.com https://lists.gnu.org/archive/html/guix-devel/2023-10 https://yhetil

Re: Shutting down qa.guix?

Hi, On sam., 09 déc. 2023 at 11:54, Ludovic Courtès wrote: > I think this underlines a collective failure to get our act together. I do not consider a collective failure considering the payment for the service. About the maintenance of such service, that’s another question, IMHO. :-) >

Re: Moment de convivialité Guix@Paris en nov… euh… décembre

salut, On Fri, 08 Dec 2023 at 08:45, Tanguy LE CARROUR wrote: > Rendez-vous début janvier (sûrement le 11, à confirmer) pour la > prochaine ! Avec des stickers si je ne les oublie pas à nouveau. ;-) Chouette soirée ! à tantôt, simon

Re: Doing away with CentOS 6 support (Linux faux-2.6)?

Hi, On Thu, 07 Dec 2023 at 23:46, Ludovic Courtès wrote: > Back in 2018, this was deemed important for HPC clusters, where CentOS 6 > was then relatively common, as Ricardo explained: Héhé! A colleague re-installed CentOS 6 this week; for testing purpose. Hum… :-) > Five years later, it

Re: Moment de convivialité Guix@Paris en nov… euh… décembre

salut Édouard, Chouette présentation ! Je pense que cela pourrait sympa de partager ton canal. :-) à tantôt, simon

Re: GNU Mes 0.26 released

Hi Janneke, On Sun, 03 Dec 2023 at 13:50, Janneke Nieuwenhuizen wrote: > We are happy to announce the release of GNU Mes 0.26. Cool! A naive question. :-) I was randomly roaming and I have seen, for example, in file module/mescc/x86_64/as.scm: --8<---cut

Re: What's the difference between a shell environment and a profile?

Hi Konrad, On Fri, 08 Dec 2023 at 17:24, Konrad Hinsen wrote: > First, I tested some Python 2 scripts in a shell environment: > > guix time-machine -C ./channels.scm \ > -- shell --container \ >python2 python2-mmtk python2-matplotlib \ >

Re: #$(this-package-input "subversion") in git introduces a cycle

Hi Maxim, I am late to the party and maybe it is already solved. On ven., 06 oct. 2023 at 22:13, Maxim Cournoyer wrote: > I've narrowed the problem down to #$(this-package-input "subversion"); > the following diff allows the build to start: [...] > I'm puzzled as to why this happens. Would

Re: sbcl-py4cl does not appear in --list-dependent output

Hi, On mer., 29 nov. 2023 at 13:27, "jgart" wrote: > Does anyone happen to know why sbcl-py4cl doesn't appear in this output? > > guix refresh --list-dependent python-numpy > > Building the following 1490 packages would ensure 3164 dependent packages are > rebuilt: I guess sbcl-py4cl is not

Re: Upgrading Guix's security team

do your best to be around by then. I think all this should be encoded in some RFC as proposed in: Request-For-Comment process: concrete implementation Simon Tournier Tue, 31 Oct 2023 12:14:42 +0100 id:87h6m7yrfh@gmail.com https://lists.gnu.org/archive/htm

Re: guix shell init

Hi jgart, On mer., 25 oct. 2023 at 14:12, "jgart" wrote: >> Could you explain what “Nix flake” means using Guix terminology? > > Here's TLDR list of nix flake features and their guix equivalents > (maybe): Thanks for explaining. If I understand correctly, Guix does not miss some feature from

Re: Building and caching old Guix derivations for a faster time machine

Hi, On mer., 22 nov. 2023 at 19:27, Ludovic Courtès wrote: > For long-term storage though, we could choose to keep lzip only (because > it compresses better). Not something we can really do with the current > ‘guix publish’ setup though. It looks good to me. For me, the priority list looks

Feedback (was Re: Meet Guix at Capitole du Libre in Toulouse)

Hi, Thanks all people! It was a very interesting experience for me and a very good moment. I hope that we will do again in the near future. As a record for the next time, let me mention two points that help: 1. Demos! It seems very helpful to have both: Guix System and Guix on foreign

Re: [maintenance] Compressed JSON files and served file extension?

Hi, On mar., 28 nov. 2023 at 16:50, Tomas Volf <~@wolfsden.cz> wrote: > You could invoke the wget with -E flag I guess. Thanks. I will try to apply that consistently. :-) On mar., 28 nov. 2023 at 21:05, Attila Lendvai wrote: >(remember: if it's not backwards,

Re: [maintenance] Compressed JSON files and served file extension?

Hi, On Mon, 20 Nov 2023 at 14:03, Attila Lendvai wrote: > TL;DR the filename shouldn't contain the .gz extension, and the HTTP > standard is crap ("If no Accept-Encoding field is present in a > request, the server MAY assume that the client will accept any content > coding."). > > use curl

Re: [maintenance] Compressed JSON files and served file extension?

Hi Ludo, On Thu, 16 Nov 2023 at 15:40, Ludovic Courtès wrote: > That said, if you become aware of actual breakage, we can revisit this! The actual breakage is my own interaction with this file. :-) Again, it happened to me yesterday. By habits, I do: $ wget

Re: Moment de convivialité Guix@Paris en nov… euh… décembre

salut, On Thu, 23 Nov 2023 at 09:18, Tanguy LE CARROUR wrote: > Jeudi 7 décembre à 19h, se tiendra la troisième édition de Guix@Paris > ouverte au public. > Comme la dernière fois, il sera possible de participer à distance (*cf* > ci-dessous). Et pour les présents, quelques stickers Guix. :-)

Re: Request-For-Comment process: concrete implementation

Hi Efraim, Thnaks for your comments. On Thu, 23 Nov 2023 at 09:04, Efraim Flashner wrote: > Actually, in terms of suggestions, I'd add the rfc/ folder in > etc/teams.scm to set guix-devel as one of the team members. Good idea! Cheers, simon

Re: $EDITOR and “guix edit”

cheme -*- !# ;;; Copyright © 2023 Simon Tournier ;;; ;;; ;;; VSCode does not respect the convention: ;;; ;;; $EDITOR +line file ;;; ;;; and instead relies on: ;;; ;;; code --goto file:line ;;; ;;; ;;; This wrapper is a workaround. It is Scheme but it could be whatever else ;;; as Bash,

Re: [maintenance] Compressed JSON files and served file extension?

Hi, On Thu, 16 Nov 2023 at 15:40, Ludovic Courtès wrote: >> However, now I get: >> >> $ wget https://guix.gnu.org/sources.json > > If you open it in a browser though, it’s fine, because browsers and in > fact many HTTP clients other than wget, honor ‘Content-Encoding’: [...] > That said, if

Re: Request-For-Comment process: concrete implementation

Hi Ludo, Thanks for giving a look. On Thu, 16 Nov 2023 at 16:03, Ludovic Courtès wrote: > Thanks for starting the discussion! I think that getting such a process > in place is key to sustain friction-less development of Guix, giving > everyone a chance to have their voice heard. Do you have

collection of “guix pull“ bug reports

Hi, >>> https://issues.guix.gnu.org/issue/62830 >>> https://issues.guix.gnu.org/issue/63451 >>> https://issues.guix.gnu.org/issue/63830 >>> https://issues.guix.gnu.org/issue/64489 >>> https://issues.guix.gnu.org/issue/64659 >>> https://issues.guix.gnu.org/issue/64753 >>>

Re: Turning off tests leads to a different store item

Hi Maxim, On Thu, 09 Nov 2023 at 10:04, Maxim Cournoyer wrote: >> I agree. On a side note, one of the issue is the time of some tests. >> Sometimes, packaging is frustrating: build takes ages, then you fix some >> tests, think it will be good, re-launch “guix build”, another test >> failing,

Re: Turning off tests leads to a different store item

phase and depends on the former. Re: Turning off tests leads to a different store item Simon Tournier Thu, 02 Nov 2023 18:02:18 +0100 id:86y1fgm6lh@gmail.com https://lists.gnu.org/archive/html/help-guix/2023-11 https://yhetil.org/guix/86y1

Stand Guix au Capitole du Libre à Toulouse, nov. 18-19

Salut, La date du Capitole du Libre approche... Chouette ! L'organisation Capitole du Libre demande le nombre de personnes qui aideront pour le stand (une histoire de sécurité et de badge). Il serait aussi judicieux que l’on puisse avoir une idée entre nous pour faciliter la journée ou les

Re: Turning off tests leads to a different store item

Hi, On Wed, 8 Nov 2023 at 20:20, Saku Laesvuori wrote: > There is another way: simply preventing the tests from changing the > resulting store item. For example, the package could first be built > without tests and then that build tree could be copied to the build tree > of the build with tests

Re: G-expressions and chroot environment? (was Re: branch master updated: gnu: Add passff.)

Hi, On Fri, 03 Nov 2023 at 19:46, Simon Tournier wrote: > However, there is still something that I am missing. The derivations > tracks all and that’s expected; thanks G-expression machinery. :-) > However, I miss how the builder works with the chrooted environment if > nothi

G-expressions and chroot environment? (was Re: branch master updated: gnu: Add passff.)

Hi, On Sat, 28 Oct 2023 at 17:05, Clément Lassieur wrote: >> ./pre-inst-env guix show passff-host >> name: passff-host >> version: 1.2.3 >> outputs: >> + out: everything >> systems: x86_64-linux mips64el-linux aarch64-linux powerpc64le-linux >> riscv64-linux >> + i686-linux

$EDITOR and “guix edit”

Hi, The command “guix edit” returns “+N path/to/file” that is then passed to $EDITOR. Therefore $EDITOR needs the command line: $ $EDITOR +N /path/to/file Well, that is accepted by many $EDITOR, to my knowledge. At least, Emacs, Vi or less are fine with it. However, some other $EDITOR

Request-For-Comment process: concrete implementation

-For-Comment process #+DATE: 2023-10-31 + Issue: 66844 + Status: pending + Supporter: Simon Tournier + Co-supporters: * Summary The "RFC" (request for comments) process is intended to provide a consistent and controlled path for new features to enter the Guix project, so that all stakeh

Re: doc: Mention the responsibilities that blocking comes with.

Hi, On sam., 14 oct. 2023 at 11:44, Maxim Cournoyer wrote: > I thought I'd advertise this proposed change here: > that touches to our common rules, so > that everyone gets to see it/comment on it. Here is the change: --8<---cut

Re: Moment de convivialité Guix@Paris en octobre

salut Tanguy, On Fri, 27 Oct 2023 at 09:04, Tanguy LE CARROUR wrote: > Merci à ceux qui ont bravé la pluie pour venir hier soir ! > Et merci à ceux qui ont supporté de nous voir manger et boire *via* > la vidéo-conférence.  Chouette soirée ! Merci Tanguy pour la logistique. > Vu que l'on

Re: guix shell init

Hi, On Wed, 25 Oct 2023 at 04:29, "jgart" wrote: > nix flakes also allows you to create your own custom template for use with > `nix flakes init`: > > https://nixos.org/manual/nix/stable/command-ref/new-cli/nix3-flake-init#template-definitions > > We could do the same with `guix shell init`

Re: guix shell init

Hi, On Wed, 25 Oct 2023 at 04:24, "jgart" wrote: > It would generate this boilerplate somehow: > > https://guix.gnu.org/en/blog/tags/cookbook/sk/html_node/Getting-Started.html Could you be precise about the boilerplate? You would like that “guix shell --init” would generate a template for

  1   2   3   4   5   >