On 24.07.2008 13:53, KH KH wrote:
2008/7/24 Thorsten Leemhuis <fedora(a)leemhuis.info>:
> On 24.07.2008 11:18, KH KH wrote:
>> 2008/7/24 David Juran <david(a)juran.se>:
>>> On Thu, 2008-07-24 at 10:52 +0200, Thorsten Leemhuis wrote:
>>>> On 24.07.2008 10:31, David Juran wrote:
>>>>> On Thu, 2008-07-24 at 10:13 +0200, KH KH wrote:
>>>>>> - Update package
>>>>>> - import new package wich obsoletes Upgrade/Path
>>>>> OK, let's get back to the root of this problem. Maybe the timing
>>>>> re-creating the mpeg2dec package under a different name was
>>>>> Nicolas, how about you back out your libmpeg2 package from rpmfusion
>>>>> then we just import the livna package there. Then when things settle
>>>>> down and rpmfusion is firmly in place I can cede ownership of the
>>>>> package to you to do whatever you like with it...
>>>> Could work. But is there a reasons why we can't simply go the other
>>>> around and import the RPM Fusion libmpeg2 to livna devel now?
>>> I'm fine with that (-:
>>> Nicolas, do you agree it's a good idea/could you do this?
>> How this will make things different than just picking it from rpmfusion ?
> For the user there is no RPM Fusion yet.
>> This problem is really an easy level one.
> Yes -- just ship the same package (the one you imported to RPM Fusion= in
> RPM Fusion and Livna. The EVR for the package in RPM Fusions of course must
> he higher then the one in Livna and Freshrpms. Problem solved, user can test
> and report problems now; if they find some we can fix them before RPM Fusion
> gets live.
Please!!! Enought talking!
I still don't understand that. So here is the question I'd like to see
Why can't libmpeg2 from RPM Fusion be imported to Livna devel with a EVR
that is lower then the one of the package that was build for RPM Fusion?
Because that's what I'd like to do, to let the Livna devel users test
the package now, as that will be a benefit for the RPM Fusion package
later, as potential bugs will get found earlier if users get the
REMOVE this package now.
Don't yell if there is nothing to remove in Livna ;-) -- the updated
mpeg2dec from your Co-Maintainer David never made it to the repo; it was
just accidentally mentioned in the build report.
How it is possible that you don't understand this is not the
I suppose that's mostly my fault, but I often have a really hard time
following your mails. Take the "REMOVE this package now." from above.
What is this here libmpeg2 from RPM Fusion? The older mpeg2dec in livna?
The new one that the libmpeg2 Co-Maintainer commited to Livna? I knew
which one you meant -- but a bit more "--verbose" would be helpful to
understand your mails.