unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alexander Vorobiev <alexander.vorobiev@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Daemon update
Date: Fri, 29 May 2015 17:34:26 -0500	[thread overview]
Message-ID: <CAGOCFPX7vV4ztKYaw0iXDTGBSqNt0m0TN=G-eaLLmt0nKs0MqA@mail.gmail.com> (raw)
In-Reply-To: <87h9qvayp5.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1856 bytes --]

Pulled, restarted. The next stop is tcsh. The tarball at ftp.astron.com s
gone, replaced with more recent version...
One observation: apparently coreutils refuses to be built as root so I had
to create a build user/group to give to guix-daemon.

Thanks,
Alex

On Fri, May 29, 2015 at 3:57 PM, Ludovic Courtès <ludo@gnu.org> wrote:

> Alexander Vorobiev <alexander.vorobiev@gmail.com> skribis:
>
> > I have some good progress finally. I started from scratch and pulled the
> > latest from git. I am now running guix-daemon as root with only one
> option
> > --no-substitutes. The make guix-binary* ran for hours and built a lot of
> > stuff (bash, gcc, perl, etc) but stumbled upon openldap which doesn't
> seem
> > to be available at the url it wants to use:
>
> Indeed, I’ve updated the OpenLDAP URLs.
>
> > I tried modifying gnu/packages/openldap.scm to use correct url (
> > ftp://mirror.switch.ch/mirror/OpenLDAP/openldap-release/...) but that
> > didn't change anything since (I am guessing) the .drv files in store
> > weren't rebuilt and still point to the old url. How do I fix that without
> > rebuilding everything that it created so far?
>
> Changing the file does have an effect, but perhaps you modified the
> wrong file?  At any rate, if you git pull now and try again it should
> work (and it won’t rebuild everything.)
>
> > As a side note, would it be possible to modify the files you suggested
> (gnu
> > packages package-management and gnu system instal) for the custom local
> > state dir in such a way (through configure? scheme variable?) that it
> > wouldn't be hard-coded? I am guessing any update to guix would cause my
> > changes to be lost?
>
> Since you’re working from a git checkout (right?), you can always
> arrange to have your changes applied.
>
> Thanks,
> Ludo’.
>

[-- Attachment #2: Type: text/html, Size: 2547 bytes --]

  reply	other threads:[~2015-05-29 22:35 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-19 14:15 Daemon update Ludovic Courtès
2015-05-21  3:03 ` Alex Vorobiev
2015-05-21  7:24   ` Taylan Ulrich Bayırlı/Kammer
2015-05-21  8:24   ` Ludovic Courtès
2015-05-22  1:47     ` Alexander Vorobiev
2015-05-22  8:35       ` Taylan Ulrich Bayırlı/Kammer
2015-05-22 13:45       ` Ludovic Courtès
2015-05-27  3:27         ` Alexander Vorobiev
2015-05-27 15:18           ` Ludovic Courtès
2015-05-27 20:10             ` Alexander Vorobiev
2015-05-27 20:51               ` Ludovic Courtès
2015-05-28 17:56                 ` Alexander Vorobiev
2015-05-29 20:57                   ` Ludovic Courtès
2015-05-29 22:34                     ` Alexander Vorobiev [this message]
2015-05-31 19:14                       ` Ludovic Courtès
2015-06-01 16:50                         ` Alexander Vorobiev
2015-06-01 19:58                           ` Ludovic Courtès
2015-06-01 20:23                             ` Alexander Vorobiev
2015-06-02  5:26                               ` Alexander Vorobiev
2015-06-03  8:24                                 ` Ludovic Courtès
2015-06-03 16:04                                   ` Alexander Vorobiev
  -- strict thread matches above, loose matches on Subject: below --
2015-05-12  7:58 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='CAGOCFPX7vV4ztKYaw0iXDTGBSqNt0m0TN=G-eaLLmt0nKs0MqA@mail.gmail.com' \
    --to=alexander.vorobiev@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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.
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).