When do you plan to upgrade? We will need packages in building state for https://fedoraproject.org/wiki/Changes/Python3.10 during May (wiki does not load for me now, but the page includes specific dates).

I'd hope to have 4.17 in rawhide during April.

That has a potential to cause a lot of friction for us due to the high number of packages that will FTBFS, however many of the failed packages are ruby packages. I'll compare the list of failures with the list of Python packages and report back.

If necessary it's always possible to temporarily alter behavior by setting %_unpackaged_files_terminate_build to 0 on the appropriate level (even all of rawhide if necessary).

asciidoc
botan
cantoolz
colin
compizconfig-python
conda
dnf
etckeeper
ginga
glances
glusterfs
gpaw
ikiwiki
ipython
libcaca
libdnet
libuser
module-build-service
mom
nfs-ganesha
numpy
odcs
omniORBpy
openwsman
pacemaker
pcs
poetry
pyflakes
pyotherside
python-actdiag
python-bashate
python-btlewrap
python-cachy
python-cu2qu
python-debtcollector
python-dill
python-django-markdownx
python-dulwich
python-edgegrid
python-editdistance
python-ephem
python-fastcache
python-fedora
python-funcparserlib
python-gabbi
python-glusterfs-api
python-humanize
python-cherrypy
python-imagehash
python-ipgetter2
python-jaraco-classes
python-jaraco-collections
python-jaraco-envs
python-jaraco-functools
python-jaraco-text
python-lacrosse
python-libdiscid
python-libsass
python-matplotlib
python-multipart
python-murano-pkg-check
python-mygpoclient
python-netapp-lib
python-nptyping
python-nwdiag
python-opencensus
python-opencensus-proto
python-openshift
python-path
python-pygraphviz
python-pygrocy
python-pyinels
python-pysmt
python-pytenable
python-pytest-spec
python-pyudev
python-pyvit
python-repoze-who-plugins-sa
python-seqdiag
python-shapely
python-sql
python-subvertpy
python-teslajsonpy
python-tld
python-typish
python-upnpy
python-websocket-client
python-xmlschema
python-yarg
python-ZConfig
python-zope-event
python-zope-exceptions
python-zope-interface
python-zope-schema
python-zope-sqlalchemy
python-zope-testing
python-zope-testrunner
pywebdav
rmlint
rrdtool
speedtest-cli
speech-dispatcher
sudo
sugar-toolkit-gtk3
tuned
389-ds-base

This will complicate things. I'll bring that concern to the devel list discussion once the change proposal is announced.

If necessary it's always possible to temporarily alter behavior by setting %_unpackaged_files_terminate_build to 0 on the appropriate level (even all of rawhide if necessary).

Release engineers, is it possible to set the config_opts['macros']['%_unpackaged_files_terminate_build'] mock option for a side tag?

If it's set for a side tag only then we'll have packages that are mysteriously being built despite failing to build on rawhide. I think it'd be saner to just flick the switch on all of rawhide for a few months to smoothen the ride if need be (I made an explicit note of this in the change now)

It is possible to set in a side tag. But I agree, if it's just set there it will confuse people as to why they don't build in regular rawhide.

Most of the above is moot now. The strict content checking was reverted upstream for this release (too many battles on too many fronts) and the implicit database creation is handled again (a bit differently) for the case of installing into an empty chroot so dnf/mock wont need any changes for this afterall.