bug#68411: Timezone not detected from /etc/localtime

[Maxim Cournoyer]

Hi,

Distopico  writes:

> Apps such as Icecat or ungoogled-chromium are not able to get the
> correct timezone from /etc/localtime when `/etc/localtime` is a realpath
> maybe because it expect /etc/share/zoneinfo, with readlink partially
> works fine some apps, maybe related with an icu bug.[1]

I don't know about ungoogled-chromium, but for IceCat, I had
investigated the problem at length in https://issues.guix.gnu.org/59368,
and it seems the bug is not in ICU but in Firefox, triggered in very
specific situations (resistFingerprinting defaults to true before user
prefs are loaded, and resetting the timezone fails in some javascript
that expects /etc/localtime to be a symlink, see:
https://bugzilla.mozilla.org/show_bug.cgi?id=1817004#c8).

-- 
Thanks,
Maxim

bug#68399: GnuTLS fails to build for aarch64 in QEMU

[Maxim Cournoyer]

Hi,

Lars Rustand  writes:

[...]

> --- ./src/gl/tests/test-suite.log ---
>
> ===
>GnuTLS 3.8.2: src/gl/tests/test-suite.log
> ===
>
> # TOTAL: 167
> # PASS:  166
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
>
> .. contents:: :depth: 2
>
> FAIL: test-free
> ===
>
> qemu-aarch64: ../../linux-user/mmap.c:801: mmap_reserve_or_unmap: Assertion 
> `ret == 0' failed.
> **
> ERROR:../../accel/tcg/cpu-exec.c:532:cpu_exec_longjmp_cleanup: assertion 
> failed: (cpu == current_cpu)
> Bail out! ERROR:../../accel/tcg/cpu-exec.c:532:cpu_exec_longjmp_cleanup: 
> assertion failed: (cpu == current_cpu)
> FAIL test-free (exit status: 127)


That one looks like a probable discrepancy due to QEMU emulation more
than a bug in GnuTLS.

On the other hand, we can see from our CI that an aarch64-linux (actual
hardware) build also failed with:

--8<---cut here---start->8---
FAIL: tls13-resume-x509
===

client:668: *** Previous session was NOT resumed
try to resume from session ticket (different cipher order)
server:911: server: session_is_resumed error (1)
try to resume from session ticket (different cipher order)
FAIL tls13-resume-x509 (exit status: 1)

FAIL: tls13-early-data
==

client:472: client: max_early_data_size mismatch -1 != 1024
server:692: server: Handshake has failed (The TLS connection was non-properly 
terminated.)

FAIL tls13-early-data (exit status: 1)

[...]

FAIL: dtls-repro-20170915
=

negotiating DTLS 1.2 with cli-cert
client: Resource temporarily unavailable, try again.
server: The operation timed out
dtls_try_with_key_mtu:578: Handshake failed
FAIL dtls-repro-20170915 (exit status: 1)

FAIL: resume-with-stek-expiration
=


testing tls1.2 resumption

STEK was rotated!
client: Handshake was completed
client: Success: Session was NOT resumed
server: Handshake was completed
server: Success: Session was NOT resumed
STEK was rotated!
client: Handshake was completed
client: Success: Session was resumed
server: Handshake was completed
server: Success: Session was resumed
STEK was rotated!
client: Handshake was completed
client: Success: Session was resumed
server: Handshake was completed
server: Success: Session was resumed
STEK was rotated!
client: Handshake was completed
client: Success: Session was NOT resumed
server: Handshake was completed
server: Success: Session was NOT resumed

testing tls1.3 resumption

client: Handshake was completed
client: Success: Session was NOT resumed
STEK was rotated!
server: Handshake was completed
server: Success: Session was NOT resumed
client: Handshake was completed
resume_and_close:140: client: Session was not resumed (but should)
STEK was rotated!
server:253: server: Handshake failed: Error in the push function.
FAIL resume-with-stek-expiration (exit status: 1)
--8<---cut here---end--->8---

See: https://ci.guix.gnu.org/build/3170604/details

We should check whether upstream is already tracking these failures and
disable the tests in the meantime in our package of QEMU for this
architecture.

-- 
Thanks,
Maxim

bug#67565: (No Subject)

[Attila Lendvai]

> hrm, i tried to reproduce it just now on the same machine, and i couldn't.

it has happened again, i'm attaching another log file.

this log file is with my shepherd branch, i.e. it contains much more log.

the error:

+ test 4 -eq 6

HTH,

-- 
• attila lendvai
• PGP: 963F 5D5F 45C7 DFCD 0A39
--
“I don't trust a man who talks about ethics when he is picking my pocket. But 
if he is acting in his own self-interest and says so, I have usually been able 
to work out some way to do business with him.”
— Robert Heinlein (1907–1988), 'Time Enough For Love' (1973)
+ shepherd --version
shepherd (GNU Shepherd) 0.10.3
Copyright (C) 2024 the Shepherd authors
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
+ herd --version
herd (GNU Shepherd) 0.10.3
Copyright (C) 2024 the Shepherd authors
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
+ socket=t-socket-11858
+ conf=t-conf-11858
+ log=t-log-11858
+ pid=t-pid-11858
+ c_file=t-count-file-descriptors-11858.c
+ exe=/home/alendvai/workspace/guix/shepherd/t-count-file-descriptors-11858
+ fd_count=/home/alendvai/workspace/guix/shepherd/t-fd-count-11858
+ herd='herd -s t-socket-11858'
+ trap 'cat t-log-11858 || true; rm -f t-socket-11858 t-conf-11858 t-log-11858 /home/alendvai/workspace/guix/shepherd/t-fd-count-11858 t-count-file-descriptors-11858.c /home/alendvai/workspace/guix/shepherd/t-count-file-descriptors-11858;
  test -f t-pid-11858 && kill `cat t-pid-11858` || true; rm -f t-pid-11858' EXIT
+ '[' -d /proc/self/fd ']'
+ cat
+ gcc -Wall t-count-file-descriptors-11858.c -o /home/alendvai/workspace/guix/shepherd/t-count-file-descriptors-11858
+ /home/alendvai/workspace/guix/shepherd/t-count-file-descriptors-11858
0 -> /dev/pts/0
1 -> /home/alendvai/workspace/guix/shepherd/tests/close-on-exec.log
2 -> /home/alendvai/workspace/guix/shepherd/tests/close-on-exec.log
3 -> /proc/11890/fd
15 -> /gnu/store/l0y8jkmip7qpa7x33972mn0dsfy8ac01-libffi-3.4.4/lib/libffi.so.8.1.2
+ cat
++ type -P sleep
+ rm -f t-pid-11858 /home/alendvai/workspace/guix/shepherd/t-fd-count-11858
+ test -f t-pid-11858
+ sleep 0.3
+ shepherd -I -s t-socket-11858 -c t-conf-11858 -l t-log-11858 --pid=t-pid-11858
Starting service root...
Service root started.
Service root running with value #t.
Service root has been started.
Configuration successfully loaded from 't-conf-11858'.
+ test -f t-pid-11858
++ cat t-pid-11858
+ shepherd_pid=11894
+ kill -0 11894
+ herd -s t-socket-11858 start inetd-ctor
Starting service inetd-ctor...
Service inetd-ctor started.
Service inetd-ctor running with value (#).
Service inetd-ctor has been started.
+ ls -l /proc/11894/fd
total 0
lr-x-- 1 alendvai users 64 Jan 19 00:06 0 -> /dev/null
l-wx-- 1 alendvai users 64 Jan 19 00:06 1 -> /home/alendvai/workspace/guix/shepherd/tests/close-on-exec.log
lrwx-- 1 alendvai users 64 Jan 19 00:06 10 -> anon_inode:[signalfd]
lr-x-- 1 alendvai users 64 Jan 19 00:06 11 -> pipe:[7007304]
l-wx-- 1 alendvai users 64 Jan 19 00:06 12 -> pipe:[7007304]
lr-x-- 1 alendvai users 64 Jan 19 00:06 13 -> pipe:[7005516]
l-wx-- 1 alendvai users 64 Jan 19 00:06 14 -> pipe:[7005516]
lr-x-- 1 alendvai users 64 Jan 19 00:06 15 -> /gnu/store/l0y8jkmip7qpa7x33972mn0dsfy8ac01-libffi-3.4.4/lib/libffi.so.8.1.2
lr-x-- 1 alendvai users 64 Jan 19 00:06 16 -> pipe:[7005517]
l-wx-- 1 alendvai users 64 Jan 19 00:06 17 -> pipe:[7005517]
lr-x-- 1 alendvai users 64 Jan 19 00:06 18 -> pipe:[7003504]
l-wx-- 1 alendvai users 64 Jan 19 00:06 19 -> pipe:[7003504]
l-wx-- 1 alendvai users 64 Jan 19 00:06 2 -> /home/alendvai/workspace/guix/shepherd/tests/close-on-exec.log
lrwx-- 1 alendvai users 64 Jan 19 00:06 20 -> socket:[7007305]
lrwx-- 1 alendvai users 64 Jan 19 00:06 22 -> socket:[7007310]
lr-x-- 1 alendvai users 64 Jan 19 00:06 3 -> pipe:[7007301]
l-wx-- 1 alendvai users 64 Jan 19 00:06 4 -> pipe:[7007301]
lr-x-- 1 alendvai users 64 Jan 19 00:06 5 -> /home/alendvai/workspace/guix/shepherd/shepherd
l-wx-- 1 alendvai users 64 Jan 19 00:06 6 -> /home/alendvai/workspace/guix/shepherd/t-log-11858
lr-x-- 1 alendvai users 64 Jan 19 00:06 7 -> pipe:[7007303]
l-wx-- 1 alendvai users 64 Jan 19 00:06 8 -> pipe:[7007303]
lrwx-- 1 alendvai users 64 Jan 19 00:06 9 -> anon_inode:[eventpoll]
+ herd -s t-socket-11858 start system-ctor
Starting service system-ctor...
Service system-ctor has been started.
+ herd -s t-socket-11858 status system-ctor
Status of system-ctor:
  It is stopped (one-shot).
  It is enabled.
  Provides (system-ctor).
  Requires ().
  Will not be respawned.
+ test -f /home/alendvai/workspace/guix/shepherd/t-fd-count-11858
++ cat /home/alendvai/workspace/guix/shepherd/t-fd-count-1185

bug#68333: Time bomb in icedtea/openjdk

[Simon Tournier]

Hi,

Thanks all for the quick fix.

Well, I am asking here but maybe such discussion would deserve its own
thread on guix-devel. :-)

On mer., 10 janv. 2024 at 15:35, Ludovic Courtès  wrote:

> Thanks for the quick investigation and patch!  I just realized that this
> affects current ‘master’ so we’d rather fix it soon.
>
> What do you think of the attached patch?  The difference is that it
> patches code at its root (in the actual source tarball rather than after
> it’s been copied), it does so for IcedTea 7 and 8, and there are patch
> files that are slightly clearer than a substitution pattern.

This fixes the future but not the past.  Hum, headache with guix
time-machine?  :-)

The question is twofold:

 1. Do we document that some Java stack is broken for “guix
time-machine”?  Other said, have we an evaluation about which Guix
revisions are broken for the stack of Java?

 2. Do we provide a “transformation” for fixing such break?  Something
that rewrite on the fly the origin for patching it; accessible only
via manifest.

WDYT?

Cheers,
simon

bug#68561: Guix wrongfully claims there is no space left

[Christopher Baines]

Lars Rustand  writes:

> Guix is claiming that there is no space left on the device when none of
> my devices are in fact full. As you can see from the output of df -h
> there is more than enough space on all filesystems:
>
>
> Filesystem  Size  Used Avail Use% Mounted on
> none7.8G 0  7.8G   0% /dev
> /dev/nvme0n1p7  250G  159G   79G  67% /
> /dev/nvme0n1p1  2.0G  428K  2.0G   1% /boot/efi
> tmpfs   7.8G  281M  7.5G   4% /dev/shm
> efivarfs184K  137K   43K  77% /sys/firmware/efi/efivars
> none7.8G   24K  7.8G   1% /run/systemd
> none7.8G 0  7.8G   0% /run/user
> tmpfs   1.6G  8.0K  1.6G   1% /run/user/1000

Check df -i, it could be that some filesystem has run out of inodes.


signature.asc
Description: PGP signature

bug#68561: Guix wrongfully claims there is no space left

[Lars Rustand]

Guix is claiming that there is no space left on the device when none of
my devices are in fact full. As you can see from the output of df -h
there is more than enough space on all filesystems:


Filesystem  Size  Used Avail Use% Mounted on
none7.8G 0  7.8G   0% /dev
/dev/nvme0n1p7  250G  159G   79G  67% /
/dev/nvme0n1p1  2.0G  428K  2.0G   1% /boot/efi
tmpfs   7.8G  281M  7.5G   4% /dev/shm
efivarfs184K  137K   43K  77% /sys/firmware/efi/efivars
none7.8G   24K  7.8G   1% /run/systemd
none7.8G 0  7.8G   0% /run/user
tmpfs   1.6G  8.0K  1.6G   1% /run/user/1000


This is the build output from Guix when trying to reconfigure my home:


warning: collision encountered:
  
/gnu/store/wjfh1v15yyv1wka7qin62xb0s7m467nd-gst-plugins-bad-1.22.2/lib/pkgconfig/gstreamer-cuda-1.0.pc
  
/gnu/store/yphrrwp56dba70p5y0bjj53r0krlpsd5-gst-plugins-bad-minimal-1.22.2/lib/pkgconfig/gstreamer-cuda-1.0.pc
warning: choosing 
/gnu/store/wjfh1v15yyv1wka7qin62xb0s7m467nd-gst-plugins-bad-1.22.2/lib/pkgconfig/gstreamer-cuda-1.0.pc

warning: collision encountered:
  
/gnu/store/wjfh1v15yyv1wka7qin62xb0s7m467nd-gst-plugins-bad-1.22.2/lib/pkgconfig/gstreamer-va-1.0.pc
  
/gnu/store/yphrrwp56dba70p5y0bjj53r0krlpsd5-gst-plugins-bad-minimal-1.22.2/lib/pkgconfig/gstreamer-va-1.0.pc
warning: choosing 
/gnu/store/wjfh1v15yyv1wka7qin62xb0s7m467nd-gst-plugins-bad-1.22.2/lib/pkgconfig/gstreamer-va-1.0.pc

warning: collision encountered:
  
/gnu/store/wjfh1v15yyv1wka7qin62xb0s7m467nd-gst-plugins-bad-1.22.2/lib/pkgconfig/gstreamer-bad-audio-1.0.pc
  
/gnu/store/yphrrwp56dba70p5y0bjj53r0krlpsd5-gst-plugins-bad-minimal-1.22.2/lib/pkgconfig/gstreamer-bad-audio-1.0.pc
warning: choosing 
/gnu/store/wjfh1v15yyv1wka7qin62xb0s7m467nd-gst-plugins-bad-1.22.2/lib/pkgconfig/gstreamer-bad-audio-1.0.pc

warning: collision encountered:
  
/gnu/store/wjfh1v15yyv1wka7qin62xb0s7m467nd-gst-plugins-bad-1.22.2/lib/pkgconfig/gstreamer-insertbin-1.0.pc
  
/gnu/store/yphrrwp56dba70p5y0bjj53r0krlpsd5-gst-plugins-bad-minimal-1.22.2/lib/pkgconfig/gstreamer-insertbin-1.0.pc
warning: choosing 
/gnu/store/wjfh1v15yyv1wka7qin62xb0s7m467nd-gst-plugins-bad-1.22.2/lib/pkgconfig/gstreamer-insertbin-1.0.pc

warning: collision encountered:
  
/gnu/store/wjfh1v15yyv1wka7qin62xb0s7m467nd-gst-plugins-bad-1.22.2/lib/pkgconfig/gstreamer-transcoder-1.0.pc
  
/gnu/store/yphrrwp56dba70p5y0bjj53r0krlpsd5-gst-plugins-bad-minimal-1.22.2/lib/pkgconfig/gstreamer-transcoder-1.0.pc
warning: choosing 
/gnu/store/wjfh1v15yyv1wka7qin62xb0s7m467nd-gst-plugins-bad-1.22.2/lib/pkgconfig/gstreamer-transcoder-1.0.pc

warning: collision encountered:
  
/gnu/store/wjfh1v15yyv1wka7qin62xb0s7m467nd-gst-plugins-bad-1.22.2/lib/pkgconfig/gstreamer-player-1.0.pc
  
/gnu/store/yphrrwp56dba70p5y0bjj53r0krlpsd5-gst-plugins-bad-minimal-1.22.2/lib/pkgconfig/gstreamer-player-1.0.pc
warning: choosing 
/gnu/store/wjfh1v15yyv1wka7qin62xb0s7m467nd-gst-plugins-bad-1.22.2/lib/pkgconfig/gstreamer-player-1.0.pc

warning: collision encountered:
  
/gnu/store/wjfh1v15yyv1wka7qin62xb0s7m467nd-gst-plugins-bad-1.22.2/lib/pkgconfig/gstreamer-sctp-1.0.pc
  
/gnu/store/yphrrwp56dba70p5y0bjj53r0krlpsd5-gst-plugins-bad-minimal-1.22.2/lib/pkgconfig/gstreamer-sctp-1.0.pc
warning: choosing 
/gnu/store/wjfh1v15yyv1wka7qin62xb0s7m467nd-gst-plugins-bad-1.22.2/lib/pkgconfig/gstreamer-sctp-1.0.pc

warning: collision encountered:
  
/gnu/store/wjfh1v15yyv1wka7qin62xb0s7m467nd-gst-plugins-bad-1.22.2/lib/pkgconfig/gstreamer-webrtc-1.0.pc
  
/gnu/store/yphrrwp56dba70p5y0bjj53r0krlpsd5-gst-plugins-bad-minimal-1.22.2/lib/pkgconfig/gstreamer-webrtc-1.0.pc
warning: choosing 
/gnu/store/wjfh1v15yyv1wka7qin62xb0s7m467nd-gst-plugins-bad-1.22.2/lib/pkgconfig/gstreamer-webrtc-1.0.pc

warning: collision encountered:
  
/gnu/store/wjfh1v15yyv1wka7qin62xb0s7m467nd-gst-plugins-bad-1.22.2/lib/pkgconfig/gstreamer-photography-1.0.pc
  
/gnu/store/yphrrwp56dba70p5y0bjj53r0krlpsd5-gst-plugins-bad-minimal-1.22.2/lib/pkgconfig/gstreamer-photography-1.0.pc
warning: choosing 
/gnu/store/wjfh1v15yyv1wka7qin62xb0s7m467nd-gst-plugins-bad-1.22.2/lib/pkgconfig/gstreamer-photography-1.0.pc

warning: collision encountered:
  
/gnu/store/wjfh1v15yyv1wka7qin62xb0s7m467nd-gst-plugins-bad-1.22.2/lib/pkgconfig/gstreamer-codecparsers-1.0.pc
  
/gnu/store/yphrrwp56dba70p5y0bjj53r0krlpsd5-gst-plugins-bad-minimal-1.22.2/lib/pkgconfig/gstreamer-codecparsers-1.0.pc
warning: choosing 
/gnu/store/wjfh1v15yyv1wka7qin62xb0s7m467nd-gst-plugins-bad-1.22.2/lib/pkgconfig/gstreamer-codecparsers-1.0.pc

warning: collision encountered:
  
/gnu/store/wjfh1v15yyv1wka7qin62xb0s7m467nd-gst-plugins-bad-1.22.2/lib/pkgconfig/gstreamer-plugins-bad-1.0.pc
  
/gnu/store/yphrrwp56dba70p5y0bjj53r0krlpsd5-gst-plugins-bad-minimal-1.22.2/lib/pkgconfig/gstreamer-plugins-bad-1.0.pc
warning: choosing 
/gnu/store/wjfh1v15yyv1wka7qin62xb0s7m467nd-gst-plugins-bad-1.22.2/lib/pkgconfig/gstreamer-plugins-bad-1.0.pc

warning: collision encountered:
  
/gnu