Re: Towards reproducibly Jupyter notebooks with Guix-Jupyter

zimoun writes: >> No, at least not explicitly. My goal is reproducing computations from >> the past, so I need to re-animate old manifest files. These could of >> course contain references to inferior-packages, so they could be >> multi-commit, but this is not my focus. > > But does it fit with t

Re: 'core-updates' Q4 2019

Hi Marius, Marius Bakke writes: > Timothy Sample writes: > >> [1] It’s not obvious, but if you edit the GDM configuration file >> generation code in “gnu/services/xorg.scm”, you can enable debug output >> for GDM. The debug output is usually extremely helpful! > > Could that be exposed as a to

Re: Getting build information in to the Guix Data Service (draft patch)

Ludovic Courtès writes: > Christopher Baines skribis: > >> This is what I've currently tried to implement. The patch I'll send adds >> two new tables to the Cuirass database, one to store events relating to >> builds (like it being scheduled, or succeeding), and another to store >> the ids of e

Re: 'core-updates' Q4 2019

Timothy Sample writes: > [1] It’s not obvious, but if you edit the GDM configuration file > generation code in “gnu/services/xorg.scm”, you can enable debug output > for GDM. The debug output is usually extremely helpful! Could that be exposed as a toggle in the service configuration? signatu

Re: KDE frameworks are outdated

Hartmut Goebel writes: > Am 18.10.19 um 20:57 schrieb Marius Bakke: >> It probably does. Really just looking for someone to try it and send in >> the patches. :-) > > I'll have a look at this. Excellent, thank you! signature.asc Description: PGP signature

State of ungoogled-chromium in Guix

Hello Guix, Version 78 of the upstream Chromium project was released yesterday, with the usual amount of security fixes: https://chromereleases.googleblog.com/2019/10/stable-channel-update-for-desktop_22.html Unfortunately the 'ungoogled-chromium' variant in Guix is still stuck on version 76. T

Re: Preliminary IceCat 68.2 package

Hi Andy, Andy Wingo writes: > I know that's not very reassuring, but if you're looking for a quick > workaround, running your "make -jN" in a loop 5 times or something may > be good enough. Thanks again for suggesting this. I was stuck, and you got me unstuck, and for that I'm very grateful. I

Re: gnu: python-pytest: Update to 5.2.1.

Tanguy Le Carrour writes: > Hi Guix! > > I'm working on updating python-pytest and… not everything is going as > smoothly as I was expecting! :-( > > Pytest 5.2.1 depends on Pluggy >=0.12.0… which depends on > importlib-metadata. But when I had the latter as a propagated-input to > python-pluggy,

Re: Help needed packaging rust-cbindgen, a dependency of IceCat 68

Ludovic Courtès writes: > Hi Mark, > > Mark H Weaver skribis: > >> I have good news and bad news. The good news is that thanks to the >> heroic efforts of Amin Bandali , a recently appointed >> co-maintainer of GNU IceCat, there now exists a preliminary version of >> IceCat 68 that builds succe

Re: gnu: python: Update to 3.8.0.

Hartmut Goebel writes: > Am 23.10.19 um 11:11 schrieb Tanguy Le Carrour: >> Python 3.8.0 was released on October the 14th [1]. >> What would be the proper way to package it for Guix?! Add a new public >> variable `python-3.8` and make `python-3` and `python` point to it? Would >> `python-3.7` go

Re: Questions about packaging

Tanguy Le Carrour writes: > Le 10/18, Marius Bakke a écrit : >> On the next 'core-updates' cycle, Pytest 5 will then become the default, >> and we will have to fix all packages that does not work with that >> version :-) > > I guess those broken packages will show up as "red" in Cuirass!? > Would

Profiles/manifests-related command line interface enhancements

Hi! While playing with multiple profiles and manifests and discussing with a couple of people in the community, I collected a number of usability issues with Guix when it comes to managing multiple profiles and dealing with manifests. Ideas for new features, more or less from most important to le

Re: Stackage LTS 14 (was: Adding Purescript)

Ricardo Wurmus writes: > Hi Timothy, > >> One of the things I want to do this time is to do the upgrade in one >> mega commit. I’m pretty sure that some of the commits last time had >> inconsistent package sets, which is not ideal. I’m not sure how to >> avoid that upgrading one package at a ti

Cuirass exposes evaluation logs

Hello Guix! Good news everyone! Cuirass now keeps logs of evaluations and exposes them over HTTP! So when an evaluation fails, you can now click on the red cross to peek at the log. More generally, you can view an evaluation log by going to: https://ci.guix.gnu.org/eval/ID/log/raw where ID

Re: Reproducible grub-install

On Mon, Oct 21, 2019 at 04:30:21PM +0200, Miguel Arruga Vivas wrote: > Hi, everybody! > > After taking a deeper look into our (guix's) grub installation > procedure, I have the thought that it could be a neat idea to make the > boot directory an actual derivation instead something of the global > s

Re: Towards reproducibly Jupyter notebooks with Guix-Jupyter

On Wed, 23 Oct 2019 at 14:15, Konrad Hinsen wrote: > > Hi Simon, > > > I am not sure to understand everything, so my questions are: > > > > - Do you consider binaries coming from multiple commits and/or > > multiple channels? > > No, at least not explicitly. My goal is reproducing computations fr

Re: Fwd: Running individual system tests

Daniel Schäfer writes: > Is there maybe an interpreted mode? Yes, if you don’t compile the Scheme files they will be interpreted. It’s much slower than using the compiled Guix. -- Ricardo

Re: gnu: python-pytest: Update to 5.2.1.

Hi Efraim, Efraim Flashner writes: [...] > I assume python-importlib-metadata only needs python-pytest for running > the test suite. We have a couple of python libraries that have > '-bootstrap' added to the end. You could try making a > python-importlib-metadata-bootstrap which doesn't use pyt

Re: KDE frameworks are outdated

Am 18.10.19 um 20:57 schrieb Marius Bakke: > It probably does. Really just looking for someone to try it and send in > the patches. :-) I'll have a look at this. -- Regards Hartmut Goebel | Hartmut Goebel | h.goe...@crazy-compilers.com | | www.crazy-compilers.com | compi

Re: Preliminary IceCat 68.2 package

Hi Andy, Andy Wingo wrote: >> I'd be very grateful for help debugging these failures or finding a >> workaround. > > I don't know what this is, but at work I have to build Firefox a lot, > and sometimes the rust bits die in the middle of compilation. Is it a > resource exhaustion issue? I am no

Re: Getting build information in to the Guix Data Service (draft patch)

Hi Chris, Christopher Baines skribis: > This is what I've currently tried to implement. The patch I'll send adds > two new tables to the Cuirass database, one to store events relating to > builds (like it being scheduled, or succeeding), and another to store > the ids of events which haven't yet

Re: We need your feedback of the documentation videos!

On Wed, 23 Oct 2019 06:49:38 -0500 pelzflorian (Florian Pelz) wrote > On Tue, Oct 22, 2019 at 08:59:40PM +0200, pelzflorian (Florian Pelz) wrote: > > Thank you for your review. I will resend tomorrow with these changes. > > I would like to include Joshua’s >

Re: 06/06: gnu: Add weasyprint.

Hi Hartmut, Hartmut Goebel skribis: > Am 22.10.19 um 23:51 schrieb Tobias Geerinckx-Rice: >> Ludo: >>> You forgot to push the patch.  Could you add it? >> >> I've reverted this patch for now to keep master relatively happy. >> > Ups, soory. New package including the patch in > 77e0cebcadc8b96613

Re: Preliminary IceCat 68.2 package

Heya Mark :) On Wed 23 Oct 2019 12:32, Mark H Weaver writes: > I wrote: >> * Many earlier attempts to build it have failed due to non-deterministic >> failures in the build system, possibly due to a bug in the Cargo tool. >> I'm not sure how much luck was involved in my successful build. Yo

Re: gnu: python: Update to 3.8.0.

Am 23.10.19 um 14:51 schrieb Tanguy Le Carrour: > Is it possible to package it and make it available, but not to make it > the default python? When would be a good time to make the switch?! Yes, you can add a package "python-3.8". You might even test if all packages still pass the test when you m

Re: Running individual system tests

Hi, On Wed, 23 Oct 2019 14:03:20 +0200 Daniel Schäfer wrote: > And I have to do it, whenever I want to run any system test, or build an > in-tree package (which I'm going to submit for inclusion)? Yes, in the end you have to do that. I agree that that's a very high bar of entry (for example c

Re: gnu: python: Update to 3.8.0.

Hi Hartmut! Le 10/23, Hartmut Goebel a écrit : > Am 23.10.19 um 11:11 schrieb Tanguy Le Carrour: > > Python 3.8.0 was released on October the 14th [1]. > > What would be the proper way to package it for Guix?! Add a new public > > variable `python-3.8` and make `python-3` and `python` point to it

Re: Towards reproducibly Jupyter notebooks with Guix-Jupyter

Hi Simon, > I am not sure to understand everything, so my questions are: > > - Do you consider binaries coming from multiple commits and/or > multiple channels? No, at least not explicitly. My goal is reproducing computations from the past, so I need to re-animate old manifest files. These could

Re: Fwd: Running individual system tests

So you're saying, I have to run ``` ./bootstrap ./configure make ./pre-inst-env guix build my-new-package ``` which builds the daemon, and compiles all Guile modules? And I have to do it, whenever I want to run any system test, or build an in-tree package (which I'm going to submit for inclusio

Re: We need your feedback of the documentation videos!

On Tue, Oct 22, 2019 at 08:59:40PM +0200, pelzflorian (Florian Pelz) wrote: > Thank you for your review. I will resend tomorrow with these changes. I would like to include Joshua’s before moving screenshots. Shall I? Regards,

Re: gnu: python: Update to 3.8.0.

Am 23.10.19 um 11:11 schrieb Tanguy Le Carrour: > Python 3.8.0 was released on October the 14th [1]. > What would be the proper way to package it for Guix?! Add a new public > variable `python-3.8` and make `python-3` and `python` point to it? Would > `python-3.7` go away?! I'm not convinced to ma

Re: Preliminary IceCat 68.2 package

I wrote: > * Many earlier attempts to build it have failed due to non-deterministic > failures in the build system, possibly due to a bug in the Cargo tool. > I'm not sure how much luck was involved in my successful build. Your > mileage may vary. Having now done a few more test builds, I'm

Re: Towards reproducibly Jupyter notebooks with Guix-Jupyter

Hi Konrad, I am not sure to understand everything, so my questions are: - Do you consider binaries coming from multiple commits and/or multiple channels? - Why splits the channel file and the manifest file? I am thinking to improve the DSL of the manifest file. All the best, simon

Re: Help needed packaging rust-cbindgen, a dependency of IceCat 68

Efraim Flashner writes: > It's pushed. I think this should be a good motivator to work on a > wip-rust branch to merge the crates into crates-io and convert the > others over. Thanks, Efraim! Mark

Re: The cookbook is on-line!

By the way, the original tutorial was published here in Org format: https://ambrevar.xyz/guix-packaging/index.html So it's possible to export it to texi with Org. That should save some work. -- Pierre Neidhardt https://ambrevar.xyz/ signature.asc Description: PGP signature

Re: The cookbook is on-line!

Understood, thanks! -- Pierre Neidhardt https://ambrevar.xyz/ signature.asc Description: PGP signature

Re: Towards reproducibly Jupyter notebooks with Guix-Jupyter

Hi Ludo, > Did you define an environment along the lines of the example at > ? > > If so, this should behave in exactly the same way as a “regular” ‘guix > environment’, so I’m not sure where the issues regarding access to the > tty co

gnu: python: Update to 3.8.0.

Hi Guix! Python 3.8.0 was released on October the 14th [1]. What would be the proper way to package it for Guix?! Add a new public variable `python-3.8` and make `python-3` and `python` point to it? Would `python-3.7` go away?! [1]: https://pythoninsider.blogspot.com/2019/10/python-380-is-now-ava

Preliminary IceCat 68.2 package

Hello fellow Guix, I was finally able to successfully build a working IceCat-68.2 package. The 'wip-icecat-68' branch on Savannah contains this preliminary work. A few caveats: * IceCat 68 has not yet been released upstream. This is very much a work-in-progress, and does not currently meet th

Re: 06/06: gnu: Add weasyprint.

Am 22.10.19 um 23:51 schrieb Tobias Geerinckx-Rice: > Ludo: >> You forgot to push the patch.  Could you add it? > > I've reverted this patch for now to keep master relatively happy. > Ups, soory. New package including the patch in 77e0cebcadc8b96613832e1554e326d48e20f72f -- Regards Hartmut Goebel

Re: gnu: python-pytest: Update to 5.2.1.

On Wed, Oct 23, 2019 at 09:22:43AM +0200, Tanguy Le Carrour wrote: > Hi Guix! > > I'm working on updating python-pytest and… not everything is going as > smoothly as I was expecting! :-( > > Pytest 5.2.1 depends on Pluggy >=0.12.0… which depends on > importlib-metadata. But when I had the latter

Re: Help needed packaging rust-cbindgen, a dependency of IceCat 68

It's pushed. I think this should be a good motivator to work on a wip-rust branch to merge the crates into crates-io and convert the others over. -- Efraim Flashner אפרים פלשנר GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351 Confidentiality cannot be guaranteed on emails sent o

Re: 'core-updates' Q4 2019

On Tue, Oct 22, 2019 at 11:07:06PM -0400, Timothy Sample wrote: > There’s a “glib-or-gtk?” flag for the Meson build system. Setting it to > “#t” in the “mutter” package makes GDM and GNOME work in a VM. Thank you for investigating, I suppose this fixes your issue. webkitgtk failed again for me th

Re: SLiM graphical login manager and keyboard layout

Hi Ludovic, Thanks for taking the time to clarify all this! … but I have to confess that I had to read it several times! ^_^' Le 10/22, Ludovic Courtès a écrit : > Tanguy Le Carrour skribis: > > Le 10/18, Diego Nicola Barbato a écrit : > >> Tanguy Le Carrour writes: > >> >(service

gnu: python-pytest: Update to 5.2.1.

Hi Guix! I'm working on updating python-pytest and… not everything is going as smoothly as I was expecting! :-( Pytest 5.2.1 depends on Pluggy >=0.12.0… which depends on importlib-metadata. But when I had the latter as a propagated-input to python-pluggy, then `guix build` gets stuck. diff -