From: ludo@gnu.org (Ludovic Courtès)
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Having a Guix archive on the download page?
Date: Thu, 19 Jul 2018 16:50:51 +0200 [thread overview]
Message-ID: <87va9bqnxw.fsf@gnu.org> (raw)
In-Reply-To: <20180711161351.zyers5wm373vlcpm@thebird.nl> (Pjotr Prins's message of "Wed, 11 Jul 2018 18:13:51 +0200")
Hello,
And sorry for the delay.
Pjotr Prins <pjotr.public12@thebird.nl> skribis:
> On Wed, Jul 11, 2018 at 02:55:45PM +0200, Ludovic Courtès wrote:
>> Now the question is, will it always be possible to run ‘guix pull’ from
>> an arbitrary-old Guix? Maybe it will still be impossible sometimes if
>> the old Guix is really too old. However, I suspect such issues will be
>> much more rare. There’s essentially a single file that needs to be put
>> under scrutiny to avoid such issues: build-aux/build-self.scm.
[...]
> The change to guile2 was such a break, guile-json/tls another
Like I wrote, this specific class of problem disappears with the new
‘guix pull’.
> That was dependencies only. We know we are going to change the
> database in the future...
FWIW the database format for /var/guix/db/db.sqlite has always been the
same in Guix.
Ludo’.
next prev parent reply other threads:[~2018-07-19 14:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-07 12:17 Having a Guix archive on the download page? Pjotr Prins
2018-07-08 12:28 ` guix pull le-certs problem - formerly: Having a Guix archive Pjotr Prins
2018-07-08 12:34 ` Pjotr Prins
2018-07-08 16:31 ` Pjotr Prins
2018-07-08 19:47 ` Ricardo Wurmus
2018-07-11 12:55 ` Having a Guix archive on the download page? Ludovic Courtès
2018-07-11 16:13 ` Pjotr Prins
2018-07-19 14:50 ` Ludovic Courtès [this message]
2018-07-20 20:21 ` EuAndreh
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=87va9bqnxw.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=pjotr.public12@thebird.nl \
/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).