Next steps to get RPM Fusion running

[Hans de Goede]

Thorsten Leemhuis wrote:
> Hi!
> 
> 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.
> 
> = most important things =
> 
> - get the mini-mirrormanager from 
> https://bugzilla.rpmfusion.org/show_bug.cgi?id=40#c9
> installed and running somewhere. Xavier afaik is ready with that for a 
> few days now; but he needs thias to get the machine in DNS, as only he 
> has control over DNS and thus is the only one that can add 
> mirror.rpmfusion.org; once that is done get the rpmfusion-release 
> package into the repos
> 

If we cannot get a hold of Matthias, we could just start with a mirrorlist like 
livna is using right?

> - we need a decision for kernel-module packaging. Decision here mainly 
> means: Get a statement (preferred a ACK) from thias regarding kmods 
> (which includes akmods), which afaics most of the other crucial 
> packagers accepted (Hans, Dominik and a few others)
> 

Same here if we cannot get hold of Matthias we should just move forward with kmods

> - once those two things are finished and the release-package is known to 
> be working I'll add rpmfusion-{non,}free-release to the livna *devel* 
> repos; then I'll build a new livna-release package that has a hard dep 
> on those two.
> 

+1

>   Livna-devel users thus will get rpmfusion enabled *automatically*. 
> Some people will not like it, but it's a reasonable things to do IMHO. 
> Especially as I plan to stop updating the livna devel repo from that 
> point (one things less to take care of for me and the package maintainers).
> 

I actually moved from livna to rpmfusion today to be able to test some things 
and to make sure local testbuilds I was doing were done against rpmfusion 
packages, and this works quite wel, for more info see below.

>  If that works out fine I plan to do the same for Fedora {8,9}-testing a 
> few days later.
> 

+1

> = other important things =
> 
> - get the remaining packages from dribble and livna into the repo; 
> latest status can be found here: 
> http://lists.rpmfusion.org/pipermail/rpmfusion-developers/2008-September/001073.html 
> 

I wish I could help here, but I'm going to the Linux Plumbers conference in 2 
days, so I'm afraid I'm out of the running for this round.

> - check that the upgrade path from Livna -> RPM Fusion is sane for each 
> package in each of the supported Fedora releases

I checked and with my set of livna packages, mpg321 is the only one which has a 
broken upgrade path. the evr's are the same so the .lvn9 wins from rpmfusions .fc10

> - start importing and building the remaining packages from freshrpms; I 
> can do that, but I want to get the ACK from thias first; especially as
> http://rpmfusion.org/InitialPackageMerge likely is not fully up to date

Erm, yes good point.

> - get the dep checker script from Fedora Extras/EPEL ( 
> http://cvs.fedoraproject.org/viewvc/extras-repoclosure/?root=fedora  ) 
> in place and let it automatically run after each successful push; if 
> possible without to much work get upgradecheck ( 
> http://cvs.fedoraproject.org/viewvc/upgradecheck/?root=fedora ) running 
> as well.
> 

+1

> 
> That round about it from the top of my head. Did I miss anything? 

Send out an announcement once we're live and organise a party, or maybe 
multiple parties (one per country) ?

Regards,

Hans