Il 19/01/2015 18:19, Edward L Heron ha scritto:
> On Mon, 2015-01-19 at 12:08 +, George Dunlap wrote:
>> ...
>>
>> The current setup is that every sig has exactly one production repo
>> per CentOS version.
>>
>> ...
>>
>> So it seems we have a couple of ways to approach it.
>>
>> 1. Keep it one
On Mon, 2015-01-19 at 12:08 +, George Dunlap wrote:
> ...
>
> The current setup is that every sig has exactly one production repo
> per CentOS version.
>
> ...
>
> So it seems we have a couple of ways to approach it.
>
> 1. Keep it one repo per SIG, and make all projects in a SIG sort out
>
On 01/17/2015 08:46 AM, Pasi Kärkkäinen wrote:
> On Fri, Jan 16, 2015 at 09:16:05PM +0200, Pasi Kärkkäinen wrote:
>> Hello,
>>
>> As discussed on the last Virt SIG meeting I promised to do some libvirt +
>> libxl testing using the latest Xen 4.4 rpms.
>>
>> Versions used:
>>
>> xen-libs-4.4.1-5.el
On Fri, Jan 16, 2015 at 12:47 AM, aurfalien wrote:
> Hi all,
>
> I thought I’d post this in case any one has issues similar to mine.
>
> First, my initial email to the list which I didn’t send;
>
> I’m trying to run a KVM based guest OS off of a mirrored ZFS dataset.
>
> It won’t run with errors "
At the moment, we're essentially using yum repos as the "patch"
mechanism to CentOS Base: SIGs populate a repo with packages they want
to add / override, and all other packages default to Base.
The current setup is that every sig has exactly one production repo
per CentOS version.
Also, we seem t
