bug#31977: clone tests fail on CentOS 7

2020-12-21 Thread Paul Garlick
Hi Simon, > If I understand well your message: > > Files: > a) '/proc/self/ns/user' exists > b) '/proc/sys/kernel/unprivileged_userns_clone' does not exist. Yes, this is the case on CentOS. So testing for the existence of the unprivileged_userns_clone file is an insuff

bug#45069: BUG: Re: guix environment: error: cannot create container: unprivileged user cannot create user namespaces

2020-12-07 Thread Paul Garlick
Hi Pierre, > # echo 1 > /proc/sys/kernel/unprivileged_userns_clone > -bash: /proc/sys/kernel/unprivileged_userns_clone: No such file or > directory Thanks, that gives us a clue. So all or part of the path '/proc/sys/kernel' is missing? Best regards, Paul.

bug#45069: BUG: Re: guix environment: error: cannot create container: unprivileged user cannot create user namespaces

2020-12-07 Thread Paul Garlick
Hi Pierre, Can you try, as root on Guix System: $ echo 1 > /proc/sys/kernel/unprivileged_userns_clone If you could report success or failure that would be helpful; the unprivileged-user-namespace-supported? test in gnu/build/linux- container.scm should be the same irrespective of the underlying

bug#31977: clone tests fail on CentOS 7

2020-12-03 Thread Paul Garlick
Hi Simon, I have pushed the fix as 8bc5ca5160db3d82bd5b6b2b7ed80c96f42bd33e. Best regards, Paul.

bug#31977: clone tests fail on CentOS 7

2020-12-02 Thread Paul Garlick
Hi Simon, On Tue, 2020-12-01 at 19:12 +0100, zimoun wrote: > This old bug #31977 is about an issue on your CentOS 7 machine. Is > it still relevant? Yes, this bug still exists. However, I have just tested a fix: --- a/gnu/build/linux-container.scm +++ b/gnu/build/linux-container.scm @@ -44,7 +

bug#39727: statx error running 'guix gc' on CentOS 7

2020-02-24 Thread Paul Garlick
Hi Ludo, > Great. Could you apply the following patch, run the daemon with: > > sudo -E ./pre-inst-env guix-daemon --build-users-group=… > > then run: > > guix gc -C42 Yes, all is good. I have re-built guix with your patch and started the daemon. Now 'guix gc' runs as expected: . .

bug#39727: statx error running 'guix gc' on CentOS 7

2020-02-24 Thread Paul Garlick
Hi Ludo, > This was during the “removing unused link” phase, right? > Yes, that's it. > The system is running CentOS 7: > > $ cat /etc/centos-release > CentOS Linux release 7.7.1908 (Core) > > What does “uname -r” return? 3.10.0-1062.12.1.el7.x86_64 > Let me know how it goes! I compiled a C

bug#39727: statx error running 'guix gc' on CentOS 7

2020-02-21 Thread Paul Garlick
Hi Guix, After a 'guix pull' today to commit 536cc4aae5b58b45b974530646a4916a29a8aa6c I noticed that 'guix gc' fails with the message: guix gc: error: statting `/gnu/store/.links/0pck...': Invalid argument The system is running CentOS 7: $ cat /etc/centos-release CentOS Linux release 7.7.1908 (

bug#31977: clone tests fail on CentOS 7

2018-06-26 Thread Paul Garlick
Hi Guix, Running 'make check' in the guix source tree on a CentOS 7 system results in 15 FAILS: tests/containers.log: 9 FAILS tests/syscalls.log: 3 FAILS tests/guix-environment-container.log: 1 FAIL tests/guix-pack.log: 1 FAIL tests/pack.log: 1 FAIL Referring to bug#24108, the cause may be that

bug#25476: pivot-root test fails on Ubuntu 16.04

2017-02-13 Thread Paul Garlick
> I think a1a8b7f2e20513a3ad968e74e7ec52546404e3c6 fixes this. > > Yes, confirmed.  The utmpx-entries test now passes. The pivot-root test still fails.  One thought; I made a change to the guix-daemon.service file, at about the same time as updating Ubuntu to 16.04, setting TMPDIR to /data/tmp.  

bug#25476: pivot-root test fails on Ubuntu 16.04

2017-02-01 Thread Paul Garlick
Hi Ludo, Here is the output from the guile session: paul$ ./pre-inst-env guile GNU Guile 2.0.13 Copyright (C) 1995-2016 Free Software Foundation, Inc. Guile comes with ABSOLUTELY NO WARRANTY; for details type `,show w'. This program is free software, and you are welcome to redistribute it under

bug#25476: pivot-root test fails on Ubuntu 16.04

2017-01-31 Thread Paul Garlick
> > Could you change “(eq? #t result)” to “result”, rerun the test, and > send > syscalls.log? > > Hi Ludo, After a 'git pull --rebase' I now have: $ git describe v0.12.0-984-gabb7eb7 The pivot-root test still fails.  The 'actual-value' is now #.  I have attached the syscalls.log file.   In fact

bug#25476: pivot-root test fails on Ubuntu 16.04

2017-01-20 Thread Paul Garlick
Hi Ludo, > That’s on Git master, right? Yes, back on the master branch the test still fails: $ git describe v0.11.0-3373-g2df3d14 > Could you post tests/syscalls.log? > Attached. Best, Paul. test-name: mount, ENOENT location: /data/paul/sourceCode/guix/tests/syscalls.scm:38 source: + (test-equal

bug#25476: pivot-root test fails on Ubuntu 16.04

2017-01-18 Thread Paul Garlick
Hi, I have noticed that the pivot-root test on my development system has started to fail.  After running 'make check' the result: FAIL is recorded for the syscalls.scm test. I have recently updated the system.  It is running Ubuntu 16.04.  Previously, the test passed.  Now: $ uname -r 4.4.0-59-g