> 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 ;-)
- get the mirror manager that adrianr put in place (see
listed as mirrors.rpmfusion.org in DNS;
* adrianr: IP address
* thias: DNS update
Afterwards update rpmfusion-release packages accordingly.
- get the remaining packages from dribble and livna into the repo and
eveything fixed up; latest status can be found here:
- start importing and building the 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
Having a list of packages that are ready for importing would help things
- 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
- 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)
- get the dep checker script from Fedora Extras/EPEL in place and let it
automatically run after each successful push; if possible without to
much work get upgradecheck running as well (Xavier is working on it afaik)
- make sure all the kernel-modules from freshrpms are converted to
kmods; also make sure all the update path for frehsrpms dkms users to
- prepare a announcement mail
- put rpmfusion-release packages into livna-testing repos for F-8 and
F-9 to move all the testing users over
- move packages from testing -> stable for F-8 and F-9; build new
rpmfusion-release packages that have the testing repo disabled!
- put rpmfusion-release packages into livna repos for F-8 and F-9 to
move all the users over
= not that important =
- in parallel to all the above: work further on getting the crucial
packages into the EL repo for RPM Fusion (
). Libmp4v2 (needed by faad2) is still blocking that work right now;
- test if current comps.xml stuff works on rawhide-anaconda; if yes then
convert comps.xml from nonfree as well; details:
- are the nvidia bits sane? There were some mails about the 177series,
but seems some questions were not answered yet
= End =
That's 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 :-)
Help for all the remaining tasks much appreciated. The mroe help, the
quicker we can start RPM Fusion for real.
I've been a Fedora package maintainer for quite some time
(https://admin.fedoraproject.org/pkgdb/users/packages/), and currently
maintain Vagalume for Livna/RPMfusion (I do not have commit rights for
Livna, since Vagalume was reviewed just a couple of months ago, close
to the transition to RPMfusion).
I've set up my RPMfusion account, already have a Bugzilla account,
signed the CLA and requested membership in packagers and bugs. Could
one of the administrators approve my group membership?
(note that the owners list does not list the email I use for Bugzilla,
michel.sylvan(a)gmail.com, as I was using my fedoraproject.org email for
the changelog entries. The package was initially intended for
inclusion in Fedora, but while it does not contain any infringing
code, it is useless without an MP3 plugin for Gstreamer and so would
not have worked out of the box)
I see that rpmfusion is working already on Fedora but the
"Configuration page for users" is still empty:
Thank you for your hard work! My Fedora box automatically switched to
rpmfusion without a glitch and it is working perfectly!
linux, blog, anime, spirituality, windsurf, wireless
registered as user #367004 with the Linux Counter, http://counter.li.org.
ICQ: 2125241, Skype: valent.turkovic
> * having libdvdcvs in one of our repos could lead to projects or
> cooperation's not to mention or link to us. That's not limited to Fedora
> or Red Hat; also some journalists and howto-writers will also chose to
> *not* mention RPM Fusion and thus not link to us, as it might be to
> dangerous in some countries
I can just endorse that...
For me as an author of a German Fedora blog, I am always having mixed emotions
about Livna. On the one hand, it's undoubtedly an important repository for
Fedora. On the other hand, I am not allowed to mention it because this could
indirectly be illegal advertising for a copy protection remover, which can be
punished with up to one year of prison in Germany. I know that other German
Fedora authors are thinking the same about that. Livna is "that certain
repository" with sweet content, but also with a bad smell.
I also offer a web service where changes in yum repositories are constantly
tracked. I always wished to add Livna, but I didn't because of the same legal
I see it that way: You have put a lot of effort on RPMfusion. You already
offer a lot of packages that are important and also legal for non-commercial
distribution. RPMfusion will be, without any doubt, the most important 3rd
party repository for Fedora.
It would be sad to waste all this great work because of just a single package.
It would be stupid to give away all that free advertising in wikis and blogs
and magazines, just to keep that single package. After all, libdvdcss is just
a "rpm -ivh http://someotherserver" command away, for those people who really
want to have it.
Just my 2cc...
Richard "Shred" Körber
We are afaics getting closer to have RPM Fusion ready for the official
lunch, so if it's fine for everyone I'd say we move the all packages
from the rpmfusion updates-testing repos to the rpmfusion updates repos
for F8 and F9; at the same time put new rpmfusion-release packages into
the repo that have rpmfusion updates-testing disabled.
A few days later we then should start to use rpmfusion updates-testing
properly -- e.g. build and ship kmods and other packages in rpmfusion
updates-testing to match the packages from fedoras updates-testing repos.
Does that sound fine for everybody?
Packages built and released for RPM Fusion (Fedora - free) development: 1
Changes in RPM Fusion (Fedora - free) development:
* Wed Oct 29 2008 Sebastian Vahl <fedora(a)deadbabylon.de> - 0.6.4-1
- new upstream version: 0.6.4
Packages built and released for RPM Fusion (Fedora - nonfree) 9: 1
Changes in RPM Fusion (Fedora - nonfree) 9:
* Wed Oct 29 2008 Julian Sikorski <belegdol[at]gmail[dot]com> - 0.2-0.7.b5.fc9.1
- Rebuilt, as something seems to have eaten a part of i386 rpm