From: <znavko@tutanota.com>
To: 33557@debbugs.gnu.org
Subject: bug#33557: guix errors, if you want
Date: Fri, 30 Nov 2018 12:48:27 +0100 (CET) [thread overview]
Message-ID: <LSZRh4N--3-1@tutanota.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2447 bytes --]
Dear, Guix Bug! This is not fatal, but if you want here what I've seen while update. How to react on warnings and fails?
#guix pull
guix ...2f24b9c...
...
ion-record-port'
;;; Failed to autoload make-session in (gnutls):
;;; missing interface for module (gnutls)
;;; Failed to autoload make-session in (gnutls):
;;; missing interface for module (gnutls)
;;; Failed to autoload connection-end/client in (gnutls):
;;; missing interface for module (gnutls)
;;; guix/discovery.scm:90:22: warning: non-literal format string
;;; guix/profiles.scm:1629:20: warning: non-literal format string
;;; guix/profiles.scm:1635:20: warning: non-literal format string
;;; guix/profiles.scm:1644:16: warning: non-literal format string
;;; guix/profiles.scm:1648:16: warning: non-literal format string
;;; guix/ui.scm:175:5: warning: non-literal format string
;;; guix/ui.scm:320:2: warning: non-literal format string
;;; guix/ui.scm:338:22: warning: non-literal format string
;;; guix/ui.scm:366:13: warning: non-literal format string
;;; guix/ui.scm:359:7[40/40] Compiling './guix/utils.scm'...
: warning: non-literal format string
;;; guix/ui.scm:354:11: warning: non-literal format string
;;; guix/ui.scm:390:7: warning: non-literal format string
;;; guix/ui.scm:487:2: warning: non-literal format string
;;; guix/ui.scm:489:2: warning: non-literal format string
;;; guix/ui.scm:600:22: warning: non-literal format string
;;; guix/ui.scm:603:22: warning: non-literal format string
;;; guix/ui.scm:713:13: warning: non-literal format string
;;; guix/ui.scm:899:14: warning: non-literal format string
;;; guix/ui.scm:924:14: warning: non-literal format string
;;; guix/ui.scm:1436:18: warning: non-literal format string
;;; guix/ui.scm:1451:10: warning: non-literal format string
;;; guix/ui.scm:1494:2: warning: non-literal format string
;;; guix/ui.scm:1510:2: warning: non-literal format string
;;; guix/ui.scm:1540:2: warning: non-literal format string
;;; guix/ui.scm:1569:2: warning: non-literal format string
;;; guix/ui.scm:1572:2: warning: non-literal format string
;;; guix/ui.scm:1591:8: warning: non-literal format string
;;; guix/ui.scm:1629:5: warning: non-literal format string
;;; guix/ui.scm:1621:5: warning: non-literal format string
...building /gnu/store/98aj7wckcsjcgkb3v0q6b7lvl8lch0ck-guix-core.drv...
loading... 86.8% of 38 files
Now it's going on, but if this has sense, I report.
[-- Attachment #2: Type: text/html, Size: 3161 bytes --]
next reply other threads:[~2018-11-30 11:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-30 11:48 znavko [this message]
2018-12-01 15:59 ` bug#33557: guix errors, if you want Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=LSZRh4N--3-1@tutanota.com \
--to=znavko@tutanota.com \
--cc=33557@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).