gdb-7.7 test failures

I've done some experimenting on my systems, and the pattern seems to be this: * On multiprocessor machines with #:parallel-tests? enabled, gdb-7.7 successfully builds. * On single-processor machines, or with #:parallel-tests? disabled, the build always fails because "make check" fails. There

Daemon update: rebuild!

I made another update of the ‘nix-upstream’ submodule, so make sure to run: git pull # should update ‘nix-upstream’ along with the rest ( cd nix ; ./sync-with-upstream ) make clean make make check Please report any problems! Ludo’.

Re: [PATCH] union: Ensure that the output is always a directory

Mark H Weaver skribis: > From 6c8582bc41c8935b8e9d63146595e87d9b92fa95 Mon Sep 17 00:00:00 2001 > From: Mark H Weaver > Date: Thu, 3 Apr 2014 17:49:20 -0400 > Subject: [PATCH] union: Ensure that the output is always a directory. > MIME-Version: 1.0 > Content-Type: text/plain; charset=UTF-8 > Con

[PATCH] union: Ensure that the output is always a directory

l...@gnu.org (Ludovic Courtès) writes: > I stumbled upon this bug: building a profile with a single package > fails, because the new union.scm makes the profile directory a symlink > to that package, which then prevents the creation of the ‘manifest’ > file: Indeed! Here's a patch that fixes tha

Re: Support for signed substitutes pushed

On Thu, Apr 03, 2014 at 09:48:55PM +0200, Ludovic Courtès wrote: > Andreas Enge skribis: > > Excellent work, thank you! > You’re welcome. :-) Does it work for you? Definitely, otherwise I would have complained ;-) Andreas

Re: [PATCH] union: Rewrite to be faster; handle symlink/directory conflicts

Mark H Weaver skribis: > From 3f503705098745ddd54251a46b5634e78b209e5f Mon Sep 17 00:00:00 2001 > From: Mark H Weaver > Date: Fri, 28 Mar 2014 03:54:01 -0400 > Subject: [PATCH] union: Rewrite to be faster; handle symlink/directory > conflicts. > > * guix/build/union.scm: Rewrite; only 'file=?'

Re: Python 3 test failures

Mark H Weaver skribis: > l...@gnu.org (Ludovic Courtès) writes: > >> Mark H Weaver skribis: >> >>> == >>> ERROR: test_fork (test.test_pty.PtyTest) >>> -- >>> Tr

Re: Support for signed substitutes pushed

Andreas Enge skribis: > Excellent work, thank you! You’re welcome. :-) Does it work for you? > On Sun, Mar 30, 2014 at 11:54:10PM +0200, Ludovic Courtès wrote: >> Please run ‘make check’, try it, and report any problems. Note that >> commit bf59c06 adds the public key used to sign substitute

Re: Can unprivileged users corrupt the store with bad tarballs?

Mark H Weaver skribis: > I was thinking about the security implications of giving out shell > access to one of my systems running Guix. > > When I ask guix-daemon to build package 'foo', it will use as an input > the source for package 'foo', usually a tarball. If the tarball is > already in the

Can unprivileged users corrupt the store with bad tarballs?

I was thinking about the security implications of giving out shell access to one of my systems running Guix. When I ask guix-daemon to build package 'foo', it will use as an input the source for package 'foo', usually a tarball. If the tarball is already in the store, it won't download it again,

Re: Why is this build considered a failure by hydra?

On Thu, Apr 03, 2014 at 05:14:42PM +0200, Ludovic Courtès wrote: > I’ve just restarted it, and now it looks as succeeding. This is something I have occasionally observed before, even without offload- ing: A build log shows that everything worked well, and the build fails. Restarting the build solv

Re: Python 3 test failures

l...@gnu.org (Ludovic Courtès) writes: > Mark H Weaver skribis: > >> == >> ERROR: test_fork (test.test_pty.PtyTest) >> -- >> Traceback (most recent call last): >

Re: Support for signed substitutes pushed

Excellent work, thank you! On Sun, Mar 30, 2014 at 11:54:10PM +0200, Ludovic Courtès wrote: > Please run ‘make check’, try it, and report any problems. Note that > commit bf59c06 adds the public key used to sign substitutes from > hydra.gnu.org. This commit is GPG-signed by me, like this message

Python 3 test failures

Mark H Weaver skribis: > == > ERROR: test_fork (test.test_pty.PtyTest) > -- > Traceback (most recent call last): > File > "/tmp/nix-build-python-3.3.3.drv-13/

Re: Why is this build considered a failure by hydra?

Mark H Weaver skribis: > Looking at http://hydra.gnu.org/jobset/gnu/master , it seems that a > large percentage of our builds have started failing. I was curious so I > took a look. The first failure I looked at was 'file', since I recently > upgraded it: > > http://hydra.gnu.org/build/46637

Re: [Nix-dev] [PATCH] Make sure /dev/pts/ptmx is world-writable

On Thu, Apr 03, 2014 at 09:31:11AM +0200, Ludovic Courtès wrote: > Lluís Batlle i Rossell skribis: > > > Usually it's handled with the devpts special mountable device. The > > "ptmxmode" variable handles that. Don't you want to mount that in the > > chroot? > > Ah sorry, I see the ptmxmode mount

Re: [Nix-dev] [PATCH] Make sure /dev/pts/ptmx is world-writable

Lluís Batlle i Rossell skribis: > Usually it's handled with the devpts special mountable device. The > "ptmxmode" variable handles that. Don't you want to mount that in the > chroot? Ah sorry, I see the ptmxmode mount option: https://www.kernel.org/doc/Documentation/filesystems/devpts.txt We

Re: [Nix-dev] [PATCH] Make sure /dev/pts/ptmx is world-writable

Hello! Lluís Batlle i Rossell skribis: > On Wed, Apr 02, 2014 at 11:41:11PM +0200, Ludovic Courtès wrote: >> Hello, >> >> While running Python 3’s test suite, we noticed that on some systems >> /dev/pts/ptmx is created with permissions 0 (that’s the case with my >> Nixpkgs-originating 3.0.43 ke

Re: Proposal: prefetch tarballs in a batch

Nikita Karetnikov skribis: >>> Is there a function that accepts a package name and returns a list of >>> implicit inputs? > >> No, because by definition, those “implicit inputs” are not listed in the >> package object. Instead, they are added by the build system (see >> build-system/gnu.scm.) >