Due to problems with free disk storage, Copr will be temporarily deleting
failed and outdated builds after 7 days instead of the default 14 days
until migration to another disk storage takes place.
Hey COPR Developers,
Recently, I am trying to deploy COPR containers on an arm instance,
except for the base image and resalloc pool tag issues, I also found there
is a strange thing on bash command, check this code from dist-git  below:
if [ ! -w $REPODIR ] ; then
echo "ERROR: You can not write to $REPODIR"
echo "ERROR: You can not create repos"
This would always fail in an aarch64 container which uses the identical
dockerfile as the x86 ones.
Could this be a fedora issue? Considering I tried fedora 35/36/37 which all
There will be an outage starting at:
$ date --date "2022-09-21 13:00 UTC"
The outage will last approximately 3 hours. The copr-backend storage (copr build results) will stay mostly online during this outage but some downtime is expected.
Reason for outage:
We're updating copr packages to the new versions which will bring new
features and bugfixes.
copr-frontend - https://copr.fedorainfracloud.org
copr-backend - https://copr-be.cloud.fedoraproject.org/
@frostyx / @praiskup / @nikromen
Please join #fedora-admin in irc.libera.chat or add comments to the ticket for this outage above.
I'm looking at this page:
Status: failed - Build failed. See logs for more details.
I do not see an obvious link to the "logs" that it is telling to me view.
After enough clicking I figured out that its in the chroot that I need to look.
Maybe make "See logs for more details." link logs to the chroot?