<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">2013/11/11 Miro Hrončok <span dir="ltr"><<a href="mailto:mhroncok@redhat.com" target="_blank">mhroncok@redhat.com</a>></span><br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Hi,<br>
I've joined RPMFusion recently and current infrastructurre bothers me.<br>
<br>
What blocks us from using Koji, Bodhi, git? Is it man power, hardware, money, licnese? How can I help with migrating to Koji and Bodhi and keep the infrastrucutre the same as Fedora has?<br></blockquote><div><br></div><div>
Hi Miro,<br><br></div><div>The problem is to get everything properly tested. Specially I'm reproducing my own koji instance (currently used for arm port), but it's not using pkgdb/bodhi yet and the koji policy isn't there. Right now I'm working on testing git/koji/ansible bridging.<br>
<br></div><div>That been said, from the packager perspective. I want to rely emphasis that the bottle neck isn't in the infra side. There are still lot of pending packages hanging for review and that's really make me sick not to have them in.<br>
</div><div><br></div><div>Also despite the plague infra isn't certainly outdated and I'm working on the move, it's probably more efficient and requires less resources to work than koji does, specially as we don't need to regen-repo each time the external repo have changed. So that's something that can eventually be worked on by someone else:<br>
</div><div>- having a script that detect the external-repo for each build target, store earch repomd.xml timestamp to immediately send a koji regen-repo command for any change. That would avoid the need to mirror the whole upstream fedora repo.<br>
<br></div><div>Also another task is to right now allow a bridge from cvs2git for the packager work. I know ktdreyer also use that to maintain xbmc, but I haven't seen anything appearing into the rpmfusion-packager package.<br>
<br></div><div>Also an unknown task is to convert the multilibs x86_64 plague config. I expect mash will handle the repo generation, but I don't know how to specify where to copy the steam.i686 (and others multilibs corner cases) to the x86_64 repository.<br>
</div><div><br></div><div>So it's just a few issues. Probably most could be sorted into the bugzilla, so anyone can pick simple task that do not need special access.<br>Here is the tracker bug I've just set:<br><a href="https://bugzilla.rpmfusion.org/show_bug.cgi?id=3023">https://bugzilla.rpmfusion.org/show_bug.cgi?id=3023</a><br>
<br></div><div>Nicolas (kwizart)<br></div><div><br><br><br><br></div><div><br><br></div><div><br><br></div><div> <br></div></div></div></div>