Libgcrypt warning: missing initialization

  • Open
  • quality assurance status badge
Details
2 participants
  • Hartmut Goebel
  • Ludovic Courtès
Owner
unassigned
Submitted by
Hartmut Goebel
Severity
normal
H
H
Hartmut Goebel wrote on 4 Oct 2019 10:16
(name . bug-guix)(address . bug-guix@gnu.org)
607208a9-67e0-f81f-5c2d-a23104223c9b@crazy-compilers.com
Hi,

the system logs for guix show this error:

guile: Libgcrypt warning: missing initialization - please fix the
application

Full log:

systemd[1]: Started Build daemon for GNU Guix.
guix-daemon[28968]: accepted connection from pid 28973, user nobody
guix-daemon[28968]: accepted connection from pid 28990, user hartmut
guix-daemon[28968]: spurious SIGPOLL
guile[28999]: Libgcrypt warning: missing initialization - please fix the
application
guix-daemon[28968]: SIGPOLL
guix-daemon[28968]: unexpected build daemon error: interrupted by the user

Build like this:

$ su -
# guix environment guix
# guix pull -commit=ccbc1c5eb2
# guix package --fallback -u
# grep ExecStart= /etc/systemd/system/guix-daemon.service
ExecStart=/usr/local/sbin/guix-daemon --build-users-group=guixbuild
--substitute-urls="https://ci.guix.gnu.org"
# /usr/local/sbin/guix-daemon --version
guix-daemon (GNU Guix) 1.0.1-6.0ed97e6

--
Regards
Hartmut Goebel

| Hartmut Goebel | h.goebel@crazy-compilers.com |
| www.crazy-compilers.com | compilers which you thought are impossible |
L
L
Ludovic Courtès wrote on 2 Dec 2019 18:36
(name . Hartmut Goebel)(address . h.goebel@crazy-compilers.com)(address . 37616@debbugs.gnu.org)
877e3ek4tr.fsf@gnu.org
Hi,

Hartmut Goebel <h.goebel@crazy-compilers.com> skribis:

Toggle quote (5 lines)
> the system logs for guix show this error:
>
> guile: Libgcrypt warning: missing initialization - please fix the
> application

This is now fixed in Guile-Gcrypt commit
bdff239141f2359fd35211ff0efd0e36829b257d (the warning turns out to be
harmless, though.)

I’ll push a 0.2.1 release soonish.

Thanks,
Ludo’.
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 37616@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 37616
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch