Il 30/01/2014 19:30, Adam Litke ha scritto:
> On 30/01/14 18:13 +, Dan Kenigsberg wrote:
>> On Thu, Jan 30, 2014 at 11:49:42AM -0500, Adam Litke wrote:
>>> Hi Sandro,
>>>
>>> After updating the MOM project's build system, I have used jenkins to
>>> produce a set of RPMs that I would like to tag
On 30/01/14 18:13 +, Dan Kenigsberg wrote:
On Thu, Jan 30, 2014 at 11:49:42AM -0500, Adam Litke wrote:
Hi Sandro,
After updating the MOM project's build system, I have used jenkins to
produce a set of RPMs that I would like to tag into the oVirt 3.4
release. Please see the jenkins job [1]
On Thu, Jan 30, 2014 at 11:49:42AM -0500, Adam Litke wrote:
> Hi Sandro,
>
> After updating the MOM project's build system, I have used jenkins to
> produce a set of RPMs that I would like to tag into the oVirt 3.4
> release. Please see the jenkins job [1] for the relevant artifacts
> for EL6[2],
Hi Sandro,
After updating the MOM project's build system, I have used jenkins to
produce a set of RPMs that I would like to tag into the oVirt 3.4
release. Please see the jenkins job [1] for the relevant artifacts
for EL6[2], F19[3], and F20[4].
Dan, should I submit a patch to vdsm to make it r
Il 30/01/2014 16:13, Yaniv Bronheim ha scritto:
> Hey,
>
> we found this yum bug and still struggling with more issuing according to the
> relation between those packages
>
> if we drop vdsm-python-cpopen the requirement in vdsm takes python-cpopen
> instead.
> in python-cpopen we have the sa
Hey,
we found this yum bug and still struggling with more issuing according to the
relation between those packages
if we drop vdsm-python-cpopen the requirement in vdsm takes python-cpopen
instead.
in python-cpopen we have the same code base and it provides all
vdsm-ptyhon-cpopen provides, s
On Thu, Jan 30, 2014 at 10:27:34AM +0100, Sandro Bonazzola wrote:
> Il 30/01/2014 10:20, Dan Kenigsberg ha scritto:
> > On Thu, Jan 30, 2014 at 08:52:36AM +, Sven Kieske wrote:
> >> Hi,
> >>
> >> any news regarding my questions?
> >>
> >> Am 29.01.2014 09:23, schrieb Sandro Bonazzola:
> >>> Il
Hi,
thanks for your reply.
So for a stable 3.3. deployment vdsm-python-cpopen would suffice
but when I want to upgrade to 3.4. I'll need python-cpopen anyway.
I guess you got some version/deprecation problems in rpm/yum to properly
replace vdsm-p-c with p-c.
To be a little bit more precise:
I
Il 30/01/2014 10:20, Dan Kenigsberg ha scritto:
> On Thu, Jan 30, 2014 at 08:52:36AM +, Sven Kieske wrote:
>> Hi,
>>
>> any news regarding my questions?
>>
>> Am 29.01.2014 09:23, schrieb Sandro Bonazzola:
>>> Il 29/01/2014 09:21, Sven Kieske ha scritto:
Hi,
I wanted to try it th
On Thu, Jan 30, 2014 at 08:52:36AM +, Sven Kieske wrote:
> Hi,
>
> any news regarding my questions?
>
> Am 29.01.2014 09:23, schrieb Sandro Bonazzola:
> > Il 29/01/2014 09:21, Sven Kieske ha scritto:
> >> Hi,
> >>
> >> I wanted to try it the other way around, installing vdsm-python-cpopen
> >
Hi,
any news regarding my questions?
Am 29.01.2014 09:23, schrieb Sandro Bonazzola:
> Il 29/01/2014 09:21, Sven Kieske ha scritto:
>> Hi,
>>
>> I wanted to try it the other way around, installing vdsm-python-cpopen
>> and check if it runs without python-cpopen .
>>
>> But that leads me to a quest
11 matches
Mail list logo
