From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Ian Campbell <ian.campbell@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: wei.liu2@citrix.com, ian.jackson@eu.citrix.com, xen-devel@lists.xen.org
Subject: Re: [PATCH v8 1/2] OSSTEST: introduce a raisin build test
Date: Tue, 4 Aug 2015 15:47:09 +0200 [thread overview]
Message-ID: <55C0C25D.1070709@citrix.com> (raw)
In-Reply-To: <1438695690.31129.114.camel@citrix.com>
El 04/08/15 a les 15.41, Ian Campbell ha escrit:
> On Tue, 2015-08-04 at 14:18 +0100, Stefano Stabellini wrote:
>> On Tue, 4 Aug 2015, Ian Campbell wrote:
>>> On Tue, 2015-08-04 at 12:18 +0100, Stefano Stabellini wrote:
>>>>> It hasn't actually failed though, is that normal?
>>>>
>>>> It is an "optional" dependency, without it passthrough is disabled in
>>>> qemu-traditional. Passing -n tell raisin to "shut up, do nothing and
>>>> continue", so at the end the build still succeed.
>>>
>>> What other sorts of things are optional?
>>
>> There isn't really a distinction between mandatory dependencies and
>> optional dependencies in raisin. This is what raisin is currently
>> complaining about:
>>
>> bridge-utils pciutils-dev libnl-3-dev libnl-route-3-dev
>>
>> bridge-utils is actually a run time dependency for Xen, while
>> libnl-3-dev and libnl-route-3-dev are build time dependencies for
>> libvirt. I think they are needed for vlan support. Should I add them
>> too?
>
> I think so, I have a feeling Remus might use them too? cf "[PATCH] osstest:
> install libnl3 packages" from Roger.
Yes, Remus needs libnl-3-dev and libnl-route-3-dev. They are available
since Wheezy, but only the ones on Squeeze are new enough for the Remus
code. Feel free to pick that patch, it only needs a comment in the
description to mention that support for anything older than Wheezy is
dropped.
Roger.
next prev parent reply other threads:[~2015-08-04 13:47 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-23 16:51 [PATCH v8 0/2] OSSTEST: introduce a raisin build test Stefano Stabellini
2015-07-23 16:52 ` [PATCH v8 1/2] " Stefano Stabellini
2015-07-31 15:53 ` Ian Jackson
2015-07-31 15:54 ` Ian Jackson
2015-07-31 16:01 ` Ian Jackson
2015-08-03 16:59 ` Stefano Stabellini
2015-08-04 10:55 ` Ian Campbell
2015-08-04 13:02 ` [PATCH 1/2] ts-raisin-build: consolidate open coded iterations over enabled components Ian Campbell
2015-08-05 7:50 ` Ian Campbell
2015-08-04 13:02 ` [PATCH 2/2] ts-raisin-build: Use git_massage_url Ian Campbell
2015-08-04 8:35 ` [PATCH v8 1/2] OSSTEST: introduce a raisin build test Ian Campbell
2015-08-04 8:39 ` Ian Campbell
2015-08-04 9:37 ` Ian Campbell
2015-08-04 13:26 ` Stefano Stabellini
2015-08-04 11:04 ` Ian Campbell
2015-08-04 11:18 ` Stefano Stabellini
2015-08-04 11:37 ` Ian Campbell
2015-08-04 13:18 ` Stefano Stabellini
2015-08-04 13:41 ` Ian Campbell
2015-08-04 13:47 ` Stefano Stabellini
2015-08-04 14:01 ` Ian Campbell
2015-08-04 13:47 ` Roger Pau Monné [this message]
2015-08-04 13:51 ` Ian Campbell
2015-07-23 16:52 ` [PATCH v8 2/2] OSSTest: push successful raisin builds Stefano Stabellini
2015-07-31 16:03 ` Ian Jackson
2015-08-03 17:09 ` Stefano Stabellini
2015-08-04 8:23 ` Ian Campbell
2015-08-04 10:50 ` Ian Campbell
2015-08-04 12:56 ` Ian Campbell
2015-08-04 13:11 ` Ian Campbell
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=55C0C25D.1070709@citrix.com \
--to=roger.pau@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.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 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.