we have updated the Copr stack to the newest versions of our packages.
This was a first major release after months, so you can expect many
The common theme for this release was to speed-up the frontend
interface, optimize internals and improve the user experience with
small UI changes.
The full list of release notes might come later.
I have prepared commit, but I am waiting untill https://pagure.io/copr/copr/pull-request/526 is merged, because it has
-------- Přeposlaná zpráva --------
Předmět: python3-configparser is going away, update packages please
Datum: Fri, 8 Feb 2019 06:05:08 -0500
Od: Avram Lubkin <aviso(a)rockhopper.net>
Komu: copr-backend-owner(a)fedoraproject.org, copr-rpmbuild-owner(a)fedoraproject.org,
graphite-web-owner(a)fedoraproject.org, python3-carbon-owner(a)fedoraproject.org, python3-copr-owner(a)fedoraproject.org,
python3-libtaskotron-owner(a)fedoraproject.org, python3-x2go-owner(a)fedoraproject.org, rpkg-owner(a)fedoraproject.org
Kopie: jamatos(a)fc.up.pt, itamar(a)ispbrasil.com.br
The following packages currently require python3-configparser. Since configparser is included in the standard library it
really shouldn't exist. python-configparser will go away completely once no python2 packages depend on it, but we'll
likely drop the python3-configparser package with the next update which should be coming out relatively soon.
The following packages currently have a dependency on pthon3-configparser. Please update your package to remove this
copr-backend (F29, Rawhide)
First, thanks for copr and to all who built and maintain it. It is excellent and now my preferred way of building RPMs for free/libre/open source software.
Is there a way that long-running jobs (I'm thinking kernel, gcc etc) can be assigned to their own dedicated build servers? The packages I build are usually quick (a few minutes) but they sometimes have to wait a long time for these longer jobs to finish.
Failing that, is there a way to spin-up a private build server tied to my project?