virtualenv isn't reproducible! (by default)

[jgart]

Thought this might be interesting to Guix packagers interested in Python:

https://www.youtube.com/watch?v=mgJiCnqzYlI

https://redirect.invidious.io/search?q=virtualenv%20isn%27t%20reproducible!%20(by%20default)%20(intermediate)%20anthony%20explains

The Guix Days! (FOSDEM 2023)

[Simon Tournier]

Dear all,

We are organizing the Guix Days, satellite to FOSDEM.  Guix Days are 2
days for hacking and discussion open to everybody interested in Guix,
from core developer to newcomer.

When?  The 2 days right before FOSDEM:
  Thursday and Friday, February 2nd and 3rd, 2023.

Where?  The usual place in Brussels:
  Institute of Cultural Affairs (ICAB), Rue Amedee Lynen 8, 1210 Brussels

More details here:

https://libreplanet.org/wiki/FOSDEM2023-guix-days

Guix Days are free to attend!  We can only receive up to 40 people for
the Guix Days (previously, we had 35) and we need to reserve the
catering.  So, please sign up on the LibrePlanet link above (add your
name as Participants) if you intend to come.  If we happen to have too
many people to attend the meeting, the first 40 who signed up have a
guaranteed entry.  If you don't want to subscribe to the wiki, you can
send a request to Pjotr, Manolis or myself.

See some past editions:

https://libreplanet.org/wiki/Group:Guix


FOSDEM is an awesome free software conference and almost everyone who
goes once keeps coming because there is something for everyone.  The
conference is back as a physical conference.  Please check the devroom
“Declarative and Minimalistic Computing”.  Among many other devrooms
[1].

https://fosdem.org/2023/schedule/track/declarative_and_minimalistic_computing/

See some last years amazing FOSDEM program:

  https://archive.fosdem.org/2020/schedule
  https://archive.fosdem.org/2019/schedule


Hope to see you there!

1: 

Re: Guile-Gcrypt 0.4.0 released

[Jonathan Brielmaier]

On 03.12.22 23:45, Vagrant Cascadian wrote:

On 2022-12-01, Ludovic Courtès wrote:

I’m pleased to announce Guile-Gcrypt version 0.4.0:

   git clone https://notabug.org/cwebber/guile-gcrypt.git
   cd guile-gcrypt
   git checkout v0.4.0  # or 425554d4327eeeb60c39e3d4a1b7bc5e36b63953
   git tag -v v0.4.0


FWIW, I updated guile-gcrypt to 0.4.0 in Debian experimental and updated
to guix 1.4.0rc1 in Debian experimental using guile-gcrypt 0.4.0, and it
seemed to go fine so far...


Those being on openSUSE Tumbleweed can enjoy 0.4.0 as well:
https://build.opensuse.org/request/show/1039343

Guix is also built against the updated version, no problems so far :)

~Jonathan

Re: File search

[(]

On Tue Dec 6, 2022 at 10:01 AM GMT, Ludovic Courtès wrote:
> The implementation based on manifests can of course miss packages, so
> it’s a tradeoff.  Purely local indexing will only find packages you
> already have anyway, so eventually we’ll need a second mode that would
> download a database.

Someone on IRC suggested that we use GraphQL to allow us to request
that a substitute server search for files in a database constructed
using all the packages that have been built.

I suggest something like this:

  # on the client
  when [built a package derivation]
[add files to local database]

  when [user ran guix find]
if [send find request to substitute server] didn't work
  [search through local database]
[display result]

  # on the substitute server
  when [built a package definition]
[add files to local database]

  when [user sent find request]
[search through local database]
[reply with result]

-- (


signature.asc
Description: PGP signature

Re: GDB is Unable to find libthread_db

[Attila Lendvai]

thanks for looking into it Ludo!

looking again at the error message, it actually means that dbus was unable to 
start the daemon (but the daemon's error output was swallowed by the 
architecture).


$ 
/gnu/store/6i4gi0sfbssv9g6yd28jgnb18219zk7h-gpaste-42.1/libexec/gpaste/gpaste-daemon

(gpaste-daemon:14604): GLib-GIO-CRITICAL **: 12:44:11.196: 
g_settings_schema_source_lookup: assertion 'source != NULL' failed
Segmentation fault


it was enough of a hint for me to fix gpaste:

https://issues.guix.gnu.org/59863

looking at the code, i have no idea why/how it was not crashing for you.


as for the GDB issue:

> $ guix shell gdb guile guile:debug -- gdb --args guile

surprisingly enough, the above fails for me:

$ guix shell gdb guile guile:debug -- gdb --args guile
GNU gdb (GDB) 12.1
[...]
Reading symbols from guile...
(No debugging symbols found in guile)
(gdb) r
Starting program: /gnu/store/dyw73lrvdnffwsp5idrcznyn0k0fzywz-profile/bin/guile
warning: File 
"/gnu/store/qlmpcy5zi84m6dikq3fnx5dz38qpczlc-guile-3.0.8/lib/libguile-3.0.so.1.5.0-gdb.scm"
 auto-loading has been declined by your `auto-load safe-path' set to 
"$debugdir:$datadir/auto-load".
To enable execution of this file add
[...]
warning: Unable to find libthread_db matching inferior's thread library, thread 
debugging will not be available.


maybe you have something installed in your profile that i don't? it's not a 
roadblock anymore, though.


> One situation where it doesn’t work is if the process being debugged is
> in a namespace different from that of GDB, but that doesn’t seem to be
> what you did, so I’m not sure.


i don't even know how to do that, so hopefully i'm not doing that. :)

--
• attila lendvai
• PGP: 963F 5D5F 45C7 DFCD 0A39
--
“Here is my secret. It is very simple: it is only with the heart that one can 
see rightly. What is essential is invisible to the eye.”
— Antoine de Saint-Exupery (1900–1944)

Re: Release progress, week 8

[Ludovic Courtès]

Mathieu Othacehe  skribis:

> - fail2ban-extension (https://ci.guix.gnu.org/build/215447/details)

Fixed:

  a420b4f34e services: fail2ban: Start server in the foreground.
  a508b5c778 services: fail2ban: Remove unnecessary Shepherd 'modules' field.
  e45c83c397 services: fail2ban: 'stop' returns #f when the dameon is stopped.

(Oops, a typo.)

Ludo’.

Re: [EXT] Re: Emacs integration for 'guix shell'

[Thompson, David]

Hey Philip,

Just a little update for this old thread.  Around the time of your
email the Emacs package was modified to enable native compilation.
Unfortunately, it made Emacs unusable on my computer which stopped my
Emacs experimentation for a bit.  I'm past that now, thankfully.

On Sat, Oct 1, 2022 at 10:38 AM Philip Kaludercic  wrote:
>
> I wrote about it in some more detail here:
> https://amodernist.com/texts/emacs-guix.html, but the post didn't
> attract much attention.

Thanks for writing that blog post!  It was very helpful.  I now have
buffer-env handling 'guix shell' integration and it works like a
charm.

- Dave

Re: Release progress, week 8

[Ludovic Courtès]

Hi!

Mathieu Othacehe  skribis:

> I noticed that we have failing tests on the version-1.4.0-tests
> specification.
>
> - docker-system (https://ci.guix.gnu.org/build/215380/details)

Fixed:

  6232959311 tests: docker-system: Increase image size.
  f59aa79ca3 system: vm: Non-volatile 'run-vm.sh' creates a CoW image.

> - prosody (https://ci.guix.gnu.org/build/215424/details)

I suspect Freetalk (the client) might be at fault.  I tried fiddling
with it, using Loudmouth 1.5.3, removing Kerberos support, but that
didn’t have any effect.

Can someone more familiar with Prosody/XMPP take a look?

> - fail2ban-extension (https://ci.guix.gnu.org/build/215447/details)
>
> that only fails on Berlin.

I’ll take a look.

> There is also an issue with the system images. The following images are
> failing on Berlin:
>
> - novena-barebones-raw-image (https://ci.guix.gnu.org/build/215363/details)
> - pine64-barebones-raw-image (https://ci.guix.gnu.org/build/215361/details)
> - pinebook-pro-barebones-raw-image 
> (https://ci.guix.gnu.org/build/215362/details)
>
> It seems that those failures are caused by an issue during info-reader
> build. I cannot reproduce it locally though.

Should be fixed now:

  fe563a87ad gnu: texinfo, info-reader: Do not run tests when cross-compiling.

> Having an RC2 with all the tests passing and images buildable could be
> nice.

Right.

Yesterday on IRC we discussed an installer crash received at
dump.guix.gnu.org.  Did you or will you have time to look into it?

I should be able to prepare and upload RC2 sometime between Thursday and
Sunday.  Now’s the time to report and fix installation problems!

Ludo’.

December update on automating patch testing and qa.guix.gnu.org

[Christopher Baines]

Hey!

I send out the last update around a month ago [1], there was also a
thread jgart started [2].

1: https://lists.gnu.org/archive/html/guix-devel/2022-11/msg00048.html
2: https://lists.gnu.org/archive/html/guix-devel/2022-11/msg00134.html

As a reminder, patches sent to guix-patches now undergo some automated
testing. You can see the progress and results of this on qa.guix.gnu.org
[3].

3: https://qa.guix.gnu.org/patches

## Recent progress

I think the biggest step forward recently has been separating "blocked"
and "unknown" builds out, as that makes it clearer when the testing has
finished. This was made possible by the Guix Data Service incrementally
working out which builds are blocked as events come in, and storing this
in a way that's easy to query efficiently.

The powerpc64le-linux and i586-gnu (Hurd) builds for patches are also
now enqueued, although due to a lack of build capacity for these
systems, the results aren't factored in to the issue status yet.

I think one of the things that came up in this thread [2] is that
there's more communicating to do about qa.guix.gnu.org. I've now merged
and deployed the update to Mumi that includes a patch from Arun to start
displaying badges from qa.guix.gnu.org, so hopefully that'll help to
link up the two services.

## Next steps

The README contains a big TODO list [4], but I'll highlight some things
here.

4: https://git.cbaines.net/guix/qa-frontpage/about/

I've also made progress on moving the Git repository on to Savannah,
there's a ticket open here now [5].

5: https://savannah.nongnu.org/support/?110790

Writing a proper service for the qa-frontpage is also on my TODO list,
that will mean it won't be running in a screen session on bayfront.

I think the most important medium term goal though is to work on testing
branches (like staging, core-updates, ...). Because they're generally
more complicated changes compared to things sent to guix-patches, I
think that's where the benefits on automatically testing the changes
will be the greatest.

## How to get involved

If you're doing any patch review, consider looking at qa.guix.gnu.org!
Even if you aren't able to push patches, it can be really useful to
review them and provide feedback. There's a review checklist at the
bottom of the QA pages.

If you're looking at getting any branches merged, it would be really
useful to hear about that so the functionality for testing those
branches can be worked on.

Also, there's a whole lot to work on in the qa-frontpage codebase, so if
you're interested in that, I'm more than happy to try and help.

If you've got any comments or questions, please let me know!

Thanks,

Chris


signature.asc
Description: PGP signature

Re: File search

[zimoun]

Hi,

On Tue, 06 Dec 2022 at 11:01, Ludovic Courtès  wrote:
> "Antoine R. Dumont (@ardumont)" 
> skribis:
>
>> Please, find enclosed the latest implementation as a patch (somewhat vcs
>> code ;). I've edited commits to mark Ludo as author with his
>> started/amended implementations first [0] (that should be in the patch).

That’s cool!


> Also going forward we’ll need a schema version, as in:
>
> --8<---cut here---start->8---
> create table SchemaVersion (
> version integer not null;
> );
> --8<---cut here---end--->8---

Well, using plain SQLite as backend will make more complicated the way
to query.  For instance, “guix index output:doc gtk”.  Maybe it could be
worth to use guile-xapian as backend.

Cheers,
simon

Re: GMP GCC C++ Hurd cross-build failure on core-updates

[zamfofex]

I realized it might also be useful to include GMP’s ‘config.log’ with 
‘--keep-failed’, so I’ll send it as an attachment in this email. Thank you in 
advance once again!This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

It was created by GNU MP configure 6.2.1, which was
generated by GNU Autoconf 2.69.  Invocation command line was

  $ ./configure CC_FOR_BUILD=gcc 
CONFIG_SHELL=/gnu/store/bphb827vv6jrja5wyp3gj4yn1f96bm99-bash-minimal-5.1.16/bin/bash
 SHELL=/gnu/store/bphb827vv6jrja5wyp3gj4yn1f96bm99-bash-minimal-5.1.16/bin/bash 
--prefix=/gnu/store/08x48463r73vvmxkwidy0rsvhhbdxs53-gmp-6.2.1 
--enable-fast-install --build=x86_64-unknown-linux-gnu --host=i586-pc-gnu 
--enable-fat --enable-cxx

## - ##
## Platform. ##
## - ##

hostname = localhost
uname -m = x86_64
uname -r = 6.0.7-gnu
uname -s = Linux
uname -v = #1 SMP PREEMPT_DYNAMIC 1

/usr/bin/uname -p = unknown
/bin/uname -X = unknown

/bin/arch  = unknown
/usr/bin/arch -k   = unknown
/usr/convex/getsysinfo = unknown
/usr/bin/hostinfo  = unknown
/bin/machine   = unknown
/usr/bin/oslevel   = unknown
/bin/universe  = unknown

PATH: /gnu/store/glj8i8s8gf3w0ich3f23ng7dp3z21yv2-m4-1.4.19/bin
PATH: 
/gnu/store/51c9khy6lz5ibv7nsd3i3whdbj8ks33s-gcc-cross-i586-pc-gnu-11.3.0/bin
PATH: 
/gnu/store/4arnacpgpn0ypdxdr587vbdg86lpyy7k-binutils-cross-i586-pc-gnu-2.38/bin
PATH: /gnu/store/wr7wgs3mbalc0zma63wwkq11ynsyjqpr-tar-1.34/bin
PATH: /gnu/store/p6qk3h2ymdhigj6gx3c65c7wc2k0q8i7-gzip-1.12/bin
PATH: /gnu/store/kbkd0m8fjb0px9pz13gwrllradkcmzja-bzip2-1.0.8/bin
PATH: /gnu/store/a4ryn93hagc26fp8xsdkyi94d7hpjyzl-xz-5.2.8/bin
PATH: /gnu/store/igl8d889yz56bl26giwn1v7b36zx4r7y-file-5.43/bin
PATH: /gnu/store/2gk12xwwb1yv18x7xd5bbh5pnvng8pm8-diffutils-3.8/bin
PATH: /gnu/store/8hfx2m8lginhlz06ilh82mmnj8kfz7dg-patch-2.7.6/bin
PATH: /gnu/store/0vx0mpdzc0a66gb4n35aazmzzi6s26pk-findutils-4.9.0/bin
PATH: /gnu/store/q709bgiyj34rzz6ljhy6zcanwb1cfp2a-gawk-5.2.1/bin
PATH: /gnu/store/kkwqizhba1z78n5006l3bvmafjd9vgg3-sed-4.8/bin
PATH: /gnu/store/k09y6lv4vmwv0iaxma1ss0mq31khmcb3-grep-3.8/bin
PATH: /gnu/store/3n73jz0nyskrq3i14j904kqdcny4vfxb-coreutils-9.1/bin
PATH: /gnu/store/37js5dn8pgv7palgyv4yhjldfpkmwccr-make-4.3/bin
PATH: /gnu/store/bphb827vv6jrja5wyp3gj4yn1f96bm99-bash-minimal-5.1.16/bin
PATH: /gnu/store/p5yx9jliryy5bb73smhja1qvzmcm4a1l-ld-wrapper-0/bin
PATH: /gnu/store/7yy335j70z4aygpcfdbx3xq3m1bm0057-binutils-2.38/bin
PATH: /gnu/store/cyjvqbhmfl4rmdqj870lckvd8ajj5lvk-gcc-11.3.0/bin
PATH: /gnu/store/jjmhkbm1k35fqjai897c5pb6bgl20k2d-glibc-2.35/bin
PATH: /gnu/store/jjmhkbm1k35fqjai897c5pb6bgl20k2d-glibc-2.35/sbin


## --- ##
## Core tests. ##
## --- ##

configure:3056: checking build system type
configure:3070: result: x86_64-unknown-linux-gnu
configure:3090: checking host system type
configure:3103: result: i586-pc-gnu
configure:3140: checking for a BSD-compatible install
configure:3208: result: 
/gnu/store/3n73jz0nyskrq3i14j904kqdcny4vfxb-coreutils-9.1/bin/install -c
configure:3219: checking whether build environment is sane
configure:3274: result: yes
configure:: checking for i586-pc-gnu-strip
configure:3349: found 
/gnu/store/4arnacpgpn0ypdxdr587vbdg86lpyy7k-binutils-cross-i586-pc-gnu-2.38/bin/i586-pc-gnu-strip
configure:3360: result: i586-pc-gnu-strip
configure:3425: checking for a thread-safe mkdir -p
configure:3464: result: 
/gnu/store/3n73jz0nyskrq3i14j904kqdcny4vfxb-coreutils-9.1/bin/mkdir -p
configure:3471: checking for gawk
configure:3487: found 
/gnu/store/q709bgiyj34rzz6ljhy6zcanwb1cfp2a-gawk-5.2.1/bin/gawk
configure:3498: result: gawk
configure:3509: checking whether make sets $(MAKE)
configure:3535: result: no
configure:3560: checking whether make supports nested variables
configure:3577: result: yes
configure:3706: checking whether to enable maintainer-specific portions of 
Makefiles
configure:3715: result: no
User:
ABI=
CC=
CFLAGS=(unset)
CPPFLAGS=(unset)
MPN_PATH=
GMP:
abilist=32
cclist=gcc icc cc
configure:5869: i586-pc-gnu-gcc 2>&1 | grep xlc >/dev/null
configure:5872: $? = 1
configure:5926: checking compiler i586-pc-gnu-gcc -m32 -O2 -pedantic 
-fomit-frame-pointer 
Test compile: 
configure:5940: i586-pc-gnu-gcc -m32 -O2 -pedantic -fomit-frame-pointer  
conftest.c >&5
configure:5943: $? = 0
Test compile: function pointer return
configure:5994: i586-pc-gnu-gcc -m32 -O2 -pedantic -fomit-frame-pointer  
conftest.c >&5
configure:5997: $? = 0
Test compile: cmov instruction
configure:6050: i586-pc-gnu-gcc -m32 -O2 -pedantic -fomit-frame-pointer  
conftest.c >&5
configure:6053: $? = 0
Test compile: double -> ulong conversion
configure:6107: i586-pc-gnu-gcc -m32 -O2 -pedantic -fomit-frame-pointer  
conftest.c >&5
configure:6110: $? = 0
Test compile: double negation
configure:6162: i586-pc-gnu-gcc -m32 -O2 -pedantic -fomit-frame-pointer  
conftest.c >&5
configure:6165: $? = 0
Test compile: double -> float conversion

Re: GNU Guix 1.4.0rc1 available for testing!

[Ludovic Courtès]

Hi Florian,

"pelzflorian (Florian Pelz)"  skribis:

> * [PATCH v2 2/3] install: Add missing e2fsprogs utility.
>   
>   Otherwise manual installation does not work as advertised.

Done.

> * [version 1.4.0rc1] reconfigure fails
>   
>   Otherwise users cannot update Guix System once installed
>   unless they take manual action.

Done.

> * [version 1.4.0rc1] install.sh script should authorize bordeaux
>   
>   Otherwise especially ARM users get far less substitutes
>   unless they take manual action.

Almost done.  :-)

Thanks for your feedback!

Ludo’.

Re: Drafting a Guix blog post on the FHS container

[Ludovic Courtès]

Hello!

John Kehayias  skribis:

> One question: what is appropriate or recommended for examples concerning 
> things like pre-built binaries? As an example, I had tested the FHS container 
> by running the Siril appimage, which has since been packaged for Guix (nice 
> work!). There are ones that I don't see that happening for anytime soon, like 
> an Electron-based app. Something like VSCodium is very popular, free (as in 
> freedom and I believe the FSDG sense), but just not something you can package 
> fully from source due to JavaScript as I understand it. It runs in the FHS 
> container.

A good example might be a free application not currently packaged in
Guix, for example due to being full of JavaScript, or nightly builds as
you wrote provided by an upstream project.

> Here is a current (rough!) draft. For the ease of plain text email I've 
> exported from the org source to text with some light edits:

Note that the blog takes Markdown¹, but hopefully the Org-to-markdown
export works well.

¹ https://git.savannah.gnu.org/cgit/guix/guix-artwork.git/tree/website/posts

The post looks great to me!  I have minor suggestions below:

> GNU Guix is different from most other GNU/Linux distributions and
> perhaps nowhere is that more obvious than the organization of the
> filesystem: Guix does not conform to the [File Hierarchy Standard]
> (FHS). In practical terms, this means there is no global `/lib'

It’s “Filesystem Hierarchy Standard”.

> To that end, we've [recently added] a new option for Guix containers,
> `--emulate-fhs' (or `-F'). This will set up an environment in the

Perhaps s/Guix containers/`guix shell`/ and add a few words about what
‘guix shell --container’ does (you can link to the manual or blog post).

> container that follows FHS expectations, so that libraries are visible
> in `/lib' in the container, as an example. Additionally, for the more
> technically-minded, the [`glibc' used in this container] will read from
> a global cache in `/etc/ld.so.cache' contrary to the behavior in [Guix
> otherwise].

Since the ld.so.cache issue is more involved (compared to simply having
/lib and /bin), maybe you can move it after the “ls /bin” example?

> Contrast that with `/bin' on a Guix system:
> ,
>  ls /bin -la
> `
>
> lrwxrwxrwx  1  root  root   61  Dec  3  16:37  sh  ->  
> /gnu/store/d99ykvj3axzzidygsmdmzxah4lvxd6hw-bash-5.1.8/bin/sh

You can show ‘ls /lib’ too.  :-)

Actually you can use or get inspiration from this animated GIF if you
like:

  https://web.fdn.fr/~lcourtes/tmp/guix-shell-fhs.gif

> useful. For example, there may be software that is free and conforms to
> the FSDG Guix follows, yet is not feasible to be [packaged] by our

s/FSDG/Free System Distribution Guidelines (FSDG)/

Thanks,
Ludo’.

Re: File search

[Ludovic Courtès]

Howdy!

"Antoine R. Dumont (@ardumont)" 
skribis:

> Please, find enclosed the latest implementation as a patch (somewhat vcs
> code ;). I've edited commits to mark Ludo as author with his
> started/amended implementations first [0] (that should be in the patch).

Nice!

> For information, I extracted some number from runs to compare our
> iterations (see the org-file attachment). The first iteration being
> "extracts packages from the store" and the second one "extracts packages
> from the system manifest". Those runs happened both on a guixified
> debian host and a raw guix host (more packages).

So we went from 413s to 11s (on the Guix System node) for only 6% fewer
files in the latter case?  Do I get that right?  That’s pretty cool.

The implementation based on manifests can of course miss packages, so
it’s a tradeoff.  Purely local indexing will only find packages you
already have anyway, so eventually we’ll need a second mode that would
download a database.

BTW, I noticed outputs are not properly handled so far, as in this
example:

--8<---cut here---start->8---
$ GUIX_EXTENSIONS_PATH=$HOME/tmp/guix-index guix index search git-send-email
git@2.38.1   
/gnu/store/g3lgyzr749l76qma7srycclgsm0f78iq-git-2.38.1-send-email/libexec/git-core/git-send-email
git@2.37.1   
/gnu/store/n3hkzz5ydm0qm1c2jja2pwy2v19mq1k0-git-2.37.1-send-email/libexec/git-core/git-send-email
--8<---cut here---end--->8---

It should instead show “git@2.38.1:send-email”.  We probably need an
‘output’ field in the ‘Packages’ table.

Also going forward we’ll need a schema version, as in:

--8<---cut here---start->8---
create table SchemaVersion (
version integer not null;
);
--8<---cut here---end--->8---

so that the tool can upgrade or discard databases that have the wrong
version.

Oh, and progress bars too.  And a pony.  :-)

Thanks for your work!

Ludo’.

Re: Licence of the Guix blog posts

[Guillaume Le Vaillant]

Ludovic Courtès  skribis:

> You might remember that I started long ago asking people who had
> contributed to the blog whether they would agree to licensing their work
> under CC-BY-SA 4.0 and GFDL version 1.3 or later, with no Invariant
> Sections, no Front-Cover Texts, and no Back-Cover Texts¹.
>
> I did not get replies from Danny Milosavljevic and Laura Lazzati²;
> everyone else agreed publicly.
>
> In the meantime, we got a new blog post³ with lots of contributors,
> thanks to Simon’s work.  Unfortunately I think we did not discuss the
> licensing terms.
>
> Therefore, I propose to apply the following patch, which leaves out a
> couple of posts as “unlicensed”.  From there on, we’ll have consistent
> free licensing by default.
>
> Thoughts?
>
> 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 are to get an answer.
>
> Ludo’.

Hi Ludo,

I wrote a paragraph for the "10 years of stories behind Guix" post, and
I agree with the proposed licensing.


signature.asc
Description: PGP signature