Re: Google Summer of Code 2023 Inquiry

Hi Kyle, On Tue, 04 Apr 2023 at 14:32, Kyle wrote: > The CRAN importer, for example, cannot yet detect non-R > dependencies. So, the profile author has to figure those out for > themselves. It's still very useful despite not being perfect. Yeah, improving the importers is very

Re: [internship]GSoC proposal review period begins today

Hi Gábor, On Mon, 20 Mar 2023 at 20:47, Gábor Boskovits wrote: > the proposal submission deadline, which is 4th April, 1800 UTC. This is a > hard deadline, contributors not submitting a proposal by this deadline are > ineligible to participate in this round of GSoC. Ouch! Well, I was in

Re: How to manage package replacements?

Hi Chris, On Tue, 28 Mar 2023 at 12:51, Christopher Baines wrote: > This is probably connected with package replacements, maybe the original > package definition should be marked as hidden? Anyway, I think the > bigger point here is I'm not sure what's meant to be done when adding >

SWH: extend sources.json and Mercurial (or not Git and not tarball)

Hi, On Thu, 16 Mar 2023 at 12:48, Ludovic Courtès wrote: > 1. Reproducibility of past revisions. If we lose copies of the > auto-generated tarballs, then OpenJDK in past revisions of Guix is > irreparably lost. We should check whether/how to get them in > Disarchive + SWH.

Re: Google Summer of Code 2023 Inquiry

Hi, On Mon, 03 Apr 2023 at 20:41, Spencer Skylar Chan wrote: >> I would expect most software versions to not be in Guix. Simon had >> mentioned that this is mostly what the guix-past repository is >> for. However, some packages might be buried on some branch or some >> commit in some Guix

Re: disarchive: disassemble then assemble tarball

Hi, On Mon, 03 Apr 2023 at 14:19, Timothy Sample wrote: > The ‘assemble-tarball’ procedure assumes (without checking) that it has > access to a copy of its input in the “workspace” directory. Normally, > it would be called from the generic ‘assemble’ procedure, which ensures > this (and also

Re: Disarchive database synchronization

Hi, On sam., 18 mars 2023 at 13:49, Timothy Sample wrote: >> (input (directory-ref >>(version 0) >> - (name "webview-sys-0.6.2") >> + (name "rust-webview-sys-0.6.2") [...] >> As Tim pointed out, Disarchive

Re: State of core-updates

Hi Andreas, On mar., 14 mars 2023 at 21:43, Andreas Enge wrote: >> Well, maybe it could be helpful if now Berlin or Bordeaux starts to >> build etc/release-manifest.scm. WDYT? > > That sounds like a great next step. Someone just has to do it™... The set of Someone is restricted since it

disarchive: disassemble then assemble tarball

Hi, Discussing in #62153 [1], it is noticed that Disarchive is not working as expected. For instance, using the ’gnu’ folder containing ’.go’ files. $ tar cvf my-gnu.tar gnu $ guix shell disarchive guile guile-lzma $ mkdir sha256 $ guile scheme@(guile-user)>

Re: Preservation of Guix (PoG) report 2023-03-13

Hi, On Mon, 13 Mar 2023 at 19:37, Timothy Sample wrote: > Note that you can link to the most recent version of the report using > . Awesome! \o/ Well, I do not remember if you consider also the ’origin’ (fixed-outputs) as ’inputs’ or ’patches’. Do you?

Re: Google Summer of Code 2023 Inquiry

Hi, On Sat, 11 Mar 2023 at 14:32, Simon Tournier wrote: > and probably more in the bug > tracker. For instance, you might be interested by: https://issues.guix.gnu.org/issue/43442#9 https://issues.guix.gnu.org/issue/43442#11 as dis

Re: GSoC 2023

Hi, On Wed, 08 Mar 2023 at 18:32, Simon Tournier wrote: > and probably more in the bug > tracker. For instance, you might be interested by: https://issues.guix.gnu.org/issue/43442#9 https://issues.guix.gnu.org/issue/43442#11 as dis

Re: Caching test results separately?

Hi, On Mon, 13 Mar 2023 at 23:21, Josselin Poiret wrote: >> (⇒ keep the test result (boolean) longer than the build result) [...] > As it stands it's really not possible, as > > 1) testing is part of the build process itself and > 2) we can't look-up any stateful info like this from the

Re: Using Guix inside a Guix container

Hi Konrad, On sam., 18 févr. 2023 at 10:21, Konrad Hinsen wrote: > Both examples are about composing tools freely, without worrying if they > use Guix internally or now. Thanks for explaining and the use-cases. Well, maybe a discussion for gwl-devel… well, I have started one. :-) Cheers,

Re: State of core-updates

Hi, On ven., 10 mars 2023 at 15:58, Andreas Enge wrote: > let me start with a call for help! I realise that it takes me about one > week and something close to 100GB on my poor 2-core laptop to rebuild > the bulk of core-updates up to the packages in my profile, and that is not > sustainable.

Re: bug#61894: [PATCH RFC] Team approval for patches

Hi Maxim, On Sat, 11 Mar 2023 at 22:26, Maxim Cournoyer wrote: > I'm sorry that you feel that way. I don't think consensus was willfully > broken, and perhaps by studying some actual examples of these > occurrences we can better understand what went wrong and how the new > suggested policy

Re: bug#61894: [PATCH RFC] Team approval for patches

Hi, On Sat, 11 Mar 2023 at 21:33, Maxim Cournoyer wrote: > It may help to shed a bit of light on the original reason I think this > change came into existence, and in the interest of transparency and > hopefully improving or finding alternatives to the proposed change, I > consent to Ludovic

Re: Google Summer of Code 2023 Inquiry

Hi Skylar, CC: Ricardo and Kyle On Mon, 06 Mar 2023 at 20:31, Spencer Skylar Chan wrote: > I've been running the Guix package manager with Arch Linux on my work > computer for 1 year and Guix system on my non-work computer for 1/2 > year. I've contributed some package upgrades to Guix with

Re: bug#61894: [PATCH RFC] Team approval for patches

Hi, On Sat, 11 Mar 2023 at 00:19, Andreas Enge wrote: > In the longer run I also agree with (b). But I am not sure it will be easy > to formulate a rule that captures well the intended policy and draws the > line between "trivial", anybody can push any time, and "complex", where more > opinions

Re: Emacs next variants

Hi, On Fri, 10 Mar 2023 at 17:59, John Kehayias wrote: > During this discussion some changes were made to this inheritance structure in > > > > and > >

Re: bug#61894: [PATCH RFC] Team approval for patches

Hi Andreas, Re-reading the thread, I think we started with different frames. :-) On ven., 10 mars 2023 at 15:19, Andreas Enge wrote: > while I am sensitive to your argument about privileges, I am afraid that > the suggestion would remove privileges from the committers, while not > bestowing

Re: Emacs next variants

Hi, On Fri, 10 Mar 2023 at 16:04, Cayetano Santos wrote: > Fine with me, even if to me emacs-next means latest from master, > including tree-sitter. You decide to use the feature, or not. Just to be sure we are on the same wavelength. :-) The package emacs-next is not currently following

Re: Emacs next variants

Hi, On jeu., 09 mars 2023 at 19:51, Cayetano Santos wrote: > (emacs-next-tree-sitter (emacs-next-gtk (emacs-next (emacs [...] > (emacs-next-gtk (emacs-next-tree-sitter (emacs-next (emacs Note that emacs-next-tree-sitter is not from the 29 branch (emacs-next) but from the 30

Re: bug#61894: [PATCH RFC] Team approval for patches

Hi, On Wed, 08 Mar 2023 at 13:58, Maxim Cournoyer wrote: > number of their R package updates (thanks!)). It seems starting to use > the 'Reviewed-by' git message tag would make this easy to account for. Quoting from thread [1]: I agree that Reviewed-by would be helpful. Once

Re: bug#61894: [PATCH RFC] Team approval for patches

Hi Maxim, On Wed, 08 Mar 2023 at 12:05, Maxim Cournoyer wrote: > On a side note, it would also introduce some kind of hierarchy in the > group, which I dislike. One of the things that make Guix special is > that it's pretty flat -- everybody can participate at the same level, at > least

Re: GSoC 2023

Hi, On Mon, 06 Mar 2023 at 23:44, Karim Taha wrote: > Hello all, I'm Karim Taha, a senior computer engineering student at > Cairo University. I'm interested in the Guix project list for the 2023 GSoC > program. I would like to work on ' Robustify long-term support for > Reproducible Research'

Re: The package/inherit trap

Hi Tobias, On Tue, 07 Mar 2023 at 22:11, Tobias Geerinckx-Rice wrote: > However, merely documenting something is not enough when we have the > chance to fix misleading naming, as we do here. It would be nice to > have, but orthogonal. I would not say it is orthogonal because renaming would

Re: guix install nyxt failure

Hi, On Wed, 02 Nov 2022 at 13:33, zimoun wrote: > However, you report an issue with inkscape when there is no path between > nyxt and inkscape; at least, it is what “guix graph --path nyxt > inkscape” says. My bad, that’s incorrect: --8<---cut

Re: The package/inherit trap

Hi Maxim, On Tue, 07 Mar 2023 at 11:43, Maxim Cournoyer wrote: >> @lisp >> (use-modules (gnu packages gdb)) ;for 'gdb' >> >> (define gdb-sans-guile >> (package >> (inherit gdb) >> (inputs (modify-inputs (package-inputs gdb) >> (delete "guile") >> @end lisp > > Do

Re: Feedback on indentation rules

Hi Maxim, On Tue, 07 Mar 2023 at 11:54, Maxim Cournoyer wrote: >> For what it is worth, I do not see an high difference between the both >> indentations. So, my opinion would to keep the current practise. > > Please take a look at my original message in this thread, >

Re: bug#61894: [PATCH RFC] Team approval for patches

Hi, On Tue, 07 Mar 2023 at 11:36, Andreas Enge wrote: > 1) Every current and potential new package is covered by a team. > 2) Every team has at least 3 members, better yet 4 or 5. >3 members would make it possible that even if one of them is on vacation >or otherwise busy a patch could

Re: Feedback on indentation rules

Hi, On Mon, 06 Mar 2023 at 17:56, Ludovic Courtès wrote: > Maxim Cournoyer skribis: > >> Thanks for the feedback. I wonder if some are of the opinion that since >> gexp->derivation is a plain function rather than a syntax having a >> special form for its 2nd argument, we should leave the

Re: Follow-up on julia import script

Hi Nicolas, On Mon, 06 Mar 2023 at 12:23, Nicolas Graves wrote: > I have a WIP version which should solve the issues of hash and > native-inputs. Awesome! > I still have the two following issues, if someone has a hint: > >> - there's a difficulty for defining guix-name->julia-name with the >>

Re: intrinsic vs extrinsic identifier: toward more robustness?

Hi, On Mon, 06 Mar 2023 at 13:22, Maxime Devos wrote: >>> For git-fetch, the value of the 'commit' field is intrinsic (except when >>> it's a tag instead). >> >> No, it is imprecise. The exception is *not* label tag as value for the >> ’commit’ field but the exception is Git commit hash as

Re: The package/inherit trap (was: gnu: stellarium: Enable ShowMySky.)

Hi, On Fri, 03 Mar 2023 at 20:21, Tobias Geerinckx-Rice wrote: > Could we rename it to something like > ‘package+replacements/inherit’? To me, that captures the spirit, > without being overly longer. Well, I gave a look at the code and have seen the replacement. But I had not thought about

Re: Guix v1.1.0 (~2020) and Software Heritage & friends

Hi Ludo, Thanks for giving a look and for your insights. On Mon, 6 Mar 2023 at 21:40, Ludovic Courtès wrote: > Maybe we should write down a road map and “recruit” on these items? Yeah, I totally agree. :-) For what it is worth, in that mood, for instance, + GSoC

Re: intrinsic vs extrinsic identifier: toward more robustness?

Hi Maxime, Thanks for your comments. On Sat, 04 Mar 2023 at 01:08, Maxime Devos wrote: > To my understanding, there is only one 'real' identifier in Guix: the > (sha256sum (base32 ...)) (*). Those other identifiers like the URL in > url-fetch and git-fetch are just hints on where to find

intrinsic vs extrinsic identifier: toward more robustness?

Hi, I would like to open a discussion about how we identify the source origin (fixed output). It is of vitally importance for being robust on the long-term (say 3-5 years). It matters in Reproducible Research context, but not only. # First thing first === ## What is an

Re: Projects for the Google Summer of Code

Hi, On Fri, 3 Mar 2023 at 01:51, Kyle Andrews wrote: > > Do you mean ’guix.install()’ from r-guix-install? > > > > https://cran.rstudio.com/web/packages/guix.install/index.html > > > > How do you install Python packages from the Python REPL? > > With the reticulate package in R, a python

Re: Guix, Nix flakes, and object capabilities

Hi, On Tue, 28 Feb 2023 at 22:13, Jonathan Frederickson wrote: > I recently had a discussion in #spritely on Libera.Chat about Guix and > Nix, and in particular a (relatively) new feature of Nix called flakes > that Guix doesn't currently have an analogue for. Well, even after several

v1.1.0 (~2020) and SWH: Part II

Hi, Let continue the investigations. Now, assume that: guix time-machine -C /tmp/v1.1.0cm -- help passes, where /tmp/v1.1.0.scm is defined elsewhere in this thread. We spot these issues: + Holes in the coverage guile-json-3.2.0.tar.gz.drv

Guix v1.1.0 (~2020) and Software Heritage & friends

Hi, Here I would like to report my attempt to simulate a “network collapse” – as discussed with Mathieu at Guix Days. :-) What is the minimal set of machines for running “guix time-machine” from a current Guix to an older one? Using this, archive.softwareheritage.org

Re: Question on the process of packge withdrawal

Hi, On Tue, 28 Feb 2023 at 17:26, wrote: > IMO, it's a matter of storing the junk where it will not be a toxic liability > and nuisance, yet easily discovered by someone looking for "parts." Well, I will not call that "junk". :-) IMHO, this is discoverable since it is part of the Git history

Re: Follow-up on julia import script

Hi, On lun., 27 févr. 2023 at 19:01, Nicolas Graves via "Development of GNU Guix and the GNU System distribution." wrote: > That's what I meant, but it seems indeed impossible. In the hypothesis > this juliahub script gets merged, what should we do? Really cloning the > repository and getting

Re: Question on the process of packge withdrawal

Hi, On dim., 26 févr. 2023 at 20:11, Sharlatan Hellseher wrote: > Other example > > > the reason it's not updated at - > development was moved to

Re: Follow-up on julia import script

Hi Nicolas, On lun., 27 févr. 2023 at 12:37, Nicolas Graves via "Development of GNU Guix and the GNU System distribution." wrote: > What we get from juliahub is really not bad, since it's really close to > what we have in other importers. Oh cool! Thanks. > - we don't have a `hash` field

Re: Merging branch wip-haskell

Hi, On Sun, 26 Feb 2023 at 10:47, Lars-Dominik Braun wrote: > the branch has been merged into master. \o/ Nice, thank you! Cheers, simo

Re: Follow-up on julia import script

Hi, >> DataAPI = "9a962f9c-6df0-11e9-0e5d-c546b8b5ee8a" >> DataValueInterfaces = "e2d170a0-9d28-54be-80f0-106bbe20a464" >> IteratorInterfaceExtensions = "82899510-4779-5014-852e-03e436cf321d" >> LinearAlgebra = "37e2e46d-f89d-539d-b4ee-838f9c8e" >> OrderedCollections =

Re: ’inherit’ and list-dependent (was Re: branch master updated: gnu: emacs: Add TREE_SITTER_GRAMMAR_PATH support.)

Hi, On Sat, 25 Feb 2023 at 19:10, Ludovic Courtès wrote: >>> In effect that means keeping back the chain of inherited objects, which >>> would lead to space leaks. [...] >> What do you mean by “space leaks”? > > Unbounded memory usage: each copy of an object is linked back to its > “parent”

Re: Projects for the Google Summer of Code

Hi, On Sun, 26 Feb 2023 at 16:52, Kyle wrote: > One idea might be to write a conda importer which looks at the > versions of software in the resulting environment and tries to make > feasible package variants of make a manifest which matches the > existing conda environment as close as

Re: Follow-up on julia import script

Hi Nicolas, On Sat, 25 Feb 2023 at 11:11, Nicolas Graves via "Development of GNU Guix and the GNU System distribution." wrote: > How would you separate inputs from propagated-inputs in this case (and > in Julia in general)? Well, I am not sure to understand the question. Basically, Julia

Re: Internship coordination status report

Hi, Thanks Gábor for mastering the organisation. :-) On Fri, 24 Feb 2023 at 19:21, Gábor Boskovits wrote: > This year the GNU Project was applying again for GSoC, and > we got the word yesterday that the GNU Project was accepted. Congrats! \o/ > Thanks to Jose E. Marches for taking care of

Re: Follow-up on julia import script

Hi, Thanks for this fresh input! :-) On ven., 24 févr. 2023 at 17:35, Nicolas Graves via "Development of GNU Guix and the GNU System distribution." wrote: > - Apparently Nicolo also has a similer code. I guess, it is that:

Re: Guix release broken without substitutes on ungrafted openssl

Hi, I overlooked the issue. Here, it is about just building because the test suite is time-dependant. Arf! IHMO, it does not change my previous but unrelated message. :-) Cheers, simon

Re: ’inherit’ and list-dependent (was Re: branch master updated: gnu: emacs: Add TREE_SITTER_GRAMMAR_PATH support.)

Hi, On Tue, 21 Feb 2023 at 23:55, Ludovic Courtès wrote: >> However, we could imagine to use ’package/inherit’ or another variant >> instead of plain ’inherit’ for creating these inherited packages. Doing >> so, we could collect some information, e.g., in the field ’properties’, >> which could

Re: Thoughts on committers pushing simple changes from other committers?

Hi, On Tue, 21 Feb 2023 at 10:52, Vagrant Cascadian wrote: > There is also no sign like "this has been reviewed by N people" better > than one person authoring it and another person pushing and signing it, > with some Reviewed-by or other relevent tags in the commit. I agree that Reviewed-by

Re: Ocaml (was: Merging core-updates?)

Hi Julien, On dim., 19 févr. 2023 at 10:15, Julien Lepiller wrote: > ocaml-4.14 and ocaml-5 don't have this issue. I just pushed a fix for > ocaml-4.09. I'll also have to fix ocaml-4.07 since it fails to build as > early as camlboot. It'll take a while to test. Thanks for pointing me > to that

Re: Using Guix inside a Guix container

Hi Konrad, On mer., 15 févr. 2023 at 10:49, Konrad Hinsen wrote: > That would create a container from the Guix profile. Not sure if this > works at all, but it's very probably not what I want because I have to > add other packages to my container, to get some real work done :-) I am sure you

Re: Golang go-updates feature branch?

Hi, On Thu, 16 Feb 2023 at 11:54, Leo Famulari wrote: > On Tue, Feb 14, 2023 at 10:22:07PM +0100, Josselin Poiret wrote: >> The inferior that's used in 'build-aux/cuirass/evaluate.scm' is built >> from the current check-out by first adding the checkout to the store and >> then building it the

Re: Guix release broken without substitutes on ungrafted openssl

Hi, On Wed, 15 Feb 2023 at 13:33, Leo Famulari wrote: > I'd guess it's happened 4 times in the last several years. > > It's one of several reasons that rebuilding old Guix releases actually > approaches being a Hard Problem. The issue is from the impure world. ;-) Well, yeah it would probably

’inherit’ and list-dependent (was Re: branch master updated: gnu: emacs: Add TREE_SITTER_GRAMMAR_PATH support.)

Hi, On dim., 12 févr. 2023 at 01:14, Ludovic Courtès wrote: >> There is an idea to update guix refresh --list-dependent to handle the >> case with inherited packages as well. WDYT? > > Unfortunately, it’s not possible because inheritance info isn’t > available at run time. Well, with the

Re: [Internship][Discussion] Do we want to run our own internship program?

Hi Gábor, On lun., 13 févr. 2023 at 21:13, Gábor Boskovits wrote: > So, the question is: do we want to run our own? By “our own”, do you mean something like “Guix Summer of Code”? Or whatever other season. :-) Similar to: https://summer.nixos.org/

Release (was Re: Discussion notes on releases and branches)

Hi, Thanks Andreas for the notes. :-) On Thu, 09 Feb 2023 at 13:19, Andreas Enge wrote: > - A release schedule for a release every 4 to 6 months sounds > reasonable. > - Mathieu, Simon, Julien and Andreas volunteer to be members of a release Ludo was volunteer for helping, if I remember

Re: Google Summer of Code?

Hi, On Fri, 10 Feb 2023 at 09:05, Gábor Boskovits wrote: > I will contact Jose, pass a link to the ideas side and check how to proceed > and if we can help somehow. Cool! Cross-finger for: February 22 - 18:00 UTC List of accepted mentoring organizations published

Re: Licence of the Guix blog posts

Hi, On Fri, 02 Dec 2022 at 17:06, zimoun wrote: > On Mon, 28 Nov 2022 at 18:22, Ludovic Courtès wrote: > >> Simon, what do you think about emailing the authors of the “10 years of >> stories” post asking if they agree with the licensing? :-) No rush, >> though the sooner the more likely we

Re: Google Summer of Code?

Hi, On mer., 08 févr. 2023 at 10:03, Ludovic Courtès wrote: > Jose Marchesi applied to have GNU participate as an umbrella > organization in GSoC: > > https://lists.gnu.org/archive/html/summer-of-code/2023-02/msg0.html The deadline for applying as our own* organization is over (February

Re: git-fetch without a hash

Hi, On dim., 05 févr. 2023 at 18:44, b...@bokr.com wrote: >> From my understanding, we could have something like, >> >> (sha256 (no-hash)) >> >> where ’no-hash’ would return a string, say >> "" or whatever else >> that would satisfy

Re: Getting tree-sitter grammars in Guix

Hi, On sam., 04 févr. 2023 at 20:27, Demis Balbach wrote: > My understanding is that I need to provide emacs with tree-sitter > support as an input for this to work, which I did, but it'll fail with > > --8<---cut here---start->8--- > Debugger entered--Lisp

Re: emacs packaging: do we need to pull existing dependencies ?

Hi, On mer., 01 févr. 2023 at 08:44, Cayetano Santos wrote: > Say for example emacs-org-roam@2.2.2: it requires emacs-org 9.4, > which is not specified in the package definition, meaning we always > pull the latest available. Do we have to, provided that emacs > releases with org ? Maybe there

Re: 01/02: packages: Adjust 'generate-package-cache' for Guile 3.0.9.

Hi Ludo, On Mon, 30 Jan 2023 at 22:52, Ludovic Courtès wrote: >> What are the performances about this change? Does it improve the >> generation of the cache? Faster or slower? >> >> Or the resulting cache, is it larger or smaller? > > The resulting cache is unchanged and build time should be

Re: Proposed changes to the commit policy (#59513)

Hi, On Mon, 30 Jan 2023 at 22:03, Christopher Baines wrote: > In the past and currently to some extent, it's been possible to move > very quickly without comprimising on quality. However, my feeling on > this is that if we want to have quality support for non x86_64-linux > architectures,

Re: valgrind

Hi Andreas, On Wed, 25 Jan 2023 at 14:16, Andreas Enge wrote: > Am Wed, Jan 25, 2023 at 01:39:29PM +0100 schrieb zimoun: >> Is the package ’valgrind/interactive’ accessible with valgrind@3.17 >> needed? Indeed, maybe it could be dropped, especially if it is broken >> for some use-case. > > I

Re: guix package updates review: app team?

Hi, On ven., 27 janv. 2023 at 14:19, Andy Tai wrote: > Hi, currently Guix has teams of reviewers for different types of > packages. For example, changes to R packages and emacs seem to be > reviewed quickly. However, recently, patches for updating more > general application packages (octave,

Re: CLI flag to ignore guix channel

Hi, On sam., 28 janv. 2023 at 20:55, Csepp wrote: >>> guix import crate behemoth-rust-package-foo -r --ignore-channel=guixrus [...] >> guix time-machine -C path/to/channels-wo-guixrus.scm \ >> -- import crate behemoth-rust-package-foo -r > How fast is that? If new commits come

Re: Unexpected error with #~(modify-phases

Hi Tobias, On Fri, 27 Jan 2023 at 20:03, Tobias Geerinckx-Rice wrote: > > You're probably missing (guix gexp), and the 'replace' syntax fails before > Guile ever gets to expanding the '#~'. Damned! Stupid me! I missed the obvious. Thanks for the quick help. :-) Cheerw, simon

Unexpected error with #~(modify-phases

Hi, Reviewing #59997 [1], there is something I am missing. Using the V2, all works as expected. But when I just modify with this diff: --8<---cut here---start->8--- 1 file changed, 2 insertions(+), 2 deletions(-) gnu/packages/minimacy.scm | 4 ++-- modified

Re: guix lint false positives and RFC patch

Hi, On sam., 12 nov. 2022 at 17:54, Vagrant Cascadian wrote: > On 2022-11-05, Ludovic Courtès wrote: >> Vagrant Cascadian skribis: >>> From bfa13fdd3616839883e50efbbc05fb132610ce67 Mon Sep 17 00:00:00 2001 >>> From: Vagrant Cascadian >>> Date: Wed, 2 Nov 2022 19:56:12 -0700 >>> Subject: [PATCH

Re: CLI flag to ignore guix channel

Hi, On jeu., 03 nov. 2022 at 21:51, jgart wrote: > I'd like a CLI flag to be able to ignore channels. > > Where should I look if I'd like to implement something like this? > > I prefer not to edit and comment out channels in ~/.config/guix/channels.scm > > I'd prefer to do the following > >

Re: Struggling to write Dissecting Guix, Part 2

Hi, On jeu., 26 janv. 2023 at 21:03, b...@bokr.com wrote: > Indeed, Simon Peyton Jones is tops. If I might, I would recommend « Build Systems à la Carte » [1]. It provides a framework to deal with various build system; Guix being one, see Table 2. 1:

Re: tree-sitter grammars for emacs memo

Hi, Thanks for the tricks. :-) On Sun, 04 Dec 2022 at 19:04, Murad Mamedov wrote: > create mode 100644 src/emacs-module.h > create mode 100644 src/tree-sitter-lang.in > > diff --git a/src/emacs-module.h b/src/emacs-module.h > new file mode 100644 > index 000..1185c06 > --- /dev/null >

Re: purpose of GnuTLS versions

Hi, On Thu, 26 Jan 2023 at 00:12, Jack Hill wrote: > It seems to me that the `gnutls` variable should refer to the latest > "stable" release, and the `gnutls-latest` variable to latest "next" > release. Does that make sense? What am I missing? This means a core-updates change – so next

01/02: packages: Adjust 'generate-package-cache' for Guile 3.0.9.

Hi, Commit ba1b61a72d56600e7c6f9c490129e95ab9ba0c9e reads: --8<---cut here---start->8--- packages: Adjust 'generate-package-cache' for Guile 3.0.9. * gnu/packages.scm (generate-package-cache): Adjust for Guile 3.0.9. [...] @@ -442,10 +443,15 @@ (define exp

Translation files .gmo and packaging

Hi, The submission patch#61010 [1] relies on the release archive: https://github.com/ice-wm/icewm/releases/download/3.3.0/icewm-3.3.0.tar.lz and this archive contains the generated .gmo files. However, these files are not in the archive:

Re: Struggling to write Dissecting Guix, Part 2

Hi, On Wed, 25 Jan 2023 at 16:54, Wojtek Kosior via "Development of GNU Guix and the GNU System distribution." wrote: > here[1] is > the paper (written by someone at Microsoft, lol) where I found this > approach. > [1]

Re: FOSDEM’s coming!

Hi Tobias, On lun., 23 janv. 2023 at 19:30, Tobias Platen wrote: > Unfortunately I'll won't make it to Brussels this year, so I ask if > there is an IRC chat or recording of talks at the fringe event. The fringe event will not be recorded, sadly. Some people will be on IRC I guess. :-)

Re: Proposed changes to the commit policy (#59513)

Hi Andreas, On Sun, 22 Jan 2023 at 18:18, Andreas Enge wrote: > So I tried it once, and find the hassle offputting. It feels like doubling > the effort - after doing the real work, I need to get back to it a week > later and more or less go through the motions again (rebase the commit > and

Getting tree-sitter grammars in Guix

Hi, On Tue, 10 Jan 2023 at 18:29, Demis Balbach wrote: > Hello, I was wondering what the "correct" way would be to get grammars > for the tree-sitter library available in Guix when using tree-sitter > with Emacs 29+. This raises a question about the bootstrap. >From my understanding, the

Re: Proposed changes to the commit policy (#59513)

Hi Andreas, On mer., 18 janv. 2023 at 12:23, Andreas Enge wrote: > as a quick concrete question: Do simple package updates still count as > trivial, or do they need to go through the patches mailing list? > I intended to update pari-gp from 2.15.1 to 2.15.2, as usual by checking > that all

Re: Packages grow, no longer fit on a 

Hi, On mer., 18 janv. 2023 at 21:44, Paul Jewell via "Development of GNU Guix and the GNU System distribution." wrote: > - does anyone actually install from a CD these days? > - Can an ISO be bigger than a CD then be installed on a memory stick? Florian reported an example in [1], quoting:

Re: Packages grow, no longer fit on a 

Hi, On jeu., 19 janv. 2023 at 15:32, Ludovic Courtès wrote: >> I also wonder how much of the space is taken by debug output. Would >> making graft derivations substitutable help? > > Graft derivations are not substitutable because it’s usually faster to > “build” them locally than to download

Re: Packages grow, no longer fit on a 

Hi Ludo, On jeu., 19 janv. 2023 at 15:14, Ludovic Courtès wrote: > To me, Emacs is still Emacs, with or without libgccjit. Of course JIT > is an improvement, I don’t deny that, but what I mean is that I still > use Emacs for the very same activities. This is even more true for > polkit,

Re: Time for ocaml-xzy.scm and reorganizing OCaml packages?

Hi Julien, On Wed, 11 Jan 2023 at 21:20, Julien Lepiller wrote: > Sounds good to me. Are you planning to work on a patch? Yes, I am planning to work on it. :-) But maybe not in one go. Since it is a boring task, I plan to do something similar as I did when “janitoring“ R packages from

Re: Packages grow, no longer fit on a 

Hi, On sam., 14 janv. 2023 at 23:07, Ludovic Courtès wrote: > --8<---cut here---start->8--- > $ guix time-machine --commit=v1.2.0 -- size emacs [...] > total: 859.7 MiB > $ guix time-machine --commit=v1.3.0 -- size emacs [...] > total: 880.5 MiB > $

Re: properties for default version? (was bug#60200: Incompatibilities between gcc-toolchain and R packages)

Hi Ludo, On mar., 17 janv. 2023 at 17:09, Ludovic Courtès wrote: >> For other cases, such issue is avoided by appending the suffix -next to >> package name; as with ghc-next, python-numpy-next, emacs-next, etc. >> >> Personally, I find the -next trick useful because the package name >> reflects

Re: Org 9.6: void org-element--cache-active-p on fresh

Hi, On lun., 16 janv. 2023 at 20:43, zimoun wrote: > Now consider: > > $ guix shell -C emacs-minimal emacs-org -E TERM \ >-- emacs -q -l config.el \ >--eval "(require 'org-element)" \ >-f org-agenda > > Then press ’m’ and type:

Re: IDEA: Give Our Generations a Name

Hi, On Mon, 16 Jan 2023 at 23:40, "jgart" wrote: > What do you think if we would be able to give past generations a name? Well, I think this would be difficult. And personally I do not have the use case. However, be able to locally Git tag and use this tag with “guix time-machine” will be

Re: Proposed (guix platforms) lookup procedures API change

Hi Maxim, On ven., 13 janv. 2023 at 22:23, Maxim Cournoyer wrote: > There is currently a proposed change [0] to modify the behavior of the > LOOKUP-PLATFORM-BY-SYSTEM, LOOKUP-PLATFORM-BY-TARGET and > LOOKUP-PLATFORM-BY-TARGET-OR-SYSTEM public procedures from (guix > platforms) that would have

Re: bug#58813: can't substitute etc/teams.scm command as doc suggests

Hi Maxim, On mer., 11 janv. 2023 at 22:00, Maxim Cournoyer wrote: > It's developed as part of U-Boot and available at > https://u-boot.readthedocs.io/en/latest/develop/patman.html. It's > generated from the same sources as the info manual from > u-boot-documentation referenced above. Oh

Re: Command consistency: suggestion

Hi, On Mon, 09 Jan 2023 at 12:22, Paul Jewell via "Development of GNU Guix and the GNU System distribution." wrote: > guix package --list-generations > > and > > guix system list-generations > > guix package has everything as an flag, but guix system (and guix home) > uses the concept of

properties for default version? (was bug#60200: Incompatibilities between gcc-toolchain and R packages)

Hi, As bug#60200 [1], the issue is one that many of us often hit: packages with several versions and when the highest one is not the default. Other said, build systems use some version for compiler and tools but Guix can also offer more recent versions for these very same compilers and tools.

<    1   2   3   4   5   >