On 19.08.2018 23:31, Maxim Cournoyer wrote:
Based on the above discussion, it seems this shouldn't be required if
you are using a very recent Guix, but I too struggled on this error at
some point and the (not-so-pretty) workaround was to issue a 'guix
package -i guile-sqlite3'.
I mean to
Hi,
Thorsten Wilms writes:
> On 02.08.2018 14:18, Ricardo Wurmus wrote:
>> Which “guix” are you using? “guix pull” installs “guix” in
>> ~/.config/guix/current/bin. Make sure that the “guix” in “guix
>> environment guix” is taken from there.
Based on the above discussion, it seems this
On 02.08.2018 14:18, Ricardo Wurmus wrote:
Which “guix” are you using? “guix pull” installs “guix” in
~/.config/guix/current/bin. Make sure that the “guix” in “guix
environment guix” is taken from there.
Tripple checked. I'm fully expecting some silly mistake, but well, I
can't find it.
Thorsten Wilms writes:
>> * Run "guix pull" at least twice - without using ./pre-inst-env.
>
> Done.
[…]
> With `guix environment guix` it's again:
> ---
> checking for sqlite3 >= 3.6.19... no
> configure: error: Package requirements (sqlite3 >= 3.6.19) were not met:
>
> No package 'sqlite3'
On 02.08.2018 09:12, Chris Marusich wrote:
configure: error: Package requirements (sqlite3 >= 3.6.19) were not met:
No package 'sqlite3' found
---
It sounds like you're saying this error occurs when you've run "guix
environment guix", and then you run "./configure --localstatedir=/var".
Is
On 17.06.2018 22:24, Thorsten Wilms wrote:
git clone https://git.savannah.gnu.org/git/guix.git
cd guix
*add package definition, commit right here, or maybe later*
guix environment guix
./bootstrap
./configure --localstatedir=/var
./pre-inst-env guix package -i *new-package*
configure fails
OK, I get it now. I had missed that message about the PATH.
I think those kinds of breakage would deserve some proper annoucements,
either on the mailing list or on the website.
What do you people think?
--
Pierre Neidhardt
Nothing is easier than to denounce the evildoer; nothing is more
Hi
On June 19, 2018 12:32:43 PM GMT+02:00, Pierre Neidhardt
wrote:
>
>> What is your path?
>/home/ambrevar/.guix-profile/bin
>/home/ambrevar/.guix-profile/sbin
>/run/setuid-programs
>/run/current-system/profile/bin
>/run/current-system/profile/sbin
This lacks the path to the guix pulled with
On 18.06.2018 21:58, Ludovic Courtès wrote:
Add this commit, the ‘guix’ package definitely has ‘guile-sqlite3’ as an
input. Could you run ‘guix edit guix’ to double-check?
"guile-sqlite3" appears twice within (define-public guix), inside
(add-after 'install 'wrap-program ...)
and also
> What is your path?
/home/ambrevar/.guix-profile/bin
/home/ambrevar/.guix-profile/sbin
/run/setuid-programs
/run/current-system/profile/bin
/run/current-system/profile/sbin
> I pulled the same commit as Thorsten and had to upgrate my path manually to
> be able to use the guix that was pulled.
Hi
On June 18, 2018 10:12:03 PM GMT+02:00, Pierre Neidhardt
wrote:
>
>I have a similar issue.
>
>> which guix
>/run/current-system/profile/bin/guix
What is your path?
I pulled the same commit as Thorsten and had to upgrate my path manually to be
able to use the guix that was pulled.
Please
I have a similar issue.
> which guix
/run/current-system/profile/bin/guix
> guix edit guix
# The package definition is in
# /home/ambrevar/.config/guix/latest/gnu/packages/package-management.scm
So guix is using "latest" instead of "current".
I suppose that if `guix' is not in my user
Hi Thorsten,
Thorsten Wilms skribis:
> configure fails with:
> checking whether Guile-Sqlite3 is available and recent enough... no
[...]
> $: which guix => /home/thorwil/.config/guix/current/bin/guix
>
> $: guix pull -l
> ...
> Generation 8Jun 17 2018 20:01:23(current)
>
Hi!
I wanted to add a package, test it and send in a patch. The docs are not
quite as clear as they should be on the right steps to take, but since
helpful and knowledgable people are never far on #guix, it became clear
that it should be (I hope):
git clone
14 matches
Mail list logo
