From: zimoun <zimon.toutoune@gmail.com>
To: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: How to install previous versions?
Date: Fri, 9 Oct 2020 18:37:44 +0200 [thread overview]
Message-ID: <CAJ3okZ0jMJUk_Xe-M6J6LtWudzca+zxGDTis=6QDZ-7aG+YUWQ@mail.gmail.com> (raw)
In-Reply-To: <74f9ab4c-346a-fa13-53ca-8d47dd50e683@posteo.de>
Hi,
On Fri, 9 Oct 2020 at 19:19, Zelphir Kaltstahl
<zelphirkaltstahl@posteo.de> wrote:
> http://data.guix.gnu.org/repository/1/branch/master/package/python-redis.
On this web page, you can click on the date: first commit and last
commit known to have this version. You can even see the status
(build, failed, pending, etc.) on this web page (appending
'output-history')
http://data.guix.gnu.org/repository/1/branch/master/package/python-redis/output-history
For example, clicking leads to:
http://data.guix.gnu.org/revision/f5111b4d2b982d58387188bc3018e4dd2e9a9d4f
And this gives you the commit with 'python-redis@3.8', using the command:
guix time-machine --commit=f5111b \
-- environment --ad-hoc python-redis python \
-- python
> So how would I need to write my manifest.scm or my one-liner to get back
> to that older version?
The best is to write a manifest file, say manifest.scm containing the
package you need:
--8<---------------cut here---------------start------------->8---
(specfications->manifest
(list
"python-redis"
"python"
"foo"
"bar"
"etc"))
--8<---------------cut here---------------end--------------->8---
The other no-so-said is to track "guix describe", you *should* _track_
the file channels.scm:
guix describe -f channels.scm
Then later or on another machine, you simply run the command:
guix time-machine -C path/to/channels.scm \
-- <subcommand> -m path/to/manifest.scm <options>
Hope that helps,
simon
next prev parent reply other threads:[~2020-10-09 17:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-09 17:00 How to install previous versions? Zelphir Kaltstahl
2020-10-09 16:37 ` zimoun [this message]
2020-10-10 15:14 ` Zelphir Kaltstahl
2020-10-10 16:44 ` zimoun
2020-10-12 13:58 ` Zelphir Kaltstahl
2020-10-12 14:29 ` zimoun
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='CAJ3okZ0jMJUk_Xe-M6J6LtWudzca+zxGDTis=6QDZ-7aG+YUWQ@mail.gmail.com' \
--to=zimon.toutoune@gmail.com \
--cc=help-guix@gnu.org \
--cc=zelphirkaltstahl@posteo.de \
/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.
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).