Re: New ‘guix pull’ - guile-sqlite3 problem

2018-07-17 Thread Chris Marusich
Pjotr Prins writes: > So I updated guix pull multiple times :) and both daemon and client > are at > > guix (GNU Guix) ecba50bb79a49b317c4b1e718f4732b36438227f > > Now I am creating an environment to build the source tree with > > env -i /bin/bash --login --noprofile --norc > guix

Re: Running the full MariaDB test suite

2018-07-17 Thread Leo Famulari
On Tue, Jul 17, 2018 at 10:04:42PM +0200, Marius Bakke wrote: > Hello! > > So far our MariaDB package has only run some very lightweight tests. > 10.1.34 flipped a switch that runs the entire "MTR" test suite. > > After patching /bin/ls and /bin/sh, and fixing a couple of failures that > showed

Running the full MariaDB test suite

2018-07-17 Thread Marius Bakke
Hello! So far our MariaDB package has only run some very lightweight tests. 10.1.34 flipped a switch that runs the entire "MTR" test suite. After patching /bin/ls and /bin/sh, and fixing a couple of failures that showed up after about 4 hours each, the most recent attempt took eight hours during

Re: linux 4.17.7 not suitable for i386

2018-07-17 Thread Brett Gilio
Leo Famulari writes: FYI, the latest stable Linux release (4.17.7) is not suitable for i386 (i686-linux) systems. Quoting Greg Kroah-Hartman: "NOTE, this kernel release is broken for i386 systems. If you are running such a machine, do NOT update to this release, you will not be able to

Re: GSoC: Adding a web interface similar to the Hydra web interface

2018-07-17 Thread Clément Lassieur
Ricardo Wurmus writes: > You can download a copy of the Cuirass database as it is used on > berlin.guixsd.org, one of the build farms of the Guix project. I have > copied it here: > > http://bootstrappable.org/cuirass.db > > It is 12G(!), which indicates that Cuirass adds way too many

Re: linux 4.17.7 not suitable for i386

2018-07-17 Thread Leo Famulari
On Tue, Jul 17, 2018 at 11:36:08AM -0400, Leo Famulari wrote: > Quoting Greg Kroah-Hartman: > > "I did this release anyway with this known problem as there is a fix in > here for x86-64 systems that was nasty to track down and was affecting > people. Given that the huge majority of systems are

Re: linux 4.17.7 not suitable for i386

2018-07-17 Thread Mark H Weaver
Leo Famulari writes: > FYI, the latest stable Linux release (4.17.7) is not suitable for i386 > (i686-linux) systems. Quoting Greg Kroah-Hartman: > > "NOTE, this kernel release is broken for i386 systems. If you are > running such a machine, do NOT update to this release, you will not be > able

linux 4.17.7 not suitable for i386

2018-07-17 Thread Leo Famulari
FYI, the latest stable Linux release (4.17.7) is not suitable for i386 (i686-linux) systems. Quoting Greg Kroah-Hartman: "NOTE, this kernel release is broken for i386 systems. If you are running such a machine, do NOT update to this release, you will not be able to boot properly. I did this

Re: Extracting a reachability path out of a (package) DAG

2018-07-17 Thread Gábor Boskovits
Björn Höfling ezt írta (időpont: 2018. júl. 17., K, 12:32): > On Tue, 17 Jul 2018 08:24:24 + > Nils Gillmann wrote: > > > > To add to this idea: > > abyayala$ nix why-depends --help > > Usage: nix why-depends ... > > > > Summary: show why a package has another package in its closure. > >

Re: MATE 1.20

2018-07-17 Thread Ricardo Wurmus
Nils Gillmann writes: > Would anyone like to take on the task of updating MATE desktop in Guix? > > -> https://mate-desktop.org/blog/2018-02-07-mate-1-20-released/ > > If no one signals working on it next month, I'll put it on my TODO > list for August. I’m already working on the GNOME

Re: Extracting a reachability path out of a (package) DAG

2018-07-17 Thread Björn Höfling
On Tue, 17 Jul 2018 08:24:24 + Nils Gillmann wrote: > To add to this idea: > abyayala$ nix why-depends --help > Usage: nix why-depends ... > > Summary: show why a package has another package in its closure. [..] > Would it be useful to have a guix package subcommand which replicates >

Re: Extracting a reachability path out of a (package) DAG

2018-07-17 Thread Björn Höfling
On Tue, 17 Jul 2018 10:22:02 +0200 Pierre Neidhardt wrote: > > gvpr -f markpath.g -a "ex 64168128 64167936" < > > qt-thing/qt.package.dot : qt-acw.dot > > Can you explain the two magic numbers? I'm not sure what you mean > with "seed nodes". The numbers are the node names from the graph

Re: Extracting a reachability path out of a (package) DAG

2018-07-17 Thread Nils Gillmann
Björn Höfling transcribed 74K bytes: > Hi Guix, > > we have this nice `guix graph` tool which outputs DAGs of the packages > (or even derivations,bags, ...). This is cool if you look at simple > packages like the "hello" package with little to no dependencies. If > you look at "real" packages

Re: Extracting a reachability path out of a (package) DAG

2018-07-17 Thread Pierre Neidhardt
> gvpr -f markpath.g -a "ex 64168128 64167936" < qt-thing/qt.package.dot > : qt-acw.dot Can you explain the two magic numbers? I'm not sure what you mean with "seed nodes". That said, I think it's a great idea. Could we go even more interactive with an interface that filter the graph "live",

MATE 1.20

2018-07-17 Thread Nils Gillmann
Would anyone like to take on the task of updating MATE desktop in Guix? -> https://mate-desktop.org/blog/2018-02-07-mate-1-20-released/ If no one signals working on it next month, I'll put it on my TODO list for August. Thanks

Extracting a reachability path out of a (package) DAG

2018-07-17 Thread Björn Höfling
Hi Guix, we have this nice `guix graph` tool which outputs DAGs of the packages (or even derivations,bags, ...). This is cool if you look at simple packages like the "hello" package with little to no dependencies. If you look at "real" packages like qt or maven the information is just