All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guillaume Rousse <Guillaume.Rousse@inria.fr>
To: xen-devel@lists.xensource.com
Subject: building xen without mercury repository access
Date: Tue, 05 Feb 2008 18:54:53 +0100	[thread overview]
Message-ID: <47A8A2ED.5000708@inria.fr> (raw)

Hello, I'm mandriva package maintainer.

I just tried to update mandriva xen package. I noticed the build
procedure changed since 3.1.0: instead of downloading pristine kernel
sources, and patching them locally, the makefile now directly fetches
modified kernel from xen mercury repository. And even if a working
directory exists, it apparently still attempts to sync it before
building... Which is quite curious for a tagged release (but I may have
misunderstood the process).

As our packages are supposed to be self-contained, I need to download
once for all the xenified kernel sources. What command should I run ?
Running "sh buildconfigs/select-repository linux-2.6.18-xen.hg .:.." in
the top-level directory, as suggested by makefile, fails miserabily:
select-repository: Searching `.:..' for linux-2.6.18-xen.hg
select-repository: Ignoring `.'
not found!
select-repository: Unable to determine Xen repository parent.
-- 
Guillaume Rousse
Moyens Informatiques - INRIA Futurs
Tel: 01 69 35 69 62

             reply	other threads:[~2008-02-05 17:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-05 17:54 Guillaume Rousse [this message]
2008-02-05 19:08 ` building xen without mercury repository access Keir Fraser
2008-02-06 22:10   ` Guillaume Rousse
2008-02-07  8:18     ` Keir Fraser
2008-02-07  9:17       ` Guillaume Rousse
2008-02-07 10:33         ` Yves-Gaël Chény
2008-02-11 22:32       ` Guillaume Rousse
2008-02-11 22:40         ` Valter Douglas Lisbôa Jr.
2008-02-11 23:10         ` Keir Fraser
2008-02-12 10:27           ` Ian Jackson
2008-02-12 10:43             ` Guillaume Rousse
2008-02-12 10:46               ` Keir Fraser
2008-02-12 11:02                 ` Ian Jackson
2008-02-12 11:25                   ` Maximilian Wilhelm
2008-02-12 11:34                     ` Keir Fraser
2008-02-13  9:30                   ` Guillaume Rousse

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47A8A2ED.5000708@inria.fr \
    --to=guillaume.rousse@inria.fr \
    --cc=xen-devel@lists.xensource.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.