bug#46795: [core-updates] emacs-websocket 1.13.1 build broken

[Danny Milosavljevic]

starting phase `make-autoloads'
Opening directory: No such file or directory, 
/gnu/store/pw8gf3cjcw9jxj7sjwz0z8cca5vkyvp8-emacs-stream-2.2.5/share/emacs/site-lisp
error: in phase 'make-autoloads': uncaught exception:
%exception #<&invoke-error program: 
"/gnu/store/rf22hzjvc63ybbzws27hjy39vsgh6r1c-emacs-minimal-27.1/bin/emacs" 
arguments: ("--quick" "--batch" "--eval=(eval '(let ((backup-inhibited t) 
(generated-autoload-file 
\"/gnu/store/pw8gf3cjcw9jxj7sjwz0z8cca5vkyvp8-emacs-stream-2.2.5/share/emacs/site-lisp/stream-autoloads.el\"))
 (update-directory-autoloads 
\"/gnu/store/pw8gf3cjcw9jxj7sjwz0z8cca5vkyvp8-emacs-stream-2.2.5/share/emacs/site-lisp\"))
 nil)") exit-status: 255 term-signal: #f stop-signal: #f> 
phase `make-autoloads' failed after 0.0 seconds
command 
"/gnu/store/rf22hzjvc63ybbzws27hjy39vsgh6r1c-emacs-minimal-27.1/bin/emacs" 
"--quick" "--batch" "--eval=(eval '(let ((backup-inhibited t) 
(generated-autoload-file 
\"/gnu/store/pw8gf3cjcw9jxj7sjwz0z8cca5vkyvp8-emacs-stream-2.2.5/share/emacs/site-lisp/stream-autoloads.el\"))
 (update-directory-autoloads 
\"/gnu/store/pw8gf3cjcw9jxj7sjwz0z8cca5vkyvp8-emacs-stream-2.2.5/share/emacs/site-lisp\"))
 nil)" failed with status 255


pgp4SlkujG1Dr.pgp
Description: OpenPGP digital signature

bug#46796: Cuirass & pointer finalization.

[Mathieu Othacehe]

Hello,

I'm trying to fix a memory corruption in the remote-server process of
Cuirass since a few days. Even though I don't have a usable core dump
file yet, I'm pretty sure the error comes from the "zmq-msg-init"
procedure of Guile-Simple-ZMQ.

This procedure creates a bytevector, call the C function zmq_msg_init to
initialize it, adds zmq_msg_close as pointer finalizer and returns a
wrapped pointer.

My understanding is that the wrapped pointer that is passed around in
Cuirass ensures that the underlying bytevector is not garbage collected
until the pointer goes out of scope. However, some assertions failures
such as this one:

--8<---cut here---start->8---
Assertion failed: check () (src/msg.cpp:394)
--8<---cut here---end--->8---

let me think that the bytevector is garbage collected, while ZMQ is
still using it. Some help would be much appreciated here :).

Thanks,

Mathieu

bug#46796: Cuirass & pointer finalization.

[zimoun]

Hi Mathieu,

I know nothing about the topic and I probably out-of-scope.

On Fri, 26 Feb 2021 at 15:14, Mathieu Othacehe  wrote:

> I'm trying to fix a memory corruption in the remote-server process of
> Cuirass since a few days. Even though I don't have a usable core dump
> file yet, I'm pretty sure the error comes from the "zmq-msg-init"
> procedure of Guile-Simple-ZMQ.
>
> This procedure creates a bytevector, call the C function zmq_msg_init to
> initialize it, adds zmq_msg_close as pointer finalizer and returns a
> wrapped pointer.
>
> My understanding is that the wrapped pointer that is passed around in
> Cuirass ensures that the underlying bytevector is not garbage collected
> until the pointer goes out of scope. However, some assertions failures
> such as this one:
>
> --8<---cut here---start->8---
> Assertion failed: check () (src/msg.cpp:394)
> --8<---cut here---end--->8---
>
> let me think that the bytevector is garbage collected, while ZMQ is
> still using it. Some help would be much appreciated here :).

>From ’zmq-msg-init’ defined here:



and why is ’zmq-message-content’ used for?  Since ’message’ is
initialized with zero, I guess.  Well, I am confused by:

--8<---cut here---start->8---
  (let ((content-ptr (zmq_msg_data (message->pointer message)))
[...]
(pointer->bytevector content-ptr size

…

(let ((msg (pointer->message! msg-pointer)))
  (when content-bv
(let ((target (zmq-message-content msg)))
  (bytevector-copy! content-bv 0 target 0 len)))
  msg
--8<---cut here---end--->8---

Is ’target’ at the same address than ’msg’?  Maybe ’target’ creates
somehow a dangling pointer.


Cheers,
simon

bug#46555: LVM swap continuously fails guix system: error: service 'swap-/dev/mapper/guix-swap' requires 'device-mapping-guix-swap', which is not provided by any service

[Shyam Saran]

Result of application of system build command

$ guix  system   build ~/tmp/config.scm

   2s
guix system: warning: the following groups appear more than once: users
guix system: error: service 'swap-/dev/mapper/guix-swap' requires
'device-mapping-guix-swap', which is not provided by any service


To be sure everything are correct

I had created lvm volume group guix and house
and their subvolume root, boot, var, gnu, swap, tmp (in guix) and home (in
house)


Result is the same, whether these volume groups were present or not.


Thanks


On Thu, 25 Feb 2021 at 18:49, Ludovic Courtès  wrote:

> Hi,
>
> Shyam Saran  skribis:
>
> > Thanks for response, I am attaching config.scm
>
> I get:
>
> --8<---cut here---start->8---
> $ guix system build /tmp/config.scm
> guix system: error: fiasko dum ŝargo de '/tmp/config.scm':
> /tmp/config.scm:277:58: In procedure append: Wrong type argument in
> position 1 (expecting empty list): #< device:
> "/dev/mapper/house-home" mount-point: "/home" type: "ext4" flags: ()
> options: #f mount?: #t mount-may-fail?: #f needed-for-boot?: #f check?: #f
> create-mount-point?: #t dependencies: (#< source:
> "/dev/sda31" targets: ("guix-root") type: #< open:
> # close: # close-non-udev-lvm-device (sources targets)> check: # 7f839682c5e0 at ice-9/boot-9.scm:803:2 _>> location: ((line . 133) (column
> . 52) (filename . "/tmp/config.scm"))> #< source:
> "/dev/sda31" targets: ("guix-boot") type: #< open:
> # close: # close-non-udev-lvm-device (sources targets)> check: # 7f839682c5e0 at ice-9/boot-9.scm:803:2 _>> location: ((line . 137) (column
> . 52) (filename . "/tmp/config.scm"))> #< source:
> "/dev/sda31" targets: ("guix-gnu") type: #< open:
> # close: # close-non-udev-lvm-device (sources targets)> check: # 7f839682c5e0 at ice-9/boot-9.scm:803:2 _>> location: ((line . 141) (column
> . 52) (filename . "/tmp/config.scm"))> #< source:
> "/dev/sda31" targets: ("guix-var") type: #< open:
> # close: # close-non-udev-lvm-device (sources targets)> check: # 7f839682c5e0 at ice-9/boot-9.scm:803:2 _>> location: ((line . 153) (column
> . 52) (filename . "/tmp/config.scm"))> #< source:
> "/dev/sda31" targets: ("guix-swap") type: #< open:
> # close: # close-non-udev-lvm-device (sources targets)> check: # 7f839682c5e0 at ice-9/boot-9.scm:803:2 _>> location: ((line . 145) (column
> . 52) (filename . "/tmp/config.scm"))> #< source:
> "/dev/sda31" targets: ("guix-tmp") type: #< open:
> # close: # close-non-udev-lvm-device (sources targets)> check: # 7f839682c5e0 at ice-9/boot-9.scm:803:2 _>> location: ((line . 149) (column
> . 52) (filename . "/tmp/config.scm"))> #< source:
> "/dev/test" targets: ("house-home") type: #< open:
> # close: # close-non-udev-lvm-device (sources targets)> check: # 7f839682c5e0 at ice-9/boot-9.scm:803:2 _>> location: ((line . 157) (column
> . 52) (filename . "/tmp/config.scm"))>) location: ((line . 233) (column .
> 50) (filename . "/tmp/config.scm"))>
> --8<---cut here---end--->8---
>
> Could you make sure the file passes ‘guix system build’?
>
> TIA,
> Ludo’.
>
;; This is an operating system configuration generated

(use-modules (guix utils))
(use-modules (guix packages))
(use-modules (gnu services networking))
(use-modules (gnu services audio))
(use-modules (gnu) (gnu system nss))
(use-service-modules networking ssh)
(use-package-modules bootloaders certs suckless wm)

(use-service-modules desktop networking cups ssh xorg avahi mail)
(use-package-modules certs gnome cups)

(use-modules (gnu packages shells))
(use-modules (gnu packages vim))

(use-modules (gnu))
(use-package-modules screen)

;; other guix

(use-modules (gnu system locale))
(use-modules (guix store))
(use-modules (rnrs lists))
(use-modules (srfi srfi-1))
(use-package-modules base idutils)
(use-service-modules dns mcron messaging)


(define %local-fs-boot-efi-partition "/dev/sda1")

(define %local-grub-ubuntu-menuentries (list (menu-entry (label "Ubuntu GNU/Linux")
 (linux "(lvm/tf1e5mXubuntu-boot)/vmlinuz")
 (linux-arguments '("root=/dev/mapper/tf1e5mXubuntu-root ro --verbose nosplash debug"))
 (initrd "(lvm/tf1e5mXubuntu-boot)/initrd.img"


(define %localmachine-host-name "komputilo")
(define %localmachine-account-uid   1000)
(define %localmachine-account-user-name "s")
(define %localmachine-account-comment   "shyam")
(define %localmachine-account-group-name"users")
(define %localmachine-account-group-gid  1000)
(define %localmachine-account-supplementry-groups   '("wheel" "netdev" "audio" "video"))
(define %localmachine-account-home-parent-directory "/home")
(define %localmachine-account-shell #~(string-append #$zsh "/bin/zsh"))
(define %localmachine-gdm-

bug#46803: User manual does not explain Profiles (nor GUIX_PROFILE)

[Luis Felipe via Bug reports for GNU Guix]

The Guix reference manual does not seem to explain what profiles are.


## Steps to reproduce

Assuming you are browsing the Guix reference manual in Info:

1. Type i (to search for an index topic).
2. Type the word profile and hit Enter.
3. Type , repeatedly to explore all the parts of the manual related to profiles.


## Expected result

At some point, I get to a section defining what is a profile exactly, a profile 
of what, what can I get from using one or many of them, what is the 
GUIX_PROFILE variable, does it accept a single path to a profile or more, and 
some use cases and examples.


## Unexpected result

I see profiles are mentioned in places where they can be used, but the text 
assumes I know what a profile is.

Similarly, the GUIX_PROFILE variable doesn't seem to be defined. It seems 
missing from the concept and programming indices.


## Additional information

The "Guix Profiles in Practice" recipe in the cookbook defines profiles to some 
extent. Maybe some of this information can be used in the manual?


---
Luis Felipe López Acevedo
https://luis-felipe.gitlab.io/

bug#46650: Extending package transformation options

[zimoun]

Hi,

On Wed, 24 Feb 2021 at 18:21, Ludovic Courtès  wrote:

>> So here, a transformation could be applied.  For example, build all
>> the dependencies without testing them;  at the 'define gnutls' (&co)
>> step or in the map.  Why not?
>
> Sure, but how do you get a user-specified transformation to this line?

I do not know (yet?). :-)

First, we are only speaking about “guix time-machine” and second, only
about corner cases which could break in the future, as expiration.
Right?
We are not talking about general transformations applied to self (even
if it could be great).

So we could imagine something like ’set-build-from-command-line’ or
’set-build-option’ to tweak self only for the inferior.  I have not
traced (yet) on the stack of calls from “guix time-machine” to self via
the inferiors, but somehow it looks like passing arguments.

Well, be able to tweak how to build Guix via the time-machine appears to
me better than configuring a build machine ahead of time.  It is like
predicting the future and instead we should try to have a flexible
present in order to fix the past once in the unpredictable future. :-)


Cheers,
simon

bug#46780: java-snappy: Test failure on ci.guix.gnu.org

[zimoun]

Hi,

On Thu, 25 Feb 2021 at 21:52, Björn Höfling  
wrote:

> Then increase the memory used by junit: Edit the build.xml file, add a
> huge "maxmemory" property like this :
>
>  If you look at the test case source code, it tries to allocate about
> 20GB and hopes that this fails. It just does not fail on huge machines...

What about adding a phase just before the test?  For example in this
build.xml file fix the max memory to 20G if it is greater.


All the best,
simon

bug#46803: User manual does not explain Profiles (nor GUIX_PROFILE)

[Tobias Geerinckx-Rice via Bug reports for GNU Guix]

Luis Felipe,

I think that would be very helpful.  I'm trying to think of a 
concise, correct, but actually useful definition of profiles for 
someone not already familiar with them or Guix.


Out of curiosity: how do you intuitively understand profiles, as 
someone who's used Guix for a while?


Luis Felipe via Bug reports for GNU Guix 写道：

[...] what is the GUIX_PROFILE variable, does it accept a single
path to a profile or more, and some use cases and 
examples. [...]


I don't think we should document GUIX_PROFILE.  It's not part of 
the definition of Guix profiles.  It should not matter to users 
nor should they rely on previously observed behaviour.  AIUI there 
are no supported ‘use cases’, beyond copy-pasting Guix error 
messages...


Similarly, the GUIX_PROFILE variable doesn't seem to be 
defined. It seems missing from the concept and programming 
indices.


...so this part isn't unexpected.

Kind regards,

T G-R


signature.asc
Description: PGP signature

bug#41669: Cross-compiled powerpc64-linux bootstrap-tarballs not reproducible

[Chris Marusich]

Hi,

Chris Marusich  writes:

> Going forward, I'm not sure how best to investigate the inputs to find
> out what's causing the differences.  I just know I really, really,
> really don't want to rebuild everything multiple times, since it takes
> hours/days.  If you have any creative ideas for how to speed up the
> investigation, I'm all ears.

I've analyzed the graph of derivations that produce differing output
across machines.  Here's an image of the graph:


And here is the GraphViz source, which you can render however you want:

digraph "Differing Derivations" {

"/gnu/store/07bd5ll0adnyrv1zaz11vz2x1ax447ka-glibc-mesboot-2.16.0.drv" [label = "glibc-mesboot-2.16.0", shape = box, fontname = sans]
"/gnu/store/0zkiqxwm6k637xr5s1690nwllnvybvyw-xz-mesboot-5.0.0.drv" [label = "xz-mesboot-5.0.0", shape = box, fontname = sans]
"/gnu/store/2pziz2j7781mhadl8lcfpzm8anvazb37-binutils-mesboot-2.20.1a.drv" [label = "binutils-mesboot-2.20.1a", shape = box, fontname = sans]
"/gnu/store/4ji6ayrgcyfyxpb583qr5ja4awdlxrdc-bootar-1a.drv" [label = "bootar-1a", shape = box, fontname = sans]
"/gnu/store/5x8a1yib7vdza727vrq4zmp6cmsafy7h-module-import-compiled.drv" [label = "module-import-compiled-1", shape = box, fontname = sans]
"/gnu/store/agday74gvxnd6a7191fw2g473b5v66kx-gcc-mesboot1-4.6.4.drv" [label = "gcc-mesboot1-4.6.4", shape = box, fontname = sans]
"/gnu/store/alvrmh47xqk7glq9wmvrzivfjp2bcvyc-module-import-compiled.drv" [label = "module-import-compiled-2", shape = box, fontname = sans]
"/gnu/store/asnd815v865cvfh2l2dlxmh5y556v3i5-gcc-core-mesboot0-2.95.3.drv" [label = "gcc-core-mesboot0-2.95.3", shape = box, fontname = sans]
"/gnu/store/bjhkfxc5axkjl1jv94q0lwym4n6si6f8-gcc-4.9.4.tar.xz.drv" [label = "gcc-4.9.4.tar.xz", shape = box, fontname = sans]
"/gnu/store/cf3m3ddm8dicrsxba4kjnji5lbyagvbk-gcc-mesboot0-2.95.3.drv" [label = "gcc-mesboot0-2.95.3", shape = box, fontname = sans]
"/gnu/store/d1g7i2w8k1g5jrx4n6xv4q8xnrlmz8f3-module-import-compiled.drv" [label = "module-import-compiled-3", shape = box, fontname = sans]
"/gnu/store/fdmz5blhzfczkpjb9jj6bdbhqlpv3i7l-gcc-7.5.0.drv" [label = "gcc-7.5.0", shape = box, fontname = sans]
"/gnu/store/fs2r7irjx7ppqks3zhsqmxb8lah1a4v0-glibc-mesboot0-2.2.5.drv" [label = "glibc-mesboot0-2.2.5", shape = box, fontname = sans]
"/gnu/store/i5wn3xl6p0zw1vglscgk0bs9dwc6hdh6-gcc-static-5.5.0.drv" [label = "gcc-static-5.5.0", shape = box, fontname = sans]
"/gnu/store/imx7vf2qg44yg9i4gsbn5bgpj3crcyr8-gcc-7.5.0.tar.xz.drv" [label = "gcc-7.5.0.tar.xz", shape = box, fontname = sans]
"/gnu/store/lhhbpfhk2xm8znvhnbrig8dfgd9xc80k-libstdc++-7.5.0.drv" [label = "libstdc++-7.5.0", shape = box, fontname = sans]
"/gnu/store/mrsasf73k1yvdcbn1wyb4ad6dk7ns3vn-binutils-mesboot1-2.14.drv" [label = "binutils-mesboot1-2.14", shape = box, fontname = sans]
"/gnu/store/wxpvfy5g3xjl0kp85cmmy66057p88kln-binutils-cross-boot0-2.34.drv" [label = "binutils-cross-boot0-2.34", shape = box, fontname = sans]
"/gnu/store/y4g2gsdxbk2kmp7lih88kdndi7868dnl-gash-utils-boot-0.1.0.drv" [label = "gash-utils-boot-0.1.0", shape = box, fontname = sans]
"/gnu/store/yz7h0nf33465a32yjpm9rh6w9959h34q-gcc-mesboot-4.9.4.drv" [label = "gcc-mesboot-4.9.4", shape = box, fontname = sans]
"/gnu/store/zf6himkd5rz2ll8ym0c2488bgpnkjkkr-gash-boot-0.2.0.drv" [label = "gash-boot-0.2.0", shape = box, fontname = sans]

"/gnu/store/i5wn3xl6p0zw1vglscgk0bs9dwc6hdh6-gcc-static-5.5.0.drv" -> "/gnu/store/fdmz5blhzfczkpjb9jj6bdbhqlpv3i7l-gcc-7.5.0.drv"
"/gnu/store/fdmz5blhzfczkpjb9jj6bdbhqlpv3i7l-gcc-7.5.0.drv" -> "/gnu/store/0zkiqxwm6k637xr5s1690nwllnvybvyw-xz-mesboot-5.0.0.drv"
"/gnu/store/fdmz5blhzfczkpjb9jj6bdbhqlpv3i7l-gcc-7.5.0.drv" -> "/gnu/store/d1g7i2w8k1g5jrx4n6xv4q8xnrlmz8f3-module-import-compiled.drv"
"/gnu/store/fdmz5blhzfczkpjb9jj6bdbhqlpv3i7l-gcc-7.5.0.drv" -> "/gnu/store/imx7vf2qg44yg9i4gsbn5bgpj3crcyr8-gcc-7.5.0.tar.xz.drv"
"/gnu/store/fdmz5blhzfczkpjb9jj6bdbhqlpv3i7l-gcc-7.5.0.drv" -> "/gnu/store/lhhbpfhk2xm8znvhnbrig8dfgd9xc80k-libstdc++-7.5.0.drv"
"/gnu/store/fdmz5blhzfczkpjb9jj6bdbhqlpv3i7l-gcc-7.5.0.drv" -> "/gnu/store/wxpvfy5g3xjl0kp85cmmy66057p88kln-binutils-cross-boot0-2.34.drv"
"/gnu/store/0zkiqxwm6k637xr5s1690nwllnvybvyw-xz-mesboot-5.0.0.drv" -> "/gnu/store/agday74gvxnd6a7191fw2g473b5v66kx-gcc-mesboot1-4.6.4.drv"
"/gnu/store/0zkiqxwm6k637xr5s1690nwllnvybvyw-xz-mesboot-5.0.0.drv" -> "/gnu/store/d1g7i2w8k1g5jrx4n6xv4q8xnrlmz8f3-module-import-compiled.drv"
"/gnu/store/0zkiqxwm6k637xr5s1690nwllnvybvyw-xz-mesboot-5.0.0.drv" -> "/gnu/store/fs2r7irjx7ppqks3zhsqmxb8lah1a4v0-glibc-mesboot0-2.2.5.drv"
"/gnu/store/0zkiqxwm6k637xr5s1690nwllnvybvyw-xz-mesboot-5.0.0.drv" -> "/gnu/store/mrsasf73k1yvdcbn1wyb4ad6dk7ns3vn-binutils-mesboot1-2.14.drv"
"/gnu/store/agday74gvxnd6a7191fw2g473b5v66kx-gcc-mesboot1-4.6.4.drv" -> "/gnu/store/cf3m3ddm8dicrsxba4kjnji5lbyagvbk-gcc-mesboot0-2.95.3.drv"
"/gnu/store/agday74gvxnd6a7191fw2g473b5v66kx-gcc-mesboot1-4.6.4.drv" -> "/gnu/store/d1g7i2w8k1g5jrx4n6xv4q8xnrlmz8f3-module-import-compiled.drv"
"/gnu/store/agday74gv