bug#27157: Building Guile 2.2 "times out"

[Maxim Cournoyer]

The build errors out with:

--8<---cut here---start->8---
  SNARF  weak-set.doc
  SNARF  weak-table.doc
  SNARF  weak-vector.doc
  SNARF  posix.doc
  SNARF  net_db.doc
  SNARF  socket.doc
  SNARF  regex-posix.doc
  CCLD libguile-2.2.la
.libs/libguile_2.2_la-posix.o: In function `scm_tmpnam':
/tmp/guix-build-guile-2.2.2.drv-0/guile-2.2.2/libguile/posix.c:1574: warning: 
the use of `tmpnam' is dangerous, better use `mkstemp'
  CCLD guile
  GEN  guile-procedures.texi
make[3]: Leaving directory 
'/tmp/guix-build-guile-2.2.2.drv-0/guile-2.2.2/libguile'
make[2]: Leaving directory 
'/tmp/guix-build-guile-2.2.2.drv-0/guile-2.2.2/libguile'
Making all in bootstrap
make[2]: Entering directory 
'/tmp/guix-build-guile-2.2.2.drv-0/guile-2.2.2/bootstrap'
  BOOTSTRAP GUILEC ice-9/eval.go
wrote `ice-9/eval.go'
  BOOTSTRAP GUILEC ice-9/psyntax-pp.go
  BOOTSTRAP GUILEC language/cps/intmap.go
building of `/gnu/store/i2p0gqxm378ydlh58qpy6jas7rdk79jg-guile-2.2.2.drv' timed 
out after 3600 seconds of silence
cannot build derivation
  `/gnu/store/c34w733549bjvcdixb0yj306ydhwv8c3-guile2.2-gnutls-3.5.9.drv':
  1 dependencies couldn't be built
--8<---cut here---end--->8---

I'm not sure where this timeout value can be configured, but clearly it
shouldn't be 1 hour since 2 cores of an i5 intel class processor can't
manage to build it under 1 hour.

Maxim

bug#27152: deprecation warnings with Guile 2.2.2

[Ricardo Wurmus]

I get a couple of deprecation warnings with Guile 2.2.2, for example

Import (ice-9 threads) to have access to `current-processor-count'.
`_IOFBF' is deprecated.  Use the symbol 'block instead.

I only see them after “export GUILE_WARN_DEPRECATED=detailed”.  Without
that variable I get a block of text that informs me that deprecated
features have been used.

This happens especially when running “make” or when not all files have
been compiled.

-- 
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net

bug#27067: Feature request: please allow for either automatic logging of all output of every guix commands or add an option to each guix command to allow it for all to be logged

[Ludovic Courtès]

Hi Brenton,

Brenton Horne  skribis:

> As I understand it only the guix build command has an option to log output to 
> a file.

Every derivation that is built, regardless of the command, has its log
stored in /var/log/guix/drvs.  What ‘guix build’ has is a simple way to
get the file name or URL of a build log:

  guix build --log-file coreutils

See:

  
https://www.gnu.org/software/guix/manual/html_node/Additional-Build-Options.html
  
https://www.gnu.org/software/guix/manual/html_node/Invoking-guix_002ddaemon.html
(specifically --lose-logs and --disable-log-compression)

Can we say your feature request has already been fulfilled?  :-)

Thanks,
Ludo’.

bug#27137: make check 'FAIL: tests/guix-package-net'

[myglc2]

On 05/30/2017 at 17:45 Ludovic Courtès writes:

> Hi myglc2,
>
> myglc2  skribis:
>
>> + test t-profile-21734-2-link = t-profile-21734-2-link
>> + guix package -p t-profile-21734 --switch-generation=-1
>> accepted connection from pid 30492, user g1
>> switched from generation 2 to 1
>> guix package: warning: Your Guix installation is 13 days old.
>> guix package: warning: Consider running 'guix pull' followed by
>> 'guix package -u' to get up-to-date packages and security updates.
>>
>> ++ readlink_base t-profile-21734
>> +++ readlink t-profile-21734
>> ++ basename t-profile-21734-1-link
>> + test t-profile-21734-1-link = t-profile-21734-1-link
>> ++ seq 1 3
>> + for i in `seq 1 3`
>> + guix package --bootstrap --roll-back -p t-profile-21734
>> accepted connection from pid 30827, user g1
>> guix package: error: profile 't-profile-21734' does not exist
>
> Could it be that a concurrent process removed ‘t-profile-21734’ behind
> our back?

I have no idea! This time I did ...

make -j check

... but I often do ...

make -j 10 check

... so I repeated ...

make -j 10 check

... a few times thinking maybe another test could delete the link, but
could not reproduce the error. BTW, from each 'make check' I do end up
with a dangling link like ...

t-profile-alt-10987-1-link ->
/home/g1/src/guix/test-tmp/store/hwr4xiqd60wrh033wvjljly50j6d39dg-profile

... is this normal?

> As you can see, that symlink was available just above.
> Or is it 100% reproducible when running
>
>   make check TESTS=tests/guix-package-net.sh
>
> ?

It is not reproducible ... except by deleting the profile while the test is
running ;-)

HTH - George

bug#27135: /root is world readable by default

[Marius Bakke]

Ludovic Courtès  writes:

> Hi Alex,
>
> Alex Griffin  skribis:
>
>> After a default install of GuixSD, anybody can read root's home
>> directory. I think /root should have permissions 700 instead of 755.
>
> Fixed in 41db5a756369f5b14d1e67a523ee0940cad56744.
>
> For the other user accounts, useradd(8) does its thing, and apparently
> it defaults to world-readable accounts (it defaults to a umask of 022 as
> written in the man page).
>
> Thoughts?

I'm in favor of overriding that default. I usually chmod /home/* to 0700
anyway. 0750 would be okay too and probably covers more use cases.


signature.asc
Description: PGP signature

bug#27135: /root is world readable by default

[Ludovic Courtès]

Hi Alex,

Alex Griffin  skribis:

> After a default install of GuixSD, anybody can read root's home
> directory. I think /root should have permissions 700 instead of 755.

Fixed in 41db5a756369f5b14d1e67a523ee0940cad56744.

For the other user accounts, useradd(8) does its thing, and apparently
it defaults to world-readable accounts (it defaults to a umask of 022 as
written in the man page).

Thoughts?

Thanks,
Ludo’.

bug#27069: LUKS partition ruined by guix init

[Marius Bakke]

Mark H Weaver  writes:

> Marius Bakke  writes:
>
>> some...@selfhosted.xyz writes:
>>
>>> Hi,
>>>
>>> I have several times over tried to install to a LUKS-partition with
>>> btrfs and failed but last time I almost had success. guix init command
>>> complained that the bios_grub flag wasn't set after many hours of
>>> compiling packages and therefore didn't install grub at first. I
>>> checked the partition with "cryptsetup luksUUID /dev/sda1" before
>>> rerunning guix init and it gives me the luksUUID so the partition
>>> seemed intact up to that point. However, after setting the bios_grub
>>> flag and rerunning guix init, the installation is successful but
>>> afterwards the cryptsetup luksUUID command says that the partition is
>>> not a valid luks device, so it seems like the GRUB installation part
>>> is what ruins the partition.
>>
>> What is your partition layout? The "bios_grub" partition must be a
>> separate (typically tiny) partition with no other data on it.
>
> FWIW, my current development system is GuixSD running with a
> LUKS-encrypted Btrfs root partition with GUID partition table.
> I don't remember encountering any difficulties during the install.

Interesting. Did you reserve some sectors before the first partition? Or
do you have the root partition marked as "bios_grub", which is what
seemingly wiped the LUKS headers here?


signature.asc
Description: PGP signature

bug#27003: [PATCH 0/3] Generalized wrap phase for perl, python.

[Marius Bakke]

Arun Isaac  writes:

>> I cannot currently make guarantees on when I'll be able to wrap my head
>> around the entire problem, so if you come to conclusions for next steps
>> on the basis of your testing, we should go with those.
>>
>> Else I will revisit this issue when I have time (which might be a
>> while).
>
> I don't have any ideas on how to fix this. And, I don't understand Guix
> internals very well. So, I'll wait for you or someone else to come up
> with a solution. But, I can help with testing patches.

I'm not sure if #25235 should block this issue though, since it's a
useful change regardless. But, not handling it adds "technical debt",
and a (minor) problem that is not currently present in perl modules.

We do have until the next 'core-updates' to think about it though ;-)


signature.asc
Description: PGP signature

bug#27120: [PATCH] gnu: graphicsmagick: Remove bundled libraries from source checkout.

[Ludovic Courtès]

Leo Famulari  skribis:

> Fixes .
>
> * gnu/packages/imagemagick.scm (graphicsmagick)[source]: Add a snippet
> to delete bundled libraries.
> [version]: Bump the package revision counter to 3.

That was fast!

> +(snippet
> + '(begin
> +;; Remove bundled software. This reduces the size of the
> +;; build source checkout from 177 MiB to 49 MiB. This 
> should
> +;; not be necessary when using the GraphicsMagick release
> +;; tarball, because these files are not distributed 
> there.
> +(for-each delete-file-recursively '("bzlib" "dcraw" 
> "hp2xx"
> +"jbig" "jp2" "jpeg"
> +"lcms" "libxml" "png"
> +"ralcgm" "tiff" "ttf"
> +"webp" "wmf" "xlib"
> +"zlib"))

You can even remove ‘begin’.

LGTM, thank you!

Ludo’.

bug#27149: ‘perl-build-system’ does not support cross-compilation

[Ricardo Wurmus]

When trying to cross-build GCompris for armhf the build fails because
Perl dependencies cannot be cross-built.

The “perl-build-system” needs to be augmented to do the right thing when
cross-compilation is requested.  But what is the right thing to do?

--
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net

bug#26897: ‘cmake-build-system’ does not support cross-compilation

[Ricardo Wurmus]

Implemented in commit d2ac5e297578dea1c872f77a26ef4d481d5dc7bd.

--
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net

bug#27142: classpath-0.99-1.e7c13ee0c fails to build

[Ricardo Wurmus]

Fixed with commit 93c103ab594fae918743f50ec8346854f0a85f1a.
-- 
Ricardo

bug#27003: [PATCH 0/3] Generalized wrap phase for perl, python.

[Arun Isaac]

> I cannot currently make guarantees on when I'll be able to wrap my head
> around the entire problem, so if you come to conclusions for next steps
> on the basis of your testing, we should go with those.
>
> Else I will revisit this issue when I have time (which might be a
> while).

I don't have any ideas on how to fix this. And, I don't understand Guix
internals very well. So, I'll wait for you or someone else to come up
with a solution. But, I can help with testing patches.

bug#27146: system init: if /etc doesn't exist, create it

[ng0]

I had the unfortunate experience of remote fixing a system,
and one way I tried to fix my original problem was to
remove the /etc directory (this included the content of
debian 8 with some alternative changes to the minimal
one I did not set up myself).
When I rebooted, this is still at activation of the first
system generation, I get the repl because the symlink
target does not exist (obviously).

We should think of such situations, however uncommon they are,
and check if /etc exists. If it doesn't exist create it
otherwise it is assumed that it exists and for example
this symlink creation will work: ssl -> /run/current-system/profile/etc/ssl

-- 
ng0
OpenPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588


signature.asc
Description: PGP signature

bug#27145: document GuixSD system recovery process + document bournish and recovery/guile repl

[ng0]

Currently neither bournish nor the guile recovery repl are documented
in a way which is helpful for a person which isn't technical
knowledged running into the unhappy case of a system which doesn't
boot. In fact both are not even mentioned in our documentation
and the built in help is not sufficient.
-- 
ng0
OpenPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588


signature.asc
Description: PGP signature

bug#27144: guix publish: “mutex already locked by thread”

[Ludovic Courtès]

Seen on hydra.gnu.org:

--8<---cut here---start->8---
GET /jkpcipgxfyfb60pr4b5n4x4j9k5mcxpp.narinfo
In ice-9/boot-9.scm:
 160: 5 [catch #t # ...]
In unknown file:
   ?: 4 [apply-smob/1 #]
In guix/workers.scm:
  84: 3 [#]
  72: 2 [loop]
  76: 1 [# misc-error 
...]
In unknown file:
   ?: 0 [make-stack #t]
ERROR: In procedure make-stack:
ERROR: Throw to key `misc-error' with args `("mutex already locked by thread")'.
--8<---cut here---end--->8---

This is with
/gnu/store/cxmj38x6rh0ykq3d5dlqbxr5h1zgiiaf-guile2.0-guix-0.13.0-1.a6d728b.

Ludo'.

bug#27142: classpath-0.99-1.e7c13ee0c fails to build

[Ricardo Wurmus]

On a machine with 62G memory classpath fails to build from source.

--8<---cut here---start->8---
$ free -h
  totalusedfree  shared  buff/cache   available
Mem:62G1.1G 35G 32M 25G 61G
Swap:  5.0G  0B5.0G
--8<---cut here---end--->8---

The problem appears to be that by default the JVM tries to allocate as
much memory as it can, so the initial size of the heap may be larger
than the set maximum.

Here’s the error:

--8<---cut here---start->8---
/gnu/store/ncvpxqykv672wjfygmki7phc7v8kz8iz-ecj-javac-on-jamvm-wrapper-3.2.2/bin/javac
  -nowarn -source 1.6 -target 1.6 -bootclasspath '' -classpath 
../vm/reference:..:../external/w3c_dom:../external/sax:../external/relaxngDatatype:../external/jsr166:.::
 -J-Xmx768M -d . @classes
Minimum heap size greater than max!
touch compile-classes
touch resources
/gnu/store/rw6zb4l1dqg1zx252ri9722ffb1r20jm-fastjar-0.98/bin/fastjar cf 
glibj.zip gnu java javax org sun META-INF && 
/gnu/store/rw6zb4l1dqg1zx252ri9722ffb1r20jm-fastjar-0.98/bin/fastjar i glibj.zip
sun: No such file or directory
Error adding sun to jar archive!
make[1]: *** [Makefile:674: glibj.zip] Error 1
make[1]: Leaving directory 
'/tmp/guix-build-classpath-0.99-1.e7c13ee0c.drv-0/source/lib'
make: *** [Makefile:523: all-recursive] Error 1
phase `build' failed after 3.7 seconds
--8<---cut here---end--->8---

I think we may be able to fix this by ensuring that we also pass
-J-Xms768M to the compiler (or -Xms768M to the invocation of “java”) to
set the initial heap size no greater than the maximum.

--
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net