You catch me in an terrible week ...
I know that still many thing todo, but for me , my role , is
what I call the software , if we can
organize the software, package maintainers can start to work , if we
can keep software centralized, for me this is the most important, with
a mirror in github, anyone can build it in his own environment ...
About other repos of replacement RPMfusion , I see all over the places,
Russian Fedora , Chinese Fedora FZUG repository (http://repo.fdzh.org/F
ZUG) , Andreas rebuild for f24 , (my) unitedrmps and more, negativo,
but I want bring they all back to RPMFusion , meanwhile we gain
experience in builds for F24 .
Now practical things , http://koji.rpmfusion.org only have one build
target which is f24-free, meanwhile we got f23 branched , and now
master points to f24 isn't it ?
So we want updates for F24 ! to build in new koji isn't it ?
Kwizart, I saw you also update rpmfusion-free-release-23 to -1 , you
also are planing move f23 to stable ? , after should be easier do the
f23 target on new koji, also we can declare f22 as eol :) to have much
less work ...
I still don't finish rfpkg (as promised) , but may I test rfpkg, for
example, try upload Virtualbox sources and commit new upstream updates
, in master , for F24 ?
On Seg, 2016-05-16 at 11:48 +0200, Nicolas Chauvet wrote:
Hi RPM Fusion developpers
As some of you are aware, out of the mud, a the new shini
infrastructure has rised up!
There is a new koji instance and a git repository living at:
(even with let's encrypt certificate).
This morning, I was able to restore the git hook to sync to github
(remember that github is a read only mirror). Most packages from the
free section are branched for f23 ( there is a need to understand why
a minor portion has failed and need to be repaired), so devel branch
is currently f24.
Contributors still cannot push until pkgdb2 is setup, so for now the
priority is for packages that fail to build in f24, you can submit a
github pull request or open a bugzilla.
There are lot of tasks remaing to have the new infra fully working,
- rfpkg (http://github.com/rpmfusion-infra/rfpkg
If you want to help, you need to dive into the code of theses
projects, setup your test own instance locally and submit patch
upstream to adapt to our needs.
Also some theme adaption would be welcomed.
If you want to pick a task, please mention it there and keep us
informed from your improvements.
Please try to avoid asking what you can do, please do something (have
a look on https://bugzilla.rpmfusion.org/show_bug.cgi?id=3023
Also to mention is that the new infra is ansible managed (old
are still using puppet), the public part is located here:
That's for thoses who wondered how to help, here what you "could"
done. Reviewing is welcomed.
From my side, there are lot more actions that I cannot list here, so
any help is appreciated.
Hopefully, next year I will have a day off!
Last word to mention, some project started as a replacement for RPM
Fusion. While it's probably a good opportunity to learn how to start
self repository / project, I just remind that it will also put Fedora
users into a conflicting situation where packages from one repo will
behave badly with packages from others repos. (missing options,
So I really hope theses new repositories will find their way to our
PS: I have some issue with gmail email rate limitations, if you want
an info from me, please drop by #rpmfusion on IRC freenodes.
Sérgio M. B.