2016-06-11 4:14 GMT+02:00 Sérgio Basto <[email protected]>: > Hi, > Finally though in make rfpkg just fedpkg with new configuration , so > rfpkg could be an alias like this: > > alias rfpkg='fedpkg --config /etc/rpkg/rfpkg.conf' > > so we got two new files > /etc/rpkg/rfpkg.conf and > /etc/koji.rf.conf (configuration of koji) in attach .
You can have a look at what is already available in github.com/rpmfusion-infra/rfpkg Your version is interesting, why do you need the clone options on the client side ? For example the sendemail [email protected] is setup on the server side, not something can be changed from clients clones. koji client configuration should be located in /etc/koji/rpmfusion-config I've pushed a version in rpmfusion-packager. > Now, we need the equivalent of fedora-cert [1] and we already > have rpmfusion-packager ( the equivalent of fedora-packager ) which > have the old command /usr/bin/rpmfusion-packager-setup. This rpmfusion- > packager-setup give me clues about where is rpmfusion-upload-ca.cert > and rpmfusion-server-ca.cert, this are the correct certificates ? Yes > > Downloading certificates manually, I end up with > pyrpkg.errors.UploadError: (60, "Peer's Certificate issuer is not > recognized.") because > https://fas.rpmfusion.org/accounts/rpmfusion-upload-ca.cert is not a > secure cert ... This is a self signed cert, (so not even a cacert file) We should migrate the fas to the new infra with the new reverse proxy setup so we can use a letsencrypt certificate easily. Please try to use the certificate fingerprint if possible unil the fas is migrated to a well trusted CA. > Tomorrow I hope to continue devel this tools tomorrow. Thx, you are on the right path
