just a quick note - we enabled Oracle Linux chroots in Fedora Copr today,
this is temporarily needed by OAMG/LEAPP team for their CI/CD system.
Feel free to test those chroots, but please don't heavily depend on them
as we don't know when we'll again drop them (preferably use
epel/centos-stream chroots instead, they should provide similar build results).
we are currently preparing Copr build system for migration to Fedora 35,
including the builder workers.
There's though, at least from the builder perspective, a major `rpkg-util`
behavior change  (removal of `auto_pack` feature) that many of the Copr
projects rely on. This is a bit unexpected as `auto_pack = True` has been
the default in Copr for a long time, and the rpkg-util upstream intentions
behind the feature were generally misunderstood (even in Copr team).
That being said, some of the currently working builds on F34 would fail
after the migration to F35.
In order to make the migration a bit less dramatic, we plan to migrate in
the following steps:
1. Document the feature drop and possible fixes/workarounds see , and
properly announce the change in advance (here we are _now_).
2. Change the default, and turn off the `auto_pack` feature for
relatively short period of time on the current F34 builders
(ie autopack=False). This will happen soon in December 2021.
The change will naturally trigger the build failures, but a bit
earlier so users will be informed sooner ... with a _temporary_
work-around in hand => everyone can provide the file
<git-root>/rpkg.conf upstream, and opt-in the old behavior with with
# temporary work-around for rpkg-util v2, auto_pack is going to be
# removed soon! See:
auto_pack = True
3. Migrate to Fedora 35, early in January 2022. This will make the
`auto_pack = True` work-around non-working, and users will have to
adapt, again, see .
Of course, anyone is encouraged to migrate to the new syntax **right now**,
sooner the better. If done correctly, package can be built both with rpkg-util
v2 and v3 .
Sorry for inconvenience! Any comment, idea or help is welcome!
There will be an outage starting at:
$ date --date '2021-11-30 12: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 servers from Fedora 33 to Fedora 35
copr-frontend - https://copr.fedorainfracloud.org
copr-backend - https://copr-be.cloud.fedoraproject.org/
@frostyx / @schlupov / @praiskup
Please join #fedora-admin in irc.liebra.chat or add comments to the ticket for
this outage above.
Hello Fedora EPEL maintainers!
First I don't feel comfortable announcing this, I'm not happy about the
situation and so I don't want to be the lightning rod :-). But I believe
that we can come to acceptable Copr/Mock solution and this needs to be
discussed... so here we are.
By the end of the year 2021 we have to fix our default EPEL 8 Mock
configuration (mock-core-configs.rpm, /etc/mock/epel-8-*.cfg) as CentOS 8
goes EOL by then.
The same thing needs to happen in Fedora Copr, with the epel-8-* chroots
(side note, in Fedora Copr we use the mock-core-configs package for builds
without any deployment specific modifications).
I am proposing (as PR against mock upstream ATM ) to switch the default
epel-* configuration from CentOS+EPEL to RHEL+EPEL as soon as possible
(see the pull request ).
This would bring some consequences, namely newly with epel-8* chroots,
- builds will require a valid Red Hat subscription (the no-cost variant is
OK as well, though )
- we will miss some build-time packages that Red Hat is not shipping, at
least at the beginning till they are added (to RHEL CRB, or other
currently unknown place).
- cross-arch compilation can not be used, Red Hat subscriptions don't
allow that (using QEMU and rpm --forcearch), 
The positive thing is that the default configuration will be much closer
to the official EPEL builds (because Fedora Koji EPEL builds are actually done
also against RHEL).
For the Fedora Copr builders, we already have the necessary Red Hat
subscriptions in hand (will be deployed by the end of the year). So we will
only loose the opportunity to build on emulated epel-8-armhfp permanently, and
epel-8-s390x temporarily (as we already work on the native s390x support).
Any thoughts? Feedback is needed here.