Just in case you run out of ideas about making Copr even better, I just saw
this feedback on the Fedora Telegram channel comparing Fedora Copr and Arch
Justing W. Flory: Fedora has a similar concept with Copr, but it's not as
widely used as AURs.
lian.rs: Copr is not quite that. Copr is more like Ubuntu PPAs, and lacks
many features such as voting, forum for each package, being able to review
the package before installing, etc, and most importantly Copr is a repo
tool, not a packaging tool. You need to know in advance the repo that
contains the software you want to install. It's not as convenient :("
As a former Arch Linux user I kind of agree. Having some voting mechanism
and maybe even the forum/discussions would be fantastic!
What do you guys think? I don't have that much time for Copr as I used to,
but, as always, I'm happy to help with UI! ;-)
updated COPR stack has been just deployed into production. This included
1) new release of copr-frontend (1.107-1) has been deployed
The main features of this release include re-enabling fedora-rawhide as
chroot names, compatibility with python2-flask-whooshee-0.4.1-2, and
finally updates related to support of Module Build Service (MBS).
2) copr-backend was redeployed for mock 1.3.4 support
The backend configuration was updated to support the new mock 1.3.4. Note
that fedora-26-* chroots will not work until the respective repositories
are publicly available. Before, rawhide repositories were used for f26
chroots but today, that needed to be changed for the rawhide branching.
Mainly because of this unpleasant config switching, we decided that
returning fedora-rawhide -* back is the best option. It will be kept as
long as mock keeps it. We run on mock and we need to play with it well.
Note that previous backend rawhide repositories are available in your
backend directories "-backup" suffixed. Otherwise, we are starting from
scratch there and new repositories will be auto-created for the new rawhide
builds. We are also starting fresh on copr-dist-git where the previous
master branch has been renamed to master-backup and new master is ready for
3) a long-standing copr-keygen issue "Keygen service error" has been
This issue should no longer occur (at least not for the same reason). Let
me know if it runs well.
There are still unsolved network problems, which cause COPR to underperform
these days while also requiring day-to-day copr-backend service
stop/starts. We are now going to debug these into depth.
The ultimate goal now is to make COPR stable and reliable.