From: Leo Famulari <leo@famulari.name>
To: swedebugia@riseup.net
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: The art of guessing a packaged downgrade version of a package
Date: Fri, 1 Jan 2016 16:09:59 -0500 [thread overview]
Message-ID: <20160101210959.GA11284@jasmine> (raw)
In-Reply-To: <22bcae0b31e189110555fdff8dfc948a@riseup.net>
On Fri, Jan 01, 2016 at 09:35:40PM +0100, swedebugia@riseup.net wrote:
> (trying to get gnupg to work knowing that ludo runs some 2.0 version)
> ~/src/guix$ guix package -i gnupg:2.0.0 -r gnupg
> guix package: error: package `gnupg-2.1.10' lacks output `2.0.0'
Did you try `guix package -i gnupg-2.0.29`? That should put the 2.0
series gnupg in your profile. You can even specify just 'gnupg-2.0' and
Guix will pick the lastest available gnupg in the '2.0' series.
>
> I would like to improve this command by making it either show me the valid
> outputs (and optionally choosing one of them to install) for this specific
> package OR hint me about running:
> guix package --show=gnupg
I see the value of hints, but never an interactive command as suggested
by a menu of valid outputs. Interactive commands break automation.
> ~$ guix package --show=gnupg
> name: gnupg
> version: 2.1.10
> outputs: out
> ...
>
> name: gnupg
> version: 2.0.29
> outputs: out
> ...
>
> name: gnupg
> version: 1.4.20
> outputs: out
>
> to get the information I need.
>
> I found the relevant code in:
> ../gnu/packages.scm:381: (leave (_ "package `~a' lacks output
> `~a'~%")
>
> To be able myself to improve this snippet I would have to learn a lot more
> Guile first. :p
>
> Anybody care to help?
>
> swedebugia
>
next prev parent reply other threads:[~2016-01-01 21:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-01 20:35 The art of guessing a packaged downgrade version of a package swedebugia
2016-01-01 21:09 ` Leo Famulari [this message]
2016-01-02 16:41 ` swedebugia
2016-01-02 20:51 ` 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=20160101210959.GA11284@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=swedebugia@riseup.net \
/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).