https://bugzilla.rpmfusion.org/show_bug.cgi?id=3827
--- Comment #10 from Nicolas Chauvet <kwizart(a)gmail.com> 2015-11-11 11:43:26 CET
---
We need to package rfpkg in order to migrate our epel5 support for the new
infra. But I would say we can drop support for EL5 given the lack of updates.
I was able to clone, both as authenticated (git preview) and anononymous (from
github). So that's okay.
rfpkg-free and rfpkg-nonfree should probably be made. We will know and pass the
tree (free/nonfree) in severals rpkg methods (upload/koji build submission/).
I would say have the section passed-in the script file (aka rfpkg -C
/etc/rpkg/rfpkg-free.conf -t free "$@")
Nothing should be missing in order to use the current upload mechanism, but we
will need to pass the section in upload. I might need to change the server side
certificate.
FYI, I've spent time to extract the curl line to currently used to upload:
upload-file = curl -k --cert ~/.rpmfusion.cert --fail --silent -F "tree=free"
-F "name=xmltv" -F "md5sum=7f95c24f91a7ac48cf81c32b21dc0492" -F
"file=(a)xmltv-0.5.67.tar.bz2"
https://cvs.rpmfusion.org/repo/pkgs/upload.cgi
So the upload method probably needs to be overriden from rpkg to do that.
Last it would be nice to see what can be backported from fedpkg 1.21 to rfpkg
@Antonio, if you can handle some of theses actions, it would be nice. None of
them (exept for the server side certificate for
cvs.rpmfusion.org) requires any
access from the infra.
--
Configure bugmail:
https://bugzilla.rpmfusion.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.