From: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
To: brettg@posteo.net
Cc: guix-devel@gnu.org
Subject: Re: Reinstallation issue
Date: Thu, 1 Nov 2018 10:29:10 +0100 [thread overview]
Message-ID: <20181101102910.69acaba5@alma-ubu> (raw)
In-Reply-To: <f3f2e545a52926a2711fa707d4377b50@posteo.net>
[-- Attachment #1: Type: text/plain, Size: 2425 bytes --]
Hi,
On Thu, 01 Nov 2018 05:02:24 +0100
brettg@posteo.net wrote:
> Hi all, I am trying to duplicate my environment on another machine of
> mine using my plain desktop comfiguration.
>
> There seems to be a bad URL request with telepathy
> On the gnome desktop service which is preventing the
> guix init system from grafting all of the packages.
>
> It’s telepathy-glib-duplicates-tests 504ing on the hydra morror
> Even though I am substituting berlin.
>
> And the relevant nixos tarball is 404ing.
Sorry, it seams there are still problems with the substitute servers.
You could try to just use berlin, like in:
guix system init --substitute-urls="https://berlin.guixsd.org"
But it might be the case that Berlin doesn't have the substitutes (yet)?
You get the 404 on nix tarballs because guix is falling back to
building from source. And then the original source package is no longer
existing on the project's side (i.e. they delete the old version,
changed the URL, etc). So guix is searching by hashsum on substitute
servers and Nix servers, but fails in your case also.
If you like, you can check which specific package it is and send a bug
or even patch for updating it in Guix. But that is more for the longer
run.
Are your computers on the same network? One solution for you could be to
use your old computer as substitute server, through guix publish:
https://www.gnu.org/software/guix/manual/en/guix.html#Invoking-guix-publish
Basically, you say on your old coputer `guix publish` and that will
serve substitutes on port 8080 (see manual to change port).
Then on your new one you can say
guix system init --substitute-urls="http://old-computers-ip:8080/"
(Maybe add berlin also, space-separated)
There are two things to look out for:
1) You need to register the key of your serving old computer into the
new computer, see docs in guix archive:
https://www.gnu.org/software/guix/manual/en/guix.html#Invoking-guix-archive
2) Your new computer should be on the same guix commit as on the old
one, at the time when you lastly did a `guix init reconfigure`,
such that it really fetches the same packages.
If you haven't done a guix pull on the old one, just run a
old$ guix --version
and save the commit.
Then do a
new$ guix pull --commit=<commit-id>
on the new one to bring them in sync.
Hope this helps,
Björn
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
prev parent reply other threads:[~2018-11-01 9:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-01 4:02 Reinstallation issue brettg
2018-11-01 9:29 ` Björn Höfling [this message]
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=20181101102910.69acaba5@alma-ubu \
--to=bjoern.hoefling@bjoernhoefling.de \
--cc=brettg@posteo.net \
--cc=guix-devel@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).