Dne 6.5.2015 v 21:08 Kevin Fenzi napsal(a): > How about a short term and a longer term plan? > > Short term: have copr download and store the src.rpm from build urls. > This would at least make things reproducable and at least someone could > download the src.rpm and send a patch. Along with this a easy way to > mail the owner of a copr would be good. Nope, short term is that user select SRPM and do "file upload" from form -- or provide url. And the result will be stored in dist-git. So they do not need to host src.rpm on some public site. > Longer term: use pagure. Have people setup their project there and work > with pagure folks to integrate copr. We could have an easy 'build this > in copr' type thing and on the copr side a 'visit this project on > pagure'. I really dislike to store project in pagure. Unless it have git-annex or similar and we store there just spec and SOURCEX as in dist-git. We could not force users to move their github project to pagure. > I think trying to do a standalone dist-get will just cause problems > when/if we want to move to something like pagure and has a lot of > issues without building up a bunch of infrastructure around it. Why it should cause trouble. The goal is to have literally copy of fedora-dist. Just have it on different HW/Storage. Then every change would be just carbon copy. -- Miroslav Suchy, RHCA Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsys _______________________________________________ infrastructure mailing list infrastructure@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/infrastructure
