On Thu, Mar 20, 2014 at 11:07:34PM +0100, Ludovic Courtès wrote:
> OK, I believe this is fixed with 89faa5c.
Indeed, it is working now. Thanks!
Andreas
Andreas Enge skribis:
> I get:
> starting substituter program
> `/usr/local/guix-git/libexec/nix/substituters/download-using-manifests.pl'
> download-using-manifests.pl: error: executing
> `/usr/local/guix-git/libexec/nix/substituters/download-using-manifests.pl':
> No such file or directory
On Thu, Mar 20, 2014 at 07:05:35PM +0100, Ludovic Courtès wrote:
> download-using-manifests.pl is a Nix thing; the equivalent in Guix in
> ‘guix substitute-binary’ (no .pl here ;-)).
>
> Normally guix-daemon.cc sets the NIX_SUBSTITUTERS environment variable
> so that the daemon’s code uses our sub
Andreas Enge skribis:
> Currently, the substituter fails for me. For instance,
>guix build pari-gp -n
> yields the following message:
> download-using-manifests.pl: error: executing
> `/usr/local/guix-git/libexec/nix/substituters/download-using-manifests.pl':
> No such file or directory
> g
Currently, the substituter fails for me. For instance,
guix build pari-gp -n
yields the following message:
download-using-manifests.pl: error: executing
`/usr/local/guix-git/libexec/nix/substituters/download-using-manifests.pl': No
such file or directory
guix build: error: build failed: substi
FWIW I’ve migrated my laptop to /gnu/store, and also switched to a
different $localstatedir (meaning that the store’s DB, build log
directory, profiles, etc. are stored in a different place.)
After that, I ended up starting from an empty profile (because the old
one was elsewhere.) So I recreated
Andreas Enge skribis:
> On Wed, Mar 12, 2014 at 12:06:10PM +0100, Ludovic Courtès wrote:
>> Right, but in master we don’t change “core” stuff like build/utils.scm,
>> glibc, etc. Sometimes there are changes that trigger a lot of rebuild,
>> but never as much as what we do in core-updates.
>
> So
On Wed, Mar 12, 2014 at 12:06:10PM +0100, Ludovic Courtès wrote:
> Right, but in master we don’t change “core” stuff like build/utils.scm,
> glibc, etc. Sometimes there are changes that trigger a lot of rebuild,
> but never as much as what we do in core-updates.
Sorry, but I am still lost; we jus
Andreas Enge skribis:
> Nothing prevents us from merging core-updates several times before a release.
> As I see it, core-updates is there so that people tracking git master are not
> forced to recompile too often.
Too often and too much. Also, changes in core-updates can potentially
break more
Nothing prevents us from merging core-updates several times before a release.
As I see it, core-updates is there so that people tracking git master are not
forced to recompile too often. But a change to master that forces recompilat-
ion should be linked with a merge of core-updates into master, wh
Cyril Roelandt skribis:
> On 03/10/2014 09:14 PM, Ludovic Courtès wrote:
>> Andreas Enge skribis:
>>
>>> Would it not be the time now to merge core-updates back into master, as
>>> anyway everything will be rebuilt?
>>
>> We need to discuss with Mark whether to release Guile 2.0.10, or just
>> p
On 03/10/2014 09:14 PM, Ludovic Courtès wrote:
Andreas Enge skribis:
Would it not be the time now to merge core-updates back into master, as
anyway everything will be rebuilt?
We need to discuss with Mark whether to release Guile 2.0.10, or just
patch it the way Cyril proposed a while back.
Andreas Enge skribis:
> Would it not be the time now to merge core-updates back into master, as
> anyway everything will be rebuilt?
We need to discuss with Mark whether to release Guile 2.0.10, or just
patch it the way Cyril proposed a while back. But that’s basically the
only thing left to fi
On Mon, Mar 10, 2014 at 10:18 AM, Andreas Enge wrote:
> Would it not be the time now to merge core-updates back into master, as
> anyway everything will be rebuilt?
>
> Andreas
>
I think that we want to wait to merge core-updates until Guile 2.0.10
is released.
- Dave
On 03/10/2014 03:18 PM, Andreas Enge wrote:
Would it not be the time now to merge core-updates back into master, as
anyway everything will be rebuilt?
It would be nice to know that a bit in advance, so we have time to push
pending patches to core-updates before it's merged into master :)
Cy
Would it not be the time now to merge core-updates back into master, as
anyway everything will be rebuilt?
Andreas
On Mon, Mar 10, 2014 at 12:09:25AM +0100, Ludovic Courtès wrote:
> If you do plan to switch to /gnu/store now, then just run ./configure
> and forget about the rest.
Just a quick comment, you will also have to restart the guix daemon.
For instance, if you installed Sree's init script:
/etc/init
So! Commit 834129e changes the default store directory to /gnu/store.
Again, if you don’t plan to change right now, make sure to configure
with --with-store-dir=/nix/store next time!
The other change is commit f5768af, which changes the place where the
store’s database and build logs are stored.
Mark H Weaver skribis:
> Can you give some advice on how best to transition from /nix/store to
> /gnu/store on an existing Guix system? Can $PREFIX/var/nix and the
> sqlite database be shared, or do I have to start with a clean slate?
> Any other suggestions?
Sorry, I was planning to mention th
19 matches
Mail list logo
