Next steps to get RPM Fusion running (V2)

Thorsten Leemhuis fedora at
Wed Oct 15 19:30:22 CEST 2008

On 15.10.2008 11:42, Hans de Goede wrote:
> Thorsten Leemhuis wrote:
>>> just thought I write down a rough list of things that I plan to do for 
>>> RPM Fusion over the next couple of weeks. I'm sending it here in the 
>>> hope that some people help me with some of those task; then we 
>>> hopefully get RPM Fusion running quite soon.
>> Here is a updated version; most important things at the top of the list; 
>> not all of the points necessarily have to be done, but ideally they all 
>> get done; if I missed anything just tell me ;-)
> As Fedora 10 is creeping closer and closer I would really like to see us go 
> live sooner rather then later, so I would like to suggest to sort this list in 
> SHOULD and MUST fix before going live items


>> - get the mirror manager that adrianr put in place (see
>> listed as in DNS;
>> Needs
>>  * adrianr:     IP address
>>  * thias:     DNS update
>> Afterwards update rpmfusion-release packages accordingly.
> As we have old style mirrorlists in place on right now, 
> and as this needs Thias, who seems to have dropped of the radar, I think this 
> is a SHOULD

A strong "SHOULD" IMHO. Would be really nice to get this in place. And 
it would be really good to have at least two different people that are 
able to update the DNS. But I suppose that's not that easy to realize?

 > [...]
>> - start importing and building the packages from freshrpms; I can do 
>> that, but I want to get the ACK from thias first; especially as
>> likely is not fully up to date 
>> Having a list of packages that are ready for importing would help things 
>> a lot
> First of all for moving livna (and dribble) user over, which is our first big 
> step I think, this is a SHOULD FIX.
> I think it would be good to have freshrpms packages not in livna/dribble in 
> rpmfusion no matter what, so I think it would be good to start working on this 
> as time permits without waiting for input from Thias. If you encounter any non 
> trivial buildfailures let me know and I'll gladly help.

I'll try to take a closer look; but I feel not that well with this plan 
-- even during imports from livna there were a few odd things. Most of 
them I could deal with on my own because I knew livna quite well, which 
is not the case for freshrpms...

>> - someone should run dep checks (e.g. for F8, F9 rawhide; once with only 
>> free and once with both free and nonfree enabled); I suspect that some 
>> problems will be found that way
> This has just been done I believe,

Yeah, thx again for your help Michael!


Most of them are not that important or rare corner-cases; I think I 
commented on all the relevant ones and CCed the maintainers in those mails.

>> - check that the upgrade path from Livna -> RPM Fusion is sane for each
>> package in each of the supported Fedora releases (I did a rough check on 
>> F9; looks good, but there are some packages still missing; maybe we can 
>> ignore those for now, as some of them are broken in livna, so it's not 
>> much of a difference)
> AFAIK we have (used to have?) some automated scripts for this in Fedora, maybe 
> we can use those ?

Setting those up just for the dribble/freshrpms/livna transition to RPM 
Fusion is afaics not worth the trouble

 > [...]
>> - move packages from testing -> stable for F-8 and F-9; build new 
>> rpmfusion-release packages that have the testing repo disabled!

But for now I think it's best to leave everything in testing to make it 
obvious that we are still in the testing phase.

 > [...]


More information about the rpmfusion-developers mailing list