From: sirgazil <sirgazil@zoho.com>
To: Giovanni Biscuolo <g@xelera.eu>, help-guix@gnu.org
Subject: Re: I can't install guile-picture-language
Date: Fri, 15 Feb 2019 09:14:59 -0500 [thread overview]
Message-ID: <4cf2911b-2706-4c8f-3bb0-becd8e854896@zoho.com> (raw)
In-Reply-To: <87mumxb94z.fsf@roquette.mug.biscuolo.net>
Hi Giovanni,
El 15/02/19 a las 6:09 a. m., Giovanni Biscuolo escribió:
> Hi sirgazil,
>
> sirgazil <sirgazil@zoho.com> writes:
>
>> Hi,
>>
>> I'm getting this error:
>>
>> ········································
>> $ guix package -i guile-picture-language
>> guix package: error: guile-picture-language: unknown package
>> ········································
>>
>> As far as I can tell, my Guix version is up to date:
>>
>> ········································
>> $ guix --version
>> guix (GNU Guix) 0.16.0-9.4bddd12
>> Copyright (C) 2019 the Guix authors
>> License GPLv3+: GNU GPL version 3 or later
>> <http://gnu.org/licenses/gpl.html>
>> This is free software: you are free to change and redistribute it.
>> There is NO WARRANTY, to the extent permitted by law.
>> ········································
>
> update your guix version with "guix pull": it's not enough up to date
Actually, I did "guix pull" and "guix package -u" before trying to
install the package.
>> It happens only with this package. I can install other packages
>> normally.
>
> yes, that's because - looking at git logs - guile-picture-language was
> added with commit 6bb5f88e1 on Sun Feb 3 01:37:12 2019 +0100 while your
> guix commit (4bddd12) is dated Mon Jan 28 23:13:41 2019 +0100
>
> guix is moving fast :-)
The error makes sense, then :)
>> What could this be? Are you able to install guile-picture-language?
>
> yes, I was able to install precompiled from the default subsitutes
> servers
>
> this is my guix description:
>
> --8<---------------cut here---------------start------------->8---
> $ guix describe
> Generation 6 Feb 14 2019 17:28:18 (current)
> guix 03d3732
> repository URL: https://git.savannah.gnu.org/git/guix.git
> branch: master
> commit: 03d373202347617056ef103d356575d068123db8
> --8<---------------cut here---------------end--------------->8---
What doesn't make sense in my case is that I just ran "guix pull" and
"guix package -u" again (both as root and user), but when I run "guix
--version", I get the same version I posted yesterday:
········································
guix --version
guix (GNU Guix) 0.16.0-9.4bddd12
Copyright (C) 2019 the Guix authors
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
········································
Also, this is what "guix describe" tells me:
········································
$ guix describe
guix describe: error: failed to determine origin
········································
--
Luis Felipe López Acevedo
http://sirgazil.bitbucket.io/
next prev parent reply other threads:[~2019-02-15 14:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-15 1:29 I can't install guile-picture-language sirgazil
2019-02-15 11:09 ` Giovanni Biscuolo
2019-02-15 14:14 ` sirgazil [this message]
2019-02-15 14:23 ` Julien Lepiller
2019-02-15 16:57 ` sirgazil
2019-02-15 14:24 ` Ricardo Wurmus
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=4cf2911b-2706-4c8f-3bb0-becd8e854896@zoho.com \
--to=sirgazil@zoho.com \
--cc=g@xelera.eu \
--cc=help-guix@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.
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).