Re: Commit access

Hi! Miguel Ángel Arruga Vivas skribis: > I'm happy to announce with this message my access to the repository and > the key I'll use to sign the commits. This text has been signed with > it, which has the following information and fingerprint: > > pub rsa3072 2020-09-09 [SC] [expires:

Re: Update on the timeline for the release v1.2.

Julien Lepiller skribis: > Le 21 octobre 2020 11:57:48 GMT-04:00, "Ludovic Courtès" a > écrit : [...] >>Yeah we could also branch on the 26th and cherry-pick harmless changes >>from ‘master’, so people can still have fun on ‘master’. >> >>Mathieu, Marius, Maxim, Tobias: thoughts? > >

Re: Update on the timeline for the release v1.2.

On Thu, 22 Oct 2020 at 00:16, Ludovic Courtès wrote: > > Wouldn't that mess up with guix's authentication mechanism? If we branch > > v1.2 early, our release will have no forward path to master, so all our > > users will get an error when running guix pull. > > No, that’s fine as long as

Re: Update on the timeline for the release v1.2.

On Thu, 22 Oct 2020 at 00:16, Ludovic Courtès wrote: > It’s the same as running ‘guix pull --branch=staging’ today for > instance. Maybe I am doing wrong: --8<---cut here---start->8--- $ guix describe Generation 94 Oct 20 2020 18:28:42(current) guix

Re: Manual PDF and translation (modular texlive?)

Ludovic Courtès writes: > Ricardo Wurmus skribis: > >> I can now build the French and the German manuals in this environment: >> >> guix environment --pure guix --ad-hoc -e '(begin (use-modules (gnu >> packages tex))(texlive-union (list texlive-epsf texlive-fonts-ec >> texlive-amsfonts

Re: Update on the timeline for the release v1.2.

Julien Lepiller writes: > Le 21 octobre 2020 11:57:48 GMT-04:00, "Ludovic Courtès" a > écrit : >>zimoun skribis: >> > The proposed coming timeline is: > > - freeze starting the Oct. 26th > - last round for testing all over the week > - unfreeze the Oct. 29th and

Re: Update on the timeline for the release v1.2.

Le 21 octobre 2020 11:57:48 GMT-04:00, "Ludovic Courtès" a écrit : >zimoun skribis: > >>> > The proposed coming timeline is: >>> > >>> > - freeze starting the Oct. 26th >>> > - last round for testing all over the week >>> > - unfreeze the Oct. 29th and then create the branch >>> > -

New Swedish PO file for 'guix' (version 1.2.0-pre2)

Hello, gentle maintainer. This is a message from the Translation Project robot. A revised PO file for textual domain 'guix' has been submitted by the Swedish team of translators. The file is available at: https://translationproject.org/latest/guix/sv.po (We can arrange things so that in

Re: Using #true and #false everywhere?

Hi, Ricardo Wurmus skribis: > Mark H Weaver writes: > >> Ricardo Wurmus writes: >> >>> I think it’s very ugly that we still need to end phases with #T, even >>> though build systems don’t care any more. The only thing that aborts a >>> build phase now is an exception. >> >> I would be glad

Re: ‘xdg-mime-database’ profile hook is slow

Hi Ludo, On Wed, 21 Oct 2020 at 11:49, Ludovic Courtès wrote: > It’s worse on a cold cache: Well, a lot of Guix operations are really slow on cold cache. ;-) > And it’s probably worse on spinning disks? What timings do you get? Some timings are provided by bug report #44053 which tracks

Re: Inkscape export errors

On Tue, 20 Oct 2020 17:51:09 + Ekaitz Zarraga wrote: > I made some research. Yours is passing the "import inkex" line > because it's able to load `lxml`. The first question I'd like to make > is: why? No real idea. I can only note that my store contains python-lxml-4.4.2 and

Re: Outreachy Applicant: An Introduction

Hi Magali, On Wed, 21 Oct 2020 at 01:08, Magali Lemes wrote: >>> I wanted to share my progress with you. This last week I submitted my first >>> patch ever. There were a few minor mistakes in it, so I had to fix them and >>> submit again. It was a great opportunity for me to learn some new Git

Re: Release v1.2 timetable

Hello! zimoun skribis: > For that we need a Guile-Git release, which could be made anytime now. Mathieu, do you want to take care of it? If not, I can do it. > Done! :-) Thanks, Ludo’.

Re: Data Services: use cases

Hi, Pierre Neidhardt skribis: > In particular, the "Version From To" table is hard to grasp to a > newcomer. I’m not a newcomer but I find it limpid: I think it immediately shows that this is about version changes and when they happened. Maybe it could be decluttered a bit by using shorter

Re: Data Services: use cases

Hi Ludo! Ludovic Courtès writes: > I’m not a newcomer but I find it limpid: I think it immediately shows > that this is about version changes and when they happened. What about the 4 points I listed? I find that they make a case for what could be improved in terms of clarity. Cheers! --

‘xdg-mime-database’ profile hook is slow

Hi, Joshua Branson skribis: > I don't want to complain (because I'm probably not going to be able to > fix any issues that I spot), but it does seem to take a while for me to > install packages, at least the XDG mime step. It's not a huge issue for > me. I just realize that installing

Re: Data Services: use cases

Hi Ludo, On Wed, 21 Oct 2020 at 11:27, Ludovic Courtès wrote: > Pierre Neidhardt skribis: > > > In particular, the "Version From To" table is hard to grasp to a > > newcomer. > > I’m not a newcomer but I find it limpid: I think it immediately shows > that this is about version changes and when

Re: File search progress: database review and question on triggers

Pierre Neidhardt skribis: > Ludovic Courtès writes: > >> It first tries ‘query-path-info’, which succeeds if the store item is >> available and contains info about its size, references, and so on. >> >> When ‘query-path-info’ fails, it falls back to >> ‘query-substitutable-path-info’, which

Re: Using #true and #false everywhere?

Hi, Andreas Enge skribis: > on the bikeshedding front: I find #true and #false confusing, since > everything I see on the Scheme language seems to use #t and #f. What material are you referring to? SICP & co.? Unfortunately, “the” Scheme language is more of a concept; SICP targets R5RS I

Re: Using #true and #false everywhere?

Hi, Andreas Enge skribis: > On Fri, Oct 16, 2020 at 12:38:23PM +0200, Ludovic Courtès wrote: >> As discussed on IRC recently, several of us think that using “#true” and >> “#false” instead of “#t” and “#f” throughout or documentation and code >> would probably make it easier for newcomers to

Size of package 'guix'

Hi, On Wed, 21 Oct 2020 at 11:12, Ludovic Courtès wrote: > > guix->libx11: graphviz@2.42.3 > > guix->fribidi: graphviz@2.42.3 > > guix->graphviz: graphviz@2.42.3 > > guix->cairo: graphviz@2.42.3 > > guix->pixman: graphviz@2.42.3 > > guix->libjpeg-turbo: graphviz@2.42.3 > > guix->pango:

Re: Using #true and #false everywhere?

Hi Mark, Mark H Weaver writes: > Ricardo Wurmus writes: > >> I think it’s very ugly that we still need to end phases with #T, even >> though build systems don’t care any more. The only thing that aborts a >> build phase now is an exception. > > I would be glad if this were the case, but I

Re: Releasing guix binary in Docker format too?

Hi, zimoun skribis: > Back to this. Since it would be nice to try to release (somewhere?) > an experimental guix Docker image. Among the issues to be addressed is whether we can push to DockerHub with free software only (there was a discussion recently on IRC about a tool to do that, but I

Re: Using #true and #false everywhere?

Hi, zimoun skribis: > I do not have a strong opinion but I am still perplex if it really > simplifies because all the material around about Scheme and especially > the Guile manual still uses #t/#f and not #true/#false. For example, > > $ guix repl > GNU Guile 3.0.4 > Copyright (C) 1995-2020

Re: Racket packages / build system

Hi! "Bonface M. K." skribis: > Thanks for the notes. I've skimmed through them > and they seem sensible. I'll look at how other > build systems are written as a first step, then > get my hands wet. Would be great to see that happen! There’s also a Chicken build system under review currently:

Re: Releasing guix binary in Docker format too?

Hi, (adding Jelle because of 'skopeo' :-)) On Wed, 21 Oct 2020 at 11:12, Ludovic Courtès wrote: > > Back to this. Since it would be nice to try to release (somewhere?) > > an experimental guix Docker image. > > Among the issues to be addressed is whether we can push to DockerHub > with free

Re: Inkscape export errors

On Wednesday, October 21, 2020 2:03 PM, Ludovic Courtès wrote: > Egun on, Saluton Ludo, > > You would then need to include this variant of ‘inkscape’ alongside > ‘python’ so that ~/.guix-profile/etc/profile sets ‘PYTHONPATH’ > accordingly. > > A better fix would be to use ‘wrap-program’ to

[PATCH 1/2] services: guix: Make /etc/guix/acl really declarative by default.

Fixes . Reported by Maxim Cournoyer . * gnu/services/base.scm (substitute-key-authorization): Symlink DEFAULT-ACL to /etc/guix/acl unconditionally. Add code to optionally back up /etc/guix/acl if it was possibly modified by hand. * doc/guix.texi (Base Services):

[PATCH 2/2] doc: Add "Getting Substitutes from Other Servers" section.

* doc/guix.texi (Getting Substitutes from Other Servers): New node. (Invoking guix-daemon): Add cross-reference. (Substitute Server Authorization): Clarify that this is unnecessary on Guix System. (Invoking guix publish): Add cross-reference. --- doc/guix.texi | 122

Re: Update on the timeline for the release v1.2.

Dear, On Wed, 21 Oct 2020 at 14:44, Ludovic Courtès wrote: > > - staging is freezed > > Do we want to merge ‘staging’ before the release, though? >From my point of view, it would be really nice. Marius or any "merger" (Jakub, Efraim, Brett), is it reasonable? WDYT? > > The proposed coming

Re: File search progress: database review and question on triggers

Ludovic Courtès writes: > A client-side approach (not involving guix-daemon) would be more readily > usable, though some of the questions above remain open. I'd also prefer to stick to the client side. But how can I trigger an event when a package gets built? Maybe we could hook into specific

Re: Manual PDF and translation (modular texlive?)

Hi, Ricardo Wurmus skribis: > I can now build the French and the German manuals in this environment: > > guix environment --pure guix --ad-hoc -e '(begin (use-modules (gnu > packages tex))(texlive-union (list texlive-epsf texlive-fonts-ec > texlive-amsfonts texlive-tex-texinfo)))' > >

Re: Update on the timeline for the release v1.2.

Hi! zimoun skribis: > The date Nov. 6th seems a more reasonable target as a release date. Works for me! > From what I am reading, > > - the tests of the installer are work ongoing > - important packages updates are also ongoing (Julia, OCaml, ...) > - fixes > - manual typos and various

Re: Racket packages / build system

Ludovic Courtès writes: > Hi! > > "Bonface M. K." skribis: > >> Thanks for the notes. I've skimmed through them >> and they seem sensible. I'll look at how other >> build systems are written as a first step, then >> get my hands wet. > > Would be great to see that happen! There’s also a

Re: Localization of language names

Hi, Miguel Ángel Arruga Vivas skribis: > From 69b8d919a802d72fca218b7dfd9e7719c4711544 Mon Sep 17 00:00:00 2001 > From: =?UTF-8?q?Miguel=20=C3=81ngel=20Arruga=20Vivas?= > > Date: Fri, 16 Oct 2020 15:02:00 +0200 > Subject: [PATCH] installer: Call setlocale after init gettext. > > *

Re: Inkscape export errors

Egun on, Ekaitz Zarraga skribis: > I'm experiencing export errors in Inkscape 1.0.1 on several formats like DXF > or Optimized SVG. I'm getting the following error: > > ``` > Traceback (most recent call last): > File "output_scour.py", line 8, in > import inkex > File >

New French PO file for 'guix' (version 1.2.0-pre2)

Hello, gentle maintainer. This is a message from the Translation Project robot. A revised PO file for textual domain 'guix' has been submitted by the French team of translators. The file is available at: https://translationproject.org/latest/guix/fr.po (We can arrange things so that in

Re: Importing package-overlay-for-Nix - How?

Hi, Danny Milosavljevic skribis: > How do I use it > > guix import nix > > in order to import those packages? This importer has bitrot; it could probably be salvaged with some effort from someone knowledgeable about today’s Nix (i.e., not me :-)): https://issues.guix.gnu.org/32339

Re: Using #true and #false everywhere?

On Wed, Oct 21, 2020 at 11:59:40AM +0200, Ludovic Courtès wrote: > What material are you referring to? SICP & co.? I simply used my favourite search engine with something such as scheme language boolean In my case the first link is to the racket manual:

Re: Using #true and #false everywhere?

On Wed, 2020-10-21 at 11:59 +0200, Ludovic Courtès wrote: > Hi, > > Andreas Enge skribis: > > > on the bikeshedding front: I find #true and #false confusing, since > > everything I see on the Scheme language seems to use #t and #f. > > What material are you referring to?  SICP & co.? > Sorry

Re: Size of package 'guix'

zimoun skribis: > On Wed, 21 Oct 2020 at 11:12, Ludovic Courtès wrote: > >> > guix->libx11: graphviz@2.42.3 >> > guix->fribidi: graphviz@2.42.3 >> > guix->graphviz: graphviz@2.42.3 >> > guix->cairo: graphviz@2.42.3 >> > guix->pixman: graphviz@2.42.3 >> > guix->libjpeg-turbo: graphviz@2.42.3 >>

Re: Update on the timeline for the release v1.2.

zimoun skribis: >> > The proposed coming timeline is: >> > >> > - freeze starting the Oct. 26th >> > - last round for testing all over the week >> > - unfreeze the Oct. 29th and then create the branch >> > - minor bug fixes and all the papeword around (NEWS, blog, etc.) >> > - release Nov.

Re: [PATCH 1/2] services: guix: Make /etc/guix/acl really declarative by default.

On 2020-10-21, Ludovic Courtès wrote: > diff --git a/doc/guix.texi b/doc/guix.texi > index c161012da5..50d2d9a730 100644 > --- a/doc/guix.texi > +++ b/doc/guix.texi ... > @@ -14583,6 +14598,27 @@ Whether to use substitutes. > @item @code{substitute-urls} (default: @code{%default-substitute-urls})

Re: Size of package 'guix'

On Wed, 21 Oct 2020 at 17:44, Ludovic Courtès wrote: > >> These are build-time dependencies so that should only be a problem when > >> one has to build ‘guix’ from source. > > > > What do you mean by "build 'guix' from source"? > > I mean that it doesn’t matter that ‘guix’ depends on ‘graphviz’

Re: Inkscape export errors

Hi, I think I managed to solve the issues. All the issues I had were coming from the extensions' dependencies not being added to Inkscape's. With the following changes it's supposed to work (it worked in my machine lol). I had to package scour too, because it wasn't packaged. I have a question

Re: Releasing guix binary in Docker format too?

Hi, zimoun skribis: > The tool is 'skopeo' and packaged in Guix. > > However, push to DockerHub requires an account (by Guix project) which > requires... probably non-free JS, at least once. Hmm OK. Users of Docker wouldn’t have to create an account and run the non-free JS, so this is

Re: Using #true and #false everywhere?

Andreas Enge skribis: > On Wed, Oct 21, 2020 at 11:59:40AM +0200, Ludovic Courtès wrote: >> What material are you referring to? SICP & co.? > > I simply used my favourite search engine with something such as >scheme language boolean OK. Note that it’s a different topic though: someone

Re: Guix Europe yearly assembly minutes

Hi Tanguy! Tanguy Le Carrour skribis: > Sorry if my question is a bit silly, but… what exactly is "Guix Europe"? > > I read the statute [1], but could not find an "official" web page for > the association, only a thread with a dead link [2] and page on a totally > unrelated > website [3]. > >

Re: Inkscape export errors

Saluton! Ekaitz Zarraga skribis: >> You would then need to include this variant of ‘inkscape’ alongside >> ‘python’ so that ~/.guix-profile/etc/profile sets ‘PYTHONPATH’ >> accordingly. >> >> A better fix would be to use ‘wrap-program’ to wrap ‘inkscape’ such that >> ‘PYTHONPATH’ always points