Re: Next steps to get RPM Fusion running

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 - 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) - 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. 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). If that works out fine I plan to do the same for Fedora {8,9}-testing a few days later. = 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/... Anybody can help with this -- pick a package, poke the maintainer directly via mail or irc; if he doesn't react at all for a few days consider to take a closer look at the package and its problem; if you can make it work send me a patch and I'll apply it to CVS and queue the build. - check that the upgrade path from Livna -> RPM Fusion is sane for each package in each of the supported Fedora releases - 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 - 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.

= not that important = - in parallel to all the above: work further on getting the crucial packages into the EL repo for RPM Fusion ( http://lists.rpmfusion.org/pipermail/rpmfusion-developers/2008-September/... ). Libmp4v2 (needed by faad2) is blocking that work right now; libmp4v2 is in Fedora and EPEL4, but not build for EPEL5 yet. Don't know why; wrote thias (who maintains libmp4v2 in Fedora and EPEL) a mail about it a week ago, no answer yet :-/

= End = That round about it from the top of my head. Did I miss anything? Likely, but I think I'm optimistic that I got the most important things on the list :-) Cu knurd