Hi! There were some discussions in private, so I think it's best to bring this up on the list. I'd like to ask all Livna maintainers to please continue with proper package maintaining in Livna for now until we start to carry users over from Livna to RPM Fusion. That should hopefully happen soon -- two weeks maybe if everything works out well (proper DNS, better filled repos, more space for the mastr-repo on the buildsys and proper release RPMs are the main things that are needed before we start with that). IOW: if you import - a new version of an existing package - a new package which obsoletes other Livna packages to RPM Fusion *please* import and build it for Livna as well for now. Yes, that is a bit of extra work, but that way the RPM Fusion (which has no users yet) packages get indirectly tested in Livna (which has a lot of users and testers); that is IMHO very important and will lead to better packages in RPM Fusion!

CU knurd

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 for re-creating the mpeg2dec package under a different name was suboptimal... Nicolas, how about you back out your libmpeg2 package from rpmfusion and 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... /David

2008/7/24 David Juran <david(a)juran.se&gt;: > 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 for > re-creating the mpeg2dec package under a different name was > suboptimal... > Nicolas, how about you back out your libmpeg2 package from rpmfusion and > 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... No, completely unacceptable. Please note what i've answeared on the list for all You cannot have a package NEVR in F-8 to be higher than F-9. If you don't understand that, I cannot explain that to you more.

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 for > re-creating the mpeg2dec package under a different name was > suboptimal... Nicolas, how about you back out your libmpeg2 package from > rpmfusion and > 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 way around and import the RPM Fusion libmpeg2 to livna devel now?

CU knurd

2008/7/24 David Juran <david(a)juran.se&gt;: > 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 for >>> re-creating the mpeg2dec package under a different name was >>> suboptimal... >>> Nicolas, how about you back out your libmpeg2 package from rpmfusion and >>> 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 way >> 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 ?

This problem is really an easy level one.

2008/7/24 Thorsten Leemhuis <fedora(a)leemhuis.info&gt;: > On 24.07.2008 11:18, KH KH wrote: >> 2008/7/24 David Juran <david(a)juran.se&gt;: >>> 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 for >>>>> re-creating the mpeg2dec package under a different name was >>>>> suboptimal... >>>>> Nicolas, how about you back out your libmpeg2 package from rpmfusion >>>>> and >>>>> 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 way >>>> 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! REMOVE this package now. How it is possible that you don't understand this is not the right way.