bug#35371: [core-updates] python-cffi fails its test suite

2019-04-21 Thread Maxim Cournoyer
It seems that something in Guix confuses the python-cffi code logic and makes it "think" the platform should be 'win32', while it is 'linux'. The errors output is copied below: --8<---cut here---start->8--- === FAILURES =

bug#35359: docker-image produces corrupt tar

2019-04-21 Thread Ludovic Courtès
Hi, rendaw <7e9wc56emja...@s.rendaw.me> skribis: > $ guix system docker-image testsystem2.scm --on-error=backtrace > successfully built > /gnu/store/l3psqh73xjb5h11y1hwrlfvl1yr920x4-guixsd-docker-image.tar.gz.drv > /gnu/store/giaw69wla9zdf4k7nddyyglvhq3629jq-guixsd-docker-image.tar.gz > $ tar -zt

bug#35356: exception caught while executing 'start' on service 'user-homes':

2019-04-21 Thread Ludovic Courtès
Hello, Danny Milosavljevic skribis: > guix system: error: exception caught while executing 'start' on service > 'user-homes': > Throw to key `match-error' with args `("match" "no matching pattern" > "#< name: \"root\" password: \"\" uid: 0 group: \"root\" > supplementary-groups: () comment: \

bug#35350: Some compile output still leaks through with --verbosity=1

2019-04-21 Thread Ludovic Courtès
Hi Mark, Mark H Weaver skribis: > Sometimes when compiling a package with --verbosity=1, some parts of the > compile output leak through. For example, see the transcript below. Weird. What’s the value of --max-jobs? Is offloading enabled? Presumably both the client and daemon are recent, ri

bug#35068: GDM crashes when it cannot find any .desktop files

2019-04-21 Thread Ludovic Courtès
Danny Milosavljevic skribis: > Apr 21 11:23:57 localhost gdm: XXX gdm: value == NULL for key == PATH > Apr 21 11:23:57 localhost gdm: Child process -1384 was already dead. > Apr 21 11:23:57 localhost gdm: Child process 1381 was already dead. > Apr 21 11:23:57 localhost gdm: Unable to kill sess

bug#35283: ISO images are not reproducible

2019-04-21 Thread Thomas Schmitt
Hi, Ludovic Courtès wrote: > AFAICS, setting SOURCE_DATE_EPOCH didn’t have a noticeable impact on > Xorriso, or at least it was overridden by the “-volume_date” options > that I pass. Probably. Among the automatic grub-mkrescue options for xorriso's mkisofs emulation is --modification-date=201

bug#35283: ISO images are not reproducible

2019-04-21 Thread Ludovic Courtès
Hi, "Thomas Schmitt" skribis: >> 833480cc1f vm: Reset file timestamps in ISO images. > > That's also a big solution for the problem of timestamps of synthetic files. > > I understand that your plan for reproducibility is to make timestamps > completely insignificant. Radical but effective. > >

bug#35283: [PATCH] grub-mkrescue: Allow users to specify a FAT serial number

2019-04-21 Thread Ludovic Courtès
Hello, While investigating reproducible ISO images for Guix¹, I found that ‘grub-mkrescue’ would invoke ’mformat’ without the ‘-N’ option. Consequently, ‘mformat’ would pick a random serial number, thereby making the ‘efi.img’ build process non-deterministic. I came up with the gross hack attache

bug#35358: texlive atomic install

2019-04-21 Thread Gabriel Hondet
Hi Ricardo, On Sun 21 Apr 2019 at 15:57 Ricardo Wurmus wrote: > Can you tell us what packages you installed? Sure, from a manifest: "texlive-latex-base" "texlive-latex-xcolor" "texlive-latex-wrapfig" "texlive-latex-titlesec" "texlive-latex-tools" "texlive-latex-tabulary"

bug#35358: texlive atomic install

2019-04-21 Thread Ricardo Wurmus
Hi Gabriel, > I installed texlive package per package (not using the "texlive") > package. I end up not being able to launch any of pdflatex, lualatex > nor xelatex, as I obtain […] Can you tell us what packages you installed? -- Ricardo

bug#35359: docker-image produces corrupt tar

2019-04-21 Thread rendaw
Package: guix Version: 0.16.0 I took the sample system configuration at the top of https://www.gnu.org/software/guix/manual/en/html_node/Using-the-Configuration-System.html#Using-the-Configuration-System and ran: ``` $ guix system docker-image testsystem2.scm --on-error=backtrace successfully bui

bug#35358: texlive atomic install

2019-04-21 Thread Gabriel Hondet
Hi, I installed texlive package per package (not using the "texlive") package. I end up not being able to launch any of pdflatex, lualatex nor xelatex, as I obtain Can't locate mktexlsr.pl in @INC (@INC contains: /gnu/store/tlpkg /gnu/store/texmf-dist/scripts/texlive /home/gabriel/. guix-profile

bug#35357: udev - ${exec_prefix} left over somewhere

2019-04-21 Thread Danny Milosavljevic
./lhd03fz51lm9wp82az83y754yybc7sb8-eudev-3.2.7/lib/udev/rules.d/64-btrfs.rules:ENV{ID_BTRFS_READY}=="1", RUN+="${exec_prefix}/bin/udevadm trigger -s block -p ID_BTRFS_READY=0" pgpkJmlEWtN32.pgp Description: OpenPGP digital signature

bug#35068: GDM crashes when it cannot find any .desktop files

2019-04-21 Thread Danny Milosavljevic
Apr 21 11:38:51 localhost gdm: GdmSessionWorkerJob: Running session_worker_job process: gdm-session-worker [pam/gdm-launch-environment] /gnu/store/qz8413ijzxnh6kfkxr8syxjwvhsc6s3a-gdm-3.26.2.1/libexec/gdm-session-worker Apr 21 11:38:51 localhost gdm: GdmSessionWorkerJob: : SessionWorkerJob on p

bug#35357: udev - ${exec_prefix} left over somewhere

2019-04-21 Thread Danny Milosavljevic
vmunix: [ 11.748355] udevd[513]: failed to execute '/gnu/store/gdm4g9h9nk5g922g56vq89jhbzbda4sc-eudev-3.2.7/lib/udev/${exec_prefix}/bin/udevadm' '${exec_prefix}/bin/udevadm trigger -s block -p ID_BTRFS_READY=0': No such file or directory pgpLHrhb6GDFs.pgp Description: OpenPGP digital signatu

bug#35068: GDM crashes when it cannot find any .desktop files

2019-04-21 Thread Danny Milosavljevic
Further investigation: diff -ru orig/gdm-3.26.2.1/daemon/gdm-session.c gdm-3.26.2.1/daemon/gdm-session.c --- orig/gdm-3.26.2.1/daemon/gdm-session.c 1970-01-01 01:00:00.0 +0100 +++ gdm-3.26.2.1/daemon/gdm-session.c 2019-04-21 10:58:31.211164558 +0200 @@ -2483,6 +2483,10 @@

bug#35356: exception caught while executing 'start' on service 'user-homes':

2019-04-21 Thread Danny Milosavljevic
guix system: error: exception caught while executing 'start' on service 'user-homes': Throw to key `match-error' with args `("match" "no matching pattern" "#< name: \"root\" password: \"\" uid: 0 group: \"root\" supplementary-groups: () comment: \"System administrator\" home-directory: # create

bug#35283: ISO images are not reproducible

2019-04-21 Thread Thomas Schmitt
Hi, > 833480cc1f vm: Reset file timestamps in ISO images. That's also a big solution for the problem of timestamps of synthetic files. I understand that your plan for reproducibility is to make timestamps completely insignificant. Radical but effective. But since you set in commit 6901b9248e