From: swedebugia <swedebugia@riseup.net>
To: guix-devel@gnu.org, ng0@n0.is
Subject: Re: upgrading on GuixSD before 0.16 to 0.16 fails
Date: Thu, 21 Feb 2019 19:41:22 +0100 [thread overview]
Message-ID: <00569D3A-76A4-4025-8F78-B02636CE0E69@riseup.net> (raw)
In-Reply-To: <20190221170944.hdlvxe5fblniecpq@uptimegirl.lan>
[-- Attachment #1: Type: text/plain, Size: 2347 bytes --]
ng0@n0.is skrev: (21 februari 2019 18:09:53 CET)
>Hi,
>
>I'm currently trying to upgrade out (gnunet) server to a new
>version of GuixSD. Upgrading it was put off for a while due to research
>reasons.
>
>This installation is from November '18, and I'm getting stuck on a
>backtrace when I'm trying to pull from the commit 0.16 tags or
>anything after it.
>
>Here's the backtrace. If it helps I can attach the config.
>
>root@firefly ~/gnunet-maintenance/gnunet# guix system build config.scm
>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.
>
>
>Backtrace:
> 14 (primitive-load "/root/.config/guix/current/bin/guix")
>In guix/ui.scm:
> 1603:12 13 (run-guix-command _ . _)
>In ice-9/boot-9.scm:
> 829:9 12 (catch _ _ #<procedure 7f01456e5498 at guix/ui.scm:615?> ?)
> 829:9 11 (catch _ _ #<procedure 7f01456e54b0 at guix/ui.scm:733?> ?)
>In guix/scripts/system.scm:
> 1268:8 10 (_)
>In guix/status.scm:
> 615:4 9 (call-with-status-report _ _)
>In guix/scripts/system.scm:
> 1138:6 8 (process-action _ _ _)
>In guix/store.scm:
> 1659:24 7 (run-with-store _ _ #:guile-for-build _ #:system _ # _)
>In guix/scripts/system.scm:
> 1151:13 6 (_ _)
> 869:18 5 (perform-action build #<<operating-system> kernel: #<p?> ?)
>In gnu/system.scm:
> 840:19 4 (operating-system-derivation _ #:container? _)
>In gnu/services.scm:
> 743:6 3 (instantiate-missing-services _)
>In guix/combinators.scm:
> 45:26 2 (fold2 #<procedure adjust-service-list (svc result ins?> ?)
> 45:26 1 (fold2 #<procedure 458edc0 at gnu/services.scm:717:11 ?> ?)
>In gnu/services.scm:
> 723:31 0 (_ _ (#<<service> type: #<service-type static-netwo?> ?) ?)
>
>gnu/services.scm:723:31: In procedure struct_vtable: Wrong type
>argument in position 1 (expecting struct): shepherd-root-service-type
We need your config to be certain but I am guessing you are bitten by the ABI changes: service->service-type.
Though this usually gives a more helpful error.
--
Sent from my k-9 mail for Android.
[-- Attachment #2: Type: text/html, Size: 2728 bytes --]
next prev parent reply other threads:[~2019-02-21 18:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-21 17:09 upgrading on GuixSD before 0.16 to 0.16 fails ng0
2019-02-21 18:41 ` swedebugia [this message]
2019-02-21 20:38 ` shpchp kernel module (Re: upgrading on GuixSD before 0.16 to 0.16 fails) ng0
2019-02-21 20:59 ` Ricardo Wurmus
2019-02-21 21:11 ` ng0
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=00569D3A-76A4-4025-8F78-B02636CE0E69@riseup.net \
--to=swedebugia@riseup.net \
--cc=guix-devel@gnu.org \
--cc=ng0@n0.is \
/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).