bug#56583: Partitioner was detecting a filesystem where none existed

[Peter]

Hi,

This is with the latest snapshot.

This is minor because it was being formatted anyway, but the issue is that
I had created a raw unformatted partition outside of GUIX, but the GUIX
partitioner tool was seeing it as possessing a filesystem of EXT4 already,
when in fact it should have been blank. Maybe it is a trace of a previous
partition that was in the space, but this is odd, it should not have
detected a filesystem on a new blank partition.

This means it was not reading the partition table correctly.

Best,
Peter

bug#56582: Installer does not detect or allow detection of other bootable partitions

[Peter]

Hi,

This is a particularly AWFUL user experience bug. Installing GUIX to a
partition only lists GUIX in the grub boot menu afterward despite the
existence of other bootable OSes on the drive.

Ok fine thinks I, I will just need to manually run grub's mkconfig to force
re-detection. But this command does not exist in GUIX. Installing grub did
not create grub2-mkconfig. Installing osprober wasn't helpful.

I did not see documentation on how to make GUIX detect and add other
operating systems to the boot menu from userland. After much time wasted, I
needed to download another distro, install it so it would repair the boot
menu, and then be able to boot into my main partition.

Recommendation:
Installer needs to detect and add to the menu the other OSes.
Documentation needs to show how to do it manually via a different method if
GUIX does not include grub2-mkconfig otherwise it needs to warn upfront
that this distro should not be used on multi-boot PCs.

Best,
Peter

bug#56580: 1.3.0 internet connectivity bug

[Peter]

Hi,

For some bizarre reason, even though it worked last night, today the 1.3.0
usb could no longer establish an internet connection on the intel wired
ethernet. Just a red screen saying no connectivity.

The issue is specific to 1.3.0. The other OSes could use the lan fine, and
the GUIX snapshot image was able to establish an internet connection fine.

Best,
Peter

bug#56581: 1.3.0 F1 reboot bug

[Peter]

Hi,

On the 1.3.0 image, F1 to reboot just locks up the computer with a black
screen. Necessary to hold down power button to force-power-off computer to
restart it.

Using the GUIX snapshot image does not have this issue, reboot works
normally with the later image.

Best,
Peter

bug#56572: failed install on partition, backtrace attached

[Peter]

Follow-up: 1.3.0 installer couldn't be used again, will submit another bug
for the reason why separately.

Using the snapshot 520v5sznglla0z1g3mz6pfsml88b8gxx-image.iso did not have
the error 1.3.0 did trying to format/write to the partition and the install
was able to complete.

So it seems as if there is an issue with the partitioning software in the
1.3.0 image.


On Fri, Jul 15, 2022 at 10:18 AM sunspark  wrote:

> Hi,
>
> I confirm it was with the 1.3.0 installer.
>
> I have since downloaded the snapshot installer but I haven't tested it
> yet. However I would need to be careful testing because this time around I
> have created raw unformatted partitions in Windows disk manager because it
> annoys me how different Linux disk utilities round numbers differently. The
> guix installer views 64 GB as 68.7 GB and entering 68.7 there to create a
> matching 64 creates 63.98 GB instead.
>
> I suppose I would need to run it twice again with the 1.3 first. Once to
> see if just formatting a windows created raw partition fixes it and once
> with a filesystem that isn't ext4 then the snapshot.
>
> My partition table is standard. 100 meg efi, 128 meg Microsoft reserved
> partiton, two NTFS partitions, the two ext4s I was attempting to create in
> unallocated space and a linux swap partition already created.
>
> Incidentally, the reboot command in F1 doesn't work either. Just black
> screens. Need to hold the power button down.
>
> Best,
> Peter
>
>
>
>
>
> Sent from my Galaxy
>
>
>  Original message 
> From: Ludovic Courtès 
> Date: 2022-07-15 06:58 (GMT-05:00)
> To: Peter 
> Cc: 56...@debbugs.gnu.org
> Subject: Re: bug#56572: failed install on partition, backtrace attached
>
> Hi Peter,
>
> Peter  skribis:
>
> > I did manual partitioning because I didn't want to wipe the other
> > partitions out.
> >
> > Set / and /home partitions, formatted as EXT4.
> >
> > Crashes as soon as it writes the changes, displays the backtrace and
> > restarts the installer.
>
> Ouch.  Could you confirm it was with the 1.3.0 installer?
>
> It would seem that the bug comes from ‘read-partition-uuid’ returning #f
> in this function:
>
> --8<---cut here---start->8---
> (define (user-partition->file-system user-partition)
>   "Convert the given USER-PARTITION record in a FILE-SYSTEM record from
> (gnu system file-systems) module and return it."
>   (let* ((mount-point (user-partition-mount-point user-partition))
>  (fs-type (user-partition-fs-type user-partition))
>  (crypt-label (user-partition-crypt-label user-partition))
>  (mount-type (user-fs-type->mount-type fs-type))
>  (file-name (user-partition-file-name user-partition))
>  (upper-file-name (user-partition-upper-file-name user-partition))
>  ;; Only compute uuid if partition is not encrypted.
>  (uuid (or crypt-label
>(uuid->string (read-partition-uuid file-name)
> fs-type
> `(file-system
>(mount-point ,mount-point)
>(device ,@(if crypt-label
>  `(,upper-file-name)
>  `((uuid ,uuid (quote ,fs-type)
>(type ,mount-type)
>,@(if crypt-label
>  '((dependencies mapped-devices))
>  '()
> --8<---cut here---end--->8---
>
> This can happen if a partition you chose to create actually contains
> random data or a file system not supported by (gnu build file-systems);
> this, in turn, can happen if you chose not to format partitions during
> the installation process.
>
> Could it be what happened in your case?
>
> Ludo’.
>

bug#56582: Installer does not detect or allow detection of other bootable partitions

[Peter]

Hi,

My concern is that what is written in the manual for bootloader-config and
invoking-guix-system does not clearly communicate what needs to be done for
those who have no exposure to either Guix or Scheme. I did actually view
those entries at first, but it seemed theoretical at first glance and I
kept moving because I was looking for an expected binary.

To expand on this, Guix installs GRUB. This is undeniable, and this is
where the problem begins.. over many years users are accustomed to GRUB
working in a certain way with specific tools.. when they encounter a grub
installation without grub-mkconfig, etc. they are at a loss, because it's a
binary they expected to find and it's just not present. I think an argument
could be made here that this behaviour breaks user space because it's
established software, but changed to function differently as opposed to
being something entirely new. It's like wearing your shoes on the opposite
foot. You can do it, but it feels wrong.

The way Debian and other distros manage Grub is via mkconfig, and the boot
menu presented is very similar to Guix's, the only difference is that
there's an extra row entry in the grub menu for the Windows bootloader to
be launched.

Personally, I dislike Grub because I feel it complicates things. I would
love to use only UEFI and use only the bios boot menu to switch, but for
whatever reason in a single internal drive system, this isn't easily done.
Giving an example, awhile back, I tried installing a distro to an external
usb drive.. it worked.. but the problem is that it installed grub to the
internal drive.. and if you removed the usb drive from the pc, things would
break because now a device it was expecting to see wasn't there. A
workaround suggested was to disconnect the internal drive, do the setup,
this way Grub would be on the external drive, then reconnect the internal
drive and then I guess use the bios uefi menu to switch between, a lot of
bother for a tightly sealed unit.

The way MS's bootloader works is nice because one of the menu options it
has is to pick a physical device so you can actually boot from a valid
bootable USB flash drive device and it launches that device directly.

Maybe the solution is just to create an EFI partition at the front of all
drives including external as Apple does and then it doesn't matter what
bootloader you use or do not use, because you could always just use the
UEFI menu to point to a device. Not using a bootloader would reduce
complexity of maintenance.. if MS's bootloader is there, people can use it
if they want to point to the device, and if it is not there, then they can
use the uefi bios menu. In theory.

MBR folks would still need to continue using a bootloader of course.

Best,
Peter


On Sat, Jul 16, 2022 at 6:32 AM Julien Lepiller  wrote:

> If anything, you also need to chainload to boot on haiku, which is free
> software. So no reason not to implement it.
>
> Le 16 juillet 2022 11:59:29 GMT+02:00, Josselin Poiret 
> a écrit :
>>
>> Hello both of you,
>>
>> Julien Lepiller  writes:
>>
>>> Of course this is only a workaround I'm proposing, we should fix the 
>>> installer to detect other OSs.
>>>
>> Just adding that we don't have any Guix bootloader entry field to
>> chainload into another bootloader, needed for some non-free system :)
>> this would need to be added as well.
>>
>> I personally don't mind, and use my UEFI boot menu instead if I want to
>> boot into said non-free OS.
>>
>> Best,
>> --
>> Josselin Poiret
>>
>>

"make check" fails with guix-0.2

[Peter Maloney]

Dear GNU,

"make check" fails with guix-0.2


This is the part that fails (tested by commenting it out):

(test-assert "filtered-port, file"
  (let ((file (search-path %load-path "guix.scm")))
(call-with-input-file file
  (lambda (input)
(let*-values (((compressed pids1)
   (filtered-port `(,%gzip "-c" "--fast") input))
  ((decompressed pids2)
   (filtered-port `(,%gzip "-d") compressed)))
  (and (every (compose zero? cdr waitpid)
  (append pids1 pids2))
   (equal? (get-bytevector-all decompressed)
   (call-with-input-file file get-bytevector-all




$ make check
make  check-recursive
make[1]: Entering directory `/home/peter/projects/guix-0.2'
Making check in po
make[2]: Entering directory `/home/peter/projects/guix-0.2/po'
make[2]: Leaving directory `/home/peter/projects/guix-0.2/po'
make[2]: Entering directory `/home/peter/projects/guix-0.2'
make  check-TESTS
make[3]: Entering directory `/home/peter/projects/guix-0.2'
make[4]: Entering directory `/home/peter/projects/guix-0.2'
PASS: tests/base32.scm
PASS: tests/builders.scm
PASS: tests/derivations.scm
PASS: tests/ui.scm
PASS: tests/records.scm
FAIL: tests/utils.scm
PASS: tests/build-utils.scm
PASS: tests/packages.scm
PASS: tests/snix.scm
PASS: tests/store.scm
PASS: tests/nar.scm
PASS: tests/union.scm
PASS: tests/guix-build.sh
PASS: tests/guix-download.sh
PASS: tests/guix-hash.sh
PASS: tests/guix-package.sh
PASS: tests/guix-gc.sh
PASS: tests/guix-daemon.sh
make[5]: Entering directory `/home/peter/projects/guix-0.2'
make  all-recursive
make[6]: Entering directory `/home/peter/projects/guix-0.2'
Making all in po
make[7]: Entering directory `/home/peter/projects/guix-0.2/po'
make[7]: Leaving directory `/home/peter/projects/guix-0.2/po'
make[7]: Entering directory `/home/peter/projects/guix-0.2'
make[7]: Leaving directory `/home/peter/projects/guix-0.2'
make[6]: Leaving directory `/home/peter/projects/guix-0.2'
make[5]: Leaving directory `/home/peter/projects/guix-0.2'

Testsuite summary for GNU Guix 0.2

# TOTAL: 18
# PASS:  17
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See ./test-suite.log
Please report to bug-guix@gnu.org
====
make[4]: *** [test-suite.log] Error 1
make[4]: Leaving directory `/home/peter/projects/guix-0.2'
make[3]: *** [check-TESTS] Error 2
make[3]: Leaving directory `/home/peter/projects/guix-0.2'
make[2]: *** [check-am] Error 2
make[2]: Leaving directory `/home/peter/projects/guix-0.2'
make[1]: *** [check-recursive] Error 1
make[1]: Leaving directory `/home/peter/projects/guix-0.2'
make: *** [check] Error 2



$ ./configure
configure: loading site script /usr/share/site/x86_64-unknown-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking for style of include used by make... GNU
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking minix/config.h usability... no
checking minix/config.h presence... no
checking for minix/config.h... no
checking whether it is safe to define __EXTENSIONS__... yes
checking whether NLS is requested... yes
checking for msgfmt... /usr/bin/msgfmt
checking for gmsgfmt... /usr/bin/msgfmt
checking for xgettext... no
checking for msgmerge... no
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for ld used by GCC... /usr/x86_64-suse-linux/bin/ld
checking if 

Re: "make check" fails with guix-0.2

[Peter Maloney]

I guess this log is useful too. ;)



$ cat ./test-suite.log

   GNU Guix 0.2: ./test-suite.log


# TOTAL: 18
# PASS:  17
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: tests/utils
=

 Starting test utils  (Writing full log to "utils.log")
 Starting test utils  (Writing full log to "utils.log")
gzip: stdin: file size changed while zipping
 Starting test utils  (Writing full log to "utils.log")
FAIL filtered-port, file
 Starting test utils  (Writing full log to "utils.log")
FAIL filtered-port, file
 Starting test utils  (Writing full log to "utils.log")
FAIL filtered-port, file
 Starting test utils  (Writing full log to "utils.log")
FAIL filtered-port, file

;;; (#t)
# of expected passes  8
# of unexpected failures  1
./test-env: line 1: 23826 Terminated     
"/home/peter/projects/guix-0.2/pre-inst-env"
"/home/peter/projects/guix-0.2/guix-daemon" --disable-chroot





On 2013-07-05 12:00, Peter Maloney wrote:
> Dear GNU,
>
> "make check" fails with guix-0.2
>
>
> This is the part that fails (tested by commenting it out):
>
> (test-assert "filtered-port, file"
>   (let ((file (search-path %load-path "guix.scm")))
> (call-with-input-file file
>   (lambda (input)
> (let*-values (((compressed pids1)
>(filtered-port `(,%gzip "-c" "--fast") input))
>   ((decompressed pids2)
>(filtered-port `(,%gzip "-d") compressed)))
>   (and (every (compose zero? cdr waitpid)
>   (append pids1 pids2))
>(equal? (get-bytevector-all decompressed)
>(call-with-input-file file get-bytevector-all
>
>
>
>
> $ make check
> make  check-recursive
> make[1]: Entering directory `/home/peter/projects/guix-0.2'
> Making check in po
> make[2]: Entering directory `/home/peter/projects/guix-0.2/po'
> make[2]: Leaving directory `/home/peter/projects/guix-0.2/po'
> make[2]: Entering directory `/home/peter/projects/guix-0.2'
> make  check-TESTS
> make[3]: Entering directory `/home/peter/projects/guix-0.2'
> make[4]: Entering directory `/home/peter/projects/guix-0.2'
> PASS: tests/base32.scm
> PASS: tests/builders.scm
> PASS: tests/derivations.scm
> PASS: tests/ui.scm
> PASS: tests/records.scm
> FAIL: tests/utils.scm
> PASS: tests/build-utils.scm
> PASS: tests/packages.scm
> PASS: tests/snix.scm
> PASS: tests/store.scm
> PASS: tests/nar.scm
> PASS: tests/union.scm
> PASS: tests/guix-build.sh
> PASS: tests/guix-download.sh
> PASS: tests/guix-hash.sh
> PASS: tests/guix-package.sh
> PASS: tests/guix-gc.sh
> PASS: tests/guix-daemon.sh
> make[5]: Entering directory `/home/peter/projects/guix-0.2'
> make  all-recursive
> make[6]: Entering directory `/home/peter/projects/guix-0.2'
> Making all in po
> make[7]: Entering directory `/home/peter/projects/guix-0.2/po'
> make[7]: Leaving directory `/home/peter/projects/guix-0.2/po'
> make[7]: Entering directory `/home/peter/projects/guix-0.2'
> make[7]: Leaving directory `/home/peter/projects/guix-0.2'
> make[6]: Leaving directory `/home/peter/projects/guix-0.2'
> make[5]: Leaving directory `/home/peter/projects/guix-0.2'
> 
> Testsuite summary for GNU Guix 0.2
> ====
> # TOTAL: 18
> # PASS:  17
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> ====
> See ./test-suite.log
> Please report to bug-guix@gnu.org
> ====
> make[4]: *** [test-suite.log] Error 1
> make[4]: Leaving directory `/home/peter/projects/guix-0.2'
> make[3]: *** [check-TESTS] Error 2
> make[3]: Leaving directory `/home/peter/projects/guix-0.2'
> make[2]: *** [check-am] Error 2
> make[2]: Leaving directory `/home/peter/projects/guix-0.2'
> make[1]: *** [check-recursive] Error 1
> make[1]: Leaving directory `/home/peter/projects/guix-0.2'
> make: *** [check] Error 2
>
>
>
> $ ./configure
> configure: loading site script /usr/share/site/x86_64-unknown-linux-gnu
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for a thread-safe mkdir -p... /usr/bin/mkdir

bug#18114: Installation images have inconsistent filenames with what's documented in the manual

[Peter Bex]

Hello all,

The Guix manual installation section at
http://www.gnu.org/software/guix/manual/html_node/System-Installation.html
says the following:

---
An installation image for USB sticks can be downloaded from
ftp://alpha.gnu.org/gnu/guix/gnu-usb-install-0.7.system.xz, where system is one 
of:

x86_64-linux
for a GNU/Linux system on Intel/AMD-compatible 64-bit CPUs;
i686-linux
for a 32-bit GNU/Linux system on Intel-compatible CPUs.
---

However, after I constructed the following URL, I got a "file not found" error:
ftp://alpha.gnu.org/gnu/guix/gnu-usb-install-0.7.x86_64-linux.xz

It turns out the filenames lack the -linux suffix as mentioned in the
manual.  davexunit on IRC mentioned that the manual is probably good, so
the files on FTP should be changed by someone with the required access.

Cheers,
Peter
-- 
http://www.more-magic.net

bug#19934: Failed run of make check

[Peter Baumgarten]

The OS was Fedora 21 x86_64, attached is the log

   GNU Guix 0.8: ./test-suite.log


# TOTAL: 33
# PASS:  19
# SKIP:  0
# XFAIL: 0
# FAIL:  14
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: tests/builders


accepted connection from pid 11190, uid 1000
@ build-started /home/me/source/guix-0.8/test-tmp/store/knhmd0pz3nkggxsnr83mgaj9zh4w275h-guile-bootstrap-2.0.drv - x86_64-linux /home/me/source/guix-0.8/test-tmp/var/log/guix/drvs/kn//hmd0pz3nkggxsnr83mgaj9zh4w275h-guile-bootstrap-2.0.drv.bz2
unpacking bootstrap Guile to '/home/me/source/guix-0.8/test-tmp/store/ii67r564iqq79ijv1awhvlcqv9diakh6-guile-bootstrap-2.0'...
/home/me/source/guix-0.8/test-tmp/store/3ii3ixvg81s0c8pm5mvq9gadaqr38yk6-build-bootstrap-guile.sh: line 5: 11206 Done/home/me/source/guix-0.8/test-tmp/store/8yfd969hb48sc89kqcidw240r7hxh4rg-xz -dc < /home/me/source/guix-0.8/test-tmp/store/0fnh7n3596fr7za1qx141i55ydy19syx-guile-2.0.9.tar.xz
 11207 Segmentation fault  (core dumped) | /home/me/source/guix-0.8/test-tmp/store/zdzxpkbavcd23wrfi9faxkzmaba7i33z-tar xv
/home/me/source/guix-0.8/test-tmp/store/3ii3ixvg81s0c8pm5mvq9gadaqr38yk6-build-bootstrap-guile.sh: line 8: /home/me/source/guix-0.8/test-tmp/store/ii67r564iqq79ijv1awhvlcqv9diakh6-guile-bootstrap-2.0/bin/guile: No such file or directory
builder for `/home/me/source/guix-0.8/test-tmp/store/knhmd0pz3nkggxsnr83mgaj9zh4w275h-guile-bootstrap-2.0.drv' failed with exit code 127
@ build-failed /home/me/source/guix-0.8/test-tmp/store/knhmd0pz3nkggxsnr83mgaj9zh4w275h-guile-bootstrap-2.0.drv - 1 builder for `/home/me/source/guix-0.8/test-tmp/store/knhmd0pz3nkggxsnr83mgaj9zh4w275h-guile-bootstrap-2.0.drv' failed with exit code 127
cannot build derivation `/home/me/source/guix-0.8/test-tmp/store/i5y5yr8555gdrvnzx6djcdpbpdcqy6f6-hello-2.8.tar.gz.drv': 1 dependencies couldn't be built
killing process 11199
@ build-started /home/me/source/guix-0.8/test-tmp/store/knhmd0pz3nkggxsnr83mgaj9zh4w275h-guile-bootstrap-2.0.drv - x86_64-linux /home/me/source/guix-0.8/test-tmp/var/log/guix/drvs/kn//hmd0pz3nkggxsnr83mgaj9zh4w275h-guile-bootstrap-2.0.drv.bz2
unpacking bootstrap Guile to '/home/me/source/guix-0.8/test-tmp/store/ii67r564iqq79ijv1awhvlcqv9diakh6-guile-bootstrap-2.0'...
/home/me/source/guix-0.8/test-tmp/store/3ii3ixvg81s0c8pm5mvq9gadaqr38yk6-build-bootstrap-guile.sh: line 5: 11220 Done/home/me/source/guix-0.8/test-tmp/store/8yfd969hb48sc89kqcidw240r7hxh4rg-xz -dc < /home/me/source/guix-0.8/test-tmp/store/0fnh7n3596fr7za1qx141i55ydy19syx-guile-2.0.9.tar.xz
 11221 Segmentation fault  (core dumped) | /home/me/source/guix-0.8/test-tmp/store/zdzxpkbavcd23wrfi9faxkzmaba7i33z-tar xv
/home/me/source/guix-0.8/test-tmp/store/3ii3ixvg81s0c8pm5mvq9gadaqr38yk6-build-bootstrap-guile.sh: line 8: /home/me/source/guix-0.8/test-tmp/store/ii67r564iqq79ijv1awhvlcqv9diakh6-guile-bootstrap-2.0/bin/guile: No such file or directory
builder for `/home/me/source/guix-0.8/test-tmp/store/knhmd0pz3nkggxsnr83mgaj9zh4w275h-guile-bootstrap-2.0.drv' failed with exit code 127
@ build-failed /home/me/source/guix-0.8/test-tmp/store/knhmd0pz3nkggxsnr83mgaj9zh4w275h-guile-bootstrap-2.0.drv - 1 builder for `/home/me/source/guix-0.8/test-tmp/store/knhmd0pz3nkggxsnr83mgaj9zh4w275h-guile-bootstrap-2.0.drv' failed with exit code 127
cannot build derivation `/home/me/source/guix-0.8/test-tmp/store/y8f85ambs4s293plrl7cdfvp85nkf692-hello-2.8.drv': 1 dependencies couldn't be built
killing process 11213
 Starting test builders  (Writing full log to "builders.log")
tests/builders.scm:66: FAIL url-fetch

;;; (hello-drv # /home/me/source/guix-0.8/test-tmp/store/w971b3sv0jdmjpprykw8rsxm2mg07ldx-hello-2.8 3298140>)
tests/builders.scm:98: FAIL gnu-build
# of expected passes  3
# of unexpected failures  2
308 operations
./test-env: line 1: 11189 Terminated  "/home/me/source/guix-0.8/pre-inst-env" "/home/me/source/guix-0.8/guix-daemon" --disable-chroot --substitute-urls="$GUIX_BINARY_SUBSTITUTE_URL"

FAIL: tests/derivations
===

accepted connection from pid 11239, uid 1000
@ build-started /home/me/source/guix-0.8/test-tmp/store/308d0ggcpki6iwi4fqplx0v2mpx756kq-foo.drv - x86_64-linux /home/me/source/guix-0.8/test-tmp/var/log/guix/drvs/30//8d0ggcpki6iwi4fqplx0v2mpx756kq-foo.drv.bz2
@ build-succeeded /home/me/source/guix-0.8/test-tmp/store/308d0ggcpki6iwi4fqplx0v2mpx756kq-foo.drv -
killing process 11248
@ build-started /home/me/source/guix-0.8/test-tmp/store/g3fdlgk4c11sxyggvdsplx49mc7q8avp-derivation-with-input-file.drv - x86_64-linux /home/me/source/guix-0.8/test-tmp/var/log/guix/drvs/g3//fdlgk4c11sxyggvdsplx49mc7q8avp-derivation-with-input-file.drv.bz2
@ build-succeeded /home/me/source/guix-0.8/test-tmp/store/g3fdlgk4c11sxyggvdsplx49mc7q8avp-derivation-with-input-file.drv -
killing process 11254
@ build-started /home/me/source/guix-0.8/test-tmp/store/wj9pgrabddr6nmravi

bug#29824: Meson 0.44.0 is broken with guix.

[Peter Mikkelsen]

Hi,

Den 9. jan. 2018 22.10 skrev "Hartmut Goebel" :

Am 09.01.2018 um 13:46 schrieb Ludovic Courtès:
> Sounds reasonable.  Does it work for you?  If so, could you provide a
> patch?

I don't have any cards in this game and not time for working on it ATM,
I just did the analysis.

@peter: What about you?




I am sorry to let you down, but I dont have any time for developing on guix
at the moment :/ and by the way, I am not, and have never considered myself
a user of meson, I just wanted the buildsystem in guix because I noticed
that gnome was starting to use it :)

-- Peter Mikkelsen

bug#27217: texlive is too big

[Peter Neidhardt]

What's the current status on this?

I've tried processing an Org letter
(http://orgmode.org/worg/exporters/koma-letter-export.html) and I get
the following error:

--8<---cut here---start->8---
(/gnu/store/m6ff2qqh0s1s8dy2ip5d757lmf5ai31x-texlive-tiny-44591/share/texmf-dis
t/tex/latex/graphics-def/pdftex.def)))

! LaTeX Error: File `grffile.sty' not found.

Type X to quit or  to proceed,
or enter new name. (Default extension: sty)

Enter file name:
! Emergency stop.


l.8 \usepackage
   {longtable}^^M
!  ==> Fatal error occurred, no output PDF file produced!
Transcript written on .//koma-letter-new-example.log.
--8<---cut here---end--->8---

I have installed some packages, among which

- texlive-bin
- Some texlive-latex-*
- texlive-latex-oberdiek (which contains grffile.sty)
- texlive-tiny

I noticed that texlive-latex-oberdiek is not in ~(texlive-union)~ (which is
used to generate texlive-tiny), so I suppose this is the root of the
issue.

Without texlive-tiny, pdflatex does not even start, failing on some
missing Perl module.

What's the intended TeXlive installation process then?
Would Guix provide a 1-to-1 map of the CTAN packages and it would be up
to the user to define their own texlive collection which calls
~(texlive-union ...)~ over a custom set of packages?

If so, I assume that koma-script does not have its own package yet.
Correct?

Let me know if I there is anything I can help with.

-- 
Pierre Neidhardt


signature.asc
Description: PGP signature

bug#27217: texlive is too big

[Peter Neidhardt]

Also it seems that the texlive importer is broken:

--8<---cut here---start->8---
> guix import texlive fontspec
following redirection to `https://ctan.org/xml/1.2/pkg/fontspec'...
Backtrace:
  10 (apply-smob/1 #)
In ice-9/boot-9.scm:
705:2  9 (call-with-prompt _ _ #)
In ice-9/eval.scm:
619:8  8 (_ #(#(#)))
In guix/ui.scm:
  1535:12  7 (run-guix-command _ . _)
In guix/scripts/import.scm:
   114:11  6 (guix-import . _)
In guix/scripts/import/texlive.scm:
91:19  5 (guix-import-texlive . _)
In guix/memoization.scm:
 98:0  4 (_ # ("fontspec" "latex") _)
In unknown file:
   3 (_ # 
# #)
In guix/import/texlive.scm:
   157:25  2 (sxml->package (*TOP* (entry (@ (id "fontspec")) (name "fontspec") 
(# #) …)) _)
In guix/serialization.scm:
   270:25  1 (write-file #f # #:select? _)
In unknown file:
   0 (lstat #f)

ERROR: In procedure lstat:
Wrong type (expecting string): #
--8<-------cut here---end--->8---

-- 
Peter Neidhardt

"How to make a million dollars:  First, get a million dollars."
-- Steve Martin


signature.asc
Description: PGP signature

bug#53496: guix pull: error: build of `/gnu/store/njrsv4nw8v750zn6ajdcn8495592q6jb-compute-guix-derivation.drv' failed

[Peter Kois]

While trying to upgrade guix, I did encounter to this error:

root@timelinex:~# guix pull
guile: warning: failed to install locale
hint: Consider installing the `glibc-utf8-locales' or `glibc-locales'
package and defining `GUIX_LOCPATH', along these lines:

 guix package -i glibc-utf8-locales
 export GUIX_LOCPATH="$HOME/.guix-profile/lib/locale"

See the "Application Setup" section in the manual, for more info.

Updating channel 'guix' from Git repository at
'https://git.savannah.gnu.org/git/guix.git'...
Building from this channel:
  guix  https://git.savannah.gnu.org/git/guix.git   3377423
substitute: updating substitutes from 'https://ci.guix.gnu.org'... 100.0%
The following derivations will be built:
   /gnu/store/rxlkjpigq9i7a81g5p1gkvxmybsmcxgx-module-import-compiled.drv
   /gnu/store/njrsv4nw8v750zn6ajdcn8495592q6jb-compute-guix-derivation.drv
building
/gnu/store/rxlkjpigq9i7a81g5p1gkvxmybsmcxgx-module-import-compiled.drv...
  4%
[###

   
]builder for
`/gnu/store/rxlkjpigq9i7a81g5p1gkvxmybsmcxgx-module-import-compiled.drv'
failed with exit code 1
build of
/gnu/store/rxlkjpigq9i7a81g5p1gkvxmybsmcxgx-module-import-compiled.drv
failed
View build log at
'/var/log/guix/drvs/rx/lkjpigq9i7a81g5p1gkvxmybsmcxgx-module-import-compiled.drv.bz2'.
cannot build derivation
`/gnu/store/njrsv4nw8v750zn6ajdcn8495592q6jb-compute-guix-derivation.drv':
1 dependencies couldn't be built
guix pull: error: build of
`/gnu/store/njrsv4nw8v750zn6ajdcn8495592q6jb-compute-guix-derivation.drv'
failed


Full log:


[ 1/78] Loading './gcrypt/hash.scm'...
[ 2/78] Loading './git.scm'...
[ 3/78] Loading './gnu/packages/bootstrap.scm'...
;;; Failed to autoload make-zlib-input-port in (zlib):
;;; missing interface for module (zlib)
;;; Failed to autoload make-zlib-input-port in (zlib):
;;; missing interface for module (zlib)
;;; Failed to autoload make-zlib-output-port in (zlib):
;;; missing interface for module (zlib)
;;; Failed to autoload make-zlib-output-port in (zlib):
;;; missing interface for module (zlib)
/gnu/store/p5si0c0k25raxc2zibiii4v531hk0waa-module-import/guix/grafts.scm:137:7:
warning: 'build-expression->derivation' is deprecated, use
'gexp->derivation' instead
Backtrace:
In ice-9/boot-9.scm:
   2312:4 19 (save-module-excursion _)
  3014:26 18 (_)
In unknown file:
  17 (primitive-load-path "gnu/packages" #)
In ice-9/eval.scm:
   721:20 16 (primitive-eval _)
In ice-9/psyntax.scm:
  1235:36 15 (expand-top-sequence _ _ _ #f _ _ _)
  1182:24 14 (parse _ (("placeholder" placeholder)) ((top) #(# # ?)) ?)
   285:10 13 (parse _ (("placeholder" placeholder)) (()) _ c&e (eval) ?)
In ice-9/eval.scm:
   293:34 12 (_ #)
In ice-9/boot-9.scm:
   2874:4 11 (define-module* _ #:filename _ #:pure _ #:version _ # _ ?)
  2887:24 10 (_)
   222:17  9 (map1 (((guix packages)) ((guix ui)) ((guix utils)) # ?))
  2800:17  8 (resolve-interface (guix packages) #:select _ #:hide _ # ?)
In ice-9/threads.scm:
    390:8  7 (_ _)
In ice-9/boot-9.scm:
  2726:13  6 (_)
In ice-9/threads.scm:
    390:8  5 (_ _)
In ice-9/boot-9.scm:
  2994:20  4 (_)
   2312:4  3 (save-module-excursion _)
  3014:26  2 (_)
In unknown file:
   1 (primitive-load-path "guix/packages" #)
In ice-9/boot-9.scm:
   3492:0  0 (module-re-export! # # ?)

ice-9/boot-9.scm:3492:0: In procedure module-re-export!:
Wrong number of arguments to #


Sincerely, Peter Kois

bug#63440: Some python-pyelftools test failed

[Peter Polidoro]

I am also running into the same issue. I am trying to package 
python-platformio, but python-pyelftools fails its check phase so 
it cannot be used as a dependency.

bug#74130: guix installation write_wait_fd unimplemented

[Peter Tillemans]

Hi,

Installing in a fresh VM on my old QNAP, this thing is slow as molasses in
january, so if there are issues related to timeouts, this thing will find
them.

related to  installer-dump-380ea41e

thanks for GUIX,

Peter Tillemans

bug#74130: guix installation write_wait_fd unimplemented

[Peter Tillemans]

Hi,

it seems to have resolved itself after retrying half a dozen times. Maybe
it was something with the substitute servers which got resolved in the
meantime. In any case at one point it got past the hangup and continued and
successfully installed.

So my immediate issue is resolved but I also assume that calling
unimplemented features are undesirable, even in exceptional circumstances.

thanks,

Peter Tillemans

bug#54453: crash running 'guix pull'

[Peter Bhat Harkins]

I tried running 'guix pull' on a VPS running guix and it crashed. The
output said to email the log to this address, so I am.

I'd appreciate any pointers towards a solution; I did a bit of googling
and didn't see how to get unstuck.

Thanks!


-- 
Peter Bhat Harkins - https://malaprop.org
-bash-5.0# time guix pull -v 1
Updating channel 'guix' from Git repository at 
'https://git.savannah.gnu.org/git/guix.git'...
Authenticating channel 'guix', commits 9edb3f6 to 386adb6 (505 new commits)...
Building from this channel:
  guix  https://git.savannah.gnu.org/git/guix.git   386adb6
substitute: updating substitutes from 'https://ci.guix.gnu.org'... 100.0%
substitute: updating substitutes from 'https://ci.guix.gnu.org'... 100.0%
substitute: updating substitutes from 'https://ci.guix.gnu.org'... 100.0%
building /gnu/store/vgv0hn6b3l03wr8n7gkr1w1544av3qch-module-import.drv...
building /gnu/store/yh914wm3zydmmymks3dhavznlkn3g7g1-module-import.drv...
building 
/gnu/store/lwnsg6xzwjrmqh4v6bhhkipg86zmhw8b-module-import-compiled.drv...
building 
/gnu/store/d53a8rwws8sjfyl55dzknr8w0ywpri1g-module-import-compiled.drv...
building 
/gnu/store/z9nsgksn1wv1p189sarxw2lp9d498bbv-compute-guix-derivation.drv...
substitute: updating substitutes from 'https://ci.guix.gnu.org'... 100.0%
substitute: updating substitutes from 'https://ci.guix.gnu.org'... 100.0%
 glibc-2.33  8.2MiB 5.6MiB/s 00:00 [
  ]   3.1%guix pull: error: You found a bug: the program 
'/gnu/store/7z9q1plaj7f0pa4znz350aa9qg969r80-compute-guix-derivation'
failed to compute the derivation for Guix (version: 
"386adb6df0e00e7170df0cdfaf0e04c38d0f3e11"; system: "x86_64-linux";
host version: "6417b97c7e10de8592ac9fda15774ee711d3dc25"; pull-version: 1).
Please report the COMPLETE output above by email to .


real9m20.124s
user4m28.800s
sys 0m2.990s

bug#54453: crash running 'guix pull'

[Peter Bhat Harkins]

Unfortunately, I have tried four or five times over the last three weeks
and always gotten this crash.




-- 
Peter Bhat Harkins - https://malaprop.org

bug#54453: crash running 'guix pull'

[Peter Bhat Harkins]

How much is required? I don't see it documented in the man page or manual.

bug#54453: crash running 'guix pull'

[Peter Bhat Harkins]

The VPS was created almost two years ago, and 'guix pull' was run many
times, though not in the last few months.

Is there documentation anywhere of what system resources a guix system,
or this particular command, requires? Is there any method for
estimating? It sounds like you're suggesting the requirements have
changed over time. Do running guix systems require more disk and RAM as
they age, or does this undocumented requirement also apply to new
systems?

At this point I'm less concerned about this individual crash bug and
more concerned that running any guix system is unsustainable.