Re: Bug triage

Hi, On Mon, 04 Nov 2024 at 07:23, Nicolas Graves wrote: > I've tried to do some bug/patch triage yesterday and marked a bunch of > patches as "easy" when they have not been reviewed and seemed easy to > review. Thank you! Much appreciated. :-) Cheers, simon

Re: bug#74204: [bug#74112] Guix is not reproducible

Hi, On Tue, 05 Nov 2024 at 23:25, Hilton Chain via Bug reports for GNU Guix wrote: >> I can confirm the reproducibility issue. >> >> I have two x86_64-linux machines building guix to verify the fix, I'll apply >> your patch once they produce matching outputs. > > Took me quite a while to build

Re: Possible useful guix package performance data

Hi, On Mon, 04 Nov 2024 at 23:22, Ludovic Courtès wrote: > Garbage collection statistics: > heap size:72.27 MiB > allocated:100.29 MiB > GC times: 13 > time spent in GC: 0.42 seconds (45% of user time) I am puzzled by this. Well, most of the time when the garbag

(unrelated and off-topics) Visiting a future of GNU

Hi, Well, this thread is already too long… And talking does not cook the rice. ;-) My message here is only to mention my “dream” about what GNU could be; initially, I thought bah who cares then I remembered: 1. words attributed to Leslie Lamport « If you’re thinking without writing, you only think

Re: Forge and build automation

Hi, On Sat, 26 Oct 2024 at 16:43, Ludovic Courtès wrote: > (“As an online Guix discussion grows longer, the probability of ending > up talking about the email workflow approaches 1.”) My comment to make it 1. ;-) > As someone who’s often repelled by web interfaces, I have also > experimented

Re: emacs-guix

Hi, On lun., 30 sept. 2024 at 10:10, Christopher Howard wrote: > I'm not really interesting much in being a guix developer right now, > but I've gained enough proficiency in Emacs and elisp to at least > troubleshoot/investigate. The bug I am focusing currently is 73462. As far as I remember,

Re: Rebuilding a package after removing a build step

Hi Konrad, On mer., 18 sept. 2024 at 10:33, Konrad Hinsen wrote: > Unfortunately, when there are several packages with identical name and > version number in two channels, Guix silently chooses one of them. Choose when doing what? :-) When running “guix shell” or “guix package”, it should war

Re: Are Guix-generated Docker images reproducible?

Hi Konrad, On lun., 16 sept. 2024 at 13:27, Konrad Hinsen wrote: > Suppose you do > > guix time-machine --channels=channels.scm -- \ > pack --format=docker --manifest=manifest.scm > > You keep a copy of channels.scm and manifest.scm, and run the same > command a few months (and "gui

toward a plan? (was Re: Reducing "You found a bug" reports)

. Many do not have any answer – which is not welcoming and friendly. Cheers, simon 1: collection of “guix pull“ bug reports Simon Tournier Wed, 23 Aug 2023 18:17:20 +0200 id:86jztl20of@gmail.com https://lists.gnu.org/archive/html/guix-devel/2023-08 https://yhetil.org/guix/86jztl20of@gm

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

------end--->8--- 1: Re: ‘core-updates’ is gone; long live ‘core-packages-team’! Simon Tournier Wed, 04 Sep 2024 14:58:37 +0200 id:87v7zby3r6@gmail.com https://lists.gnu.org/archive/html/guix-devel/2024-09 https://yhetil.org/guix/87v7zby3r6@gmail.com

Naming “build train” instead of “merge train”?

Hi Ludo, all On Fri, 06 Sep 2024 at 11:11, Ludovic Courtès wrote: > In the end, perhaps we’ll have to negotiate on a case-by-case basis. > The important thing to me is: independent testing as much as possible, > and well-defined responsibilities and scope for the people/teams > engaging in such

Re: bug#72891: [PATCH RFC] doc: Define the purpose, membership, and creation of teams.

Hi Ludo, As you mentioned elsewhere, this patch deserves the attention of guix-devel, hence CC: guix-devel. :-) [bug#72891] [PATCH RFC] doc: Define the purpose, membership, and creation of teams. Ludovic Courtès Fri, 30 Aug 2024 12:12:04 +0200 id:fb9721adfc71b841dcb6a2575539449c

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

Hi Ludo, all, On Sat, 31 Aug 2024 at 15:03, Ludovic Courtès wrote: > To reduce world rebuilds, perhaps we’ll sometimes create “merge trains”, > whereby we’ll merge, say, the branch upgrading CMake and that ungrafting > ibus on top of ‘core-packages-team’, and then merge this combination in > ‘ma

Re: Reducing "You found a bug" reports

instead the next step seems: « Someone™ would need to implement a better way for generating good reports ». ;-) Cheers, simon 1: collection of “guix pull“ bug reports Simon Tournier Wed, 23 Aug 2023 18:17:20 +0200 id:86jztl20of@gmail.com https://lists.gnu.org/archive/html/guix-devel/2023-

Re: Question about changing versioning for TeX Live packages

Hi, On Fri, 19 Jul 2024 at 18:38, Nicolas Goaziou via "Development of GNU Guix and the GNU System distribution." wrote: > I'm only changing the `version' field. For the record, "core-updates" > currently contains all TeX Live packages with their version switched to > "2024.2". Cool! Nice it’s

Re: Should we document how to detect if build machines are reachable before trying to offload?

Hi Ludo, On Sun, 21 Jul 2024 at 14:56, Ludovic Courtès wrote: > I guess this is probably what we should permit: building locally when we > cannot offload. > > Does that make sense? Yes! This feature seems wanted. ;-) Aside it would satisfy requests [1,2] randomly picked up :-) it would help in

Re: Question about changing versioning for TeX Live packages

Hi Nicolas, Sorry if this had been answered elsewhere, I have missed it. On Sat, 15 Jun 2024 at 19:07, Nicolas Goaziou via "Development of GNU Guix and the GNU System distribution." wrote: > I'd like to change versioning for TeX Live packages. Currently, it > refers to a revision number in the

Re: Reducing "You found a bug" reports

Hi, On Mon, 17 Jun 2024 at 14:59, Ludovic Courtès wrote: >> It doesn’t feel great to tell users to report a bug for things that >> aren’t bugs. They’re either closed, or never followed up on; it’s a >> poor experience on both ends. > > I agree, it’s pretty bad. > > I’m fine removing the “report

Re: [PATCH Cuirass 1/4] specification: Ensure name is a symbol.

Hi, On Mon, 17 Jun 2024 at 15:16, Ludovic Courtès wrote: > statically-typed language programmers would be > right to laugh at us here, I admit Nah because the new feature is really nice! :-) Thanks. But it remembers me one of our first in-person discussion back then on

Re: Sustainable funding and maintenance for our infrastructure

Hi, On Thu, 11 Jul 2024 at 11:38, Ludovic Courtès wrote: > Good point. In practice we’re already doing a combination of the above > and I agree that there are probably advantages to keep it that way. Well, from my perspective, the question is architecture per architecture. I mean, I think it’

Re: ci.guix.gnu.org is getting back to life

Hi, On Thu, 11 Jul 2024 at 12:26, Ludovic Courtès wrote: > These things require constant attention. Thank you for such attention! Thanks Chris for playing the role of “database administrator”. :-) Well, it reminds me that our discussion [1] “Sustainable funding and maintenance for our infrast

Re: How to test fixed output derivations in the bordeaux build farm?

Hi, On Sat, 01 Jun 2024 at 15:26, Ludovic Courtès wrote: > Yes. You can’t “change the behavior of derivations” at build time, > except by passing GUIX_DOWNLOAD_METHODS to guix-daemon itself, provided > GUIX_DOWNLOAD_METHODS is also in ‘impureEnvVars’ of said derivation, as > you wrote. It’s in

Re: anonymized nginx logs (was Re: Guix user statistics and upstream/downstream dependencies)

Hi Ricardo, On Wed, 10 Jul 2024 at 22:15, Ricardo Wurmus wrote: > Do you want the plain log files or would the processed HTML report > (generated with goaccess) be sufficient? The HTML report will be sufficient as a start. :-) > The latest report is on

Re: GNU Mes 0.27 released

Hi Andrius, On Tue, 09 Jul 2024 at 23:15, Andrius Štikonas wrote: >> Do you mean remove guile-bootstrap from the picture? The root of this >> graph: > > I think what janneke means (correct me if I'm wrong) is that before now gash > and gash utils could only run on guile but not on mes. So that

anonymized nginx logs (was Re: Guix user statistics and upstream/downstream dependencies)

Hi Maxim, On Tue, 14 May 2024 at 07:57, Maxim Cournoyer wrote: > We have detailed anonymized nginx logs of all downloaded substitutes > from Berlin, at least. If you are interested to use this data as a > source we could probably make it available to you since it's anonymized > (real IP address

Re: GNU Mes 0.27 released

Hi Janneke, On Sat, 06 Jul 2024 at 11:16, Janneke Nieuwenhuizen wrote: > We are happy to announce the release of GNU Mes 0.27. Cool! Really nice. > Remove indirect Guile > dependencies (via Gash and Gash-Utils) from the Mes bootstrap in Guix. Do

Re: Sustainable funding and maintenance for our infrastructure

Hi Ricardo, all, I agree with many words in the thread. Reading all the messages in the thread, the solution seems to try a mix of the three options. We could imagine “buy and host” more exotic hardware but not a complete data center neither, “rent” for specific needs and ask for more “sponsor”.

Re: Sustainable funding and maintenance for our infrastructure

Hi, On Tue, 02 Jul 2024 at 16:24, Ludovic Courtès wrote: > The reason for this discussion is that we were > thinking that we should not take our existing build farms for granted > and be prepared for the future. Could you explain the rationale? I understand and fully

Breath, let take a short break :-)

Hi MSavoritias, This message is not to cut any discussion but maybe it could be helpful or a bit saner if you refrain to rehash again and again the same to all messages, replying the same (or almost) to each person expressing different opinions. No blame, and I also include myself: being very ent

Draft: dry-run + Exclude checker with package properties

Hi, Patch #71697 [1] introduces dry-run for the checkers and a way to exclude some checkers directly in the package definition. In addition to exclude checkers from the command-line. FWIW, I think it covers: > but it is too easy to forget and once the cat is out > of t

Re: Exclude checker with package properties [draft PATCH]

Hi Felix, On Fri, 21 Jun 2024 at 20:37, Felix Lechner wrote: > > Is debbugs.gnu.org having issues? > > Yes, the community0p server crashed this morning. Luckily, Debbugs > appears to be back online and added messages I sent during the outage. > Maybe yours will get there, too. Thanks. Yeah th

Re: Exclude checker with package properties [draft PATCH]

On Fri, 21 Jun 2024 at 19:51, Simon Tournier wrote: > Well, thinking about indeed it could helpful in some context to specify > the checkers to exclude at the package definition level. Other said, > this patch could be generalized. Work in progress… :-) Done here: https://issues.gui

Exclude checker with package properties [draft PATCH]

0:00 2001 Message-ID: <8cb162bcde91d3b39453de576caadb9a6f8f8733.1718990517.git.zimon.touto...@gmail.com> From: Simon Tournier Date: Fri, 21 Jun 2024 19:17:57 +0200 Subject: [PATCH] guix: lint: Honor 'no-archival?' package property. * guix/lint.scm (check-archival): Skip the checker

About SWH, let avoid the wrong discussion

Hi all, For the record, the Software Heritage initiative is supportive of the Guix project since years. It means that members of Guix community have or had interactions with Software Heritage (SWH) teams since years. For example, the blog post “Connecting reproducible deployment to a long-term s

Re: Next Steps For the Software Heritage Problem

Hi, On Thu, 20 Jun 2024 at 19:42, Dale Mellor wrote: > I'm sure guix lint tried to push my code out to them the last time I > tried. Yes, it’s the checker ’archival’. Therefore, running “guix lint -x archival” does not send any request to SWH. Cheers, simon

Re: Next Steps For the Software Heritage Problem

Hi MSavoritias, all, On Thu, 20 Jun 2024 at 09:51, MSavoritias wrote: >> Not to avoid the question but from a pragmatic point of view, one >> might ask if the source code you write and do not want to be included >> in the training dataset, if this source code is concretely part of >> that traini

Re: Next Steps For the Software Heritage Problem

Hi MSavoritias, all, Let me provide more context. The concern started couple of months ago, to my knowledge. And discussion is still on going. So I think that’s incorrect to say “any result for over 6 months”. Moreover, I feel you have a misunderstanding about HuggingFace and SWH partnership.

Re: Next Steps For the Software Heritage Problem

Hi Ian, all, On Tue, 18 Jun 2024 at 10:57, Ian Eure wrote: > Guix is continuing to partner with SWH in spite of their continued > support of these violations. Quickly because I am in the middle of a busy day. :-) I think that LLM asks ethical and legal question that even FSF or EFF or SFC doe

Re: "guix pack -f docker" does too much work

Hi, On Sat, 01 Jun 2024 at 15:58, Ludovic Courtès wrote: >> I think it would be great if "guix pack -f docker" could avoid building >> all these identical layers again and again. Perhaps it would be >> possible to have a single derivation for each layer? This way we >> wouldn't have to recreat

Re: Postmortem of service downtime

Hi Ludo, On Thu, 23 May 2024 at 19:31, Ludovic Courtès wrote: > From Sunday May 19th to Tuesday may 21st, for about 36h, > bayfront.guix.gnu.org, the machine behind many services went down: > > https://lists.gnu.org/archive/html/info-guix/2024-05/msg0.html > > Affected web sites and servic

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 bar/re

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' > de

Extension for improving Guix search?

https://lists.gnu.org/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 in

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 less

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 e

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 we

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 spee

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 not

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 is

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 and/o

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 o

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. --8<---

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

, see point #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 pr

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 “adve

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: https://www.softwareheritage.org/2023/10/19/swh-state

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 ask

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 an

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 > gnu.or

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 +0

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: > > htt

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 here---end-

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 thi

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 > find

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 to

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 s

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 anyo

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 G

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”: https://lore.kernel.org/git/20191008123156.gg11...@szeder

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 to

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 a

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 proces

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 G

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 t

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 al

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 u

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 > @@ -683,7

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 tests

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. We

  1   2   3   4   5   >