Hi, While looking into the packages on my F31 that were not rebuilt for F31, I was looking at tk and why it was not rebuilt for F31 - it appears this package has a noautobuild file in dist-git.  Should packages still be allowed to opt-out of mass rebuilds?  I can't find any recent documentation about noautobuild or reminders to maintainers to manually rebuild their packages.

Yeah, looks like mass rebuild just skips these packages: https://pagure.io/releng/blob/master/f/scripts/mass-rebuild.py#_125 I am wondering if it wouldn't make sense to do a scratch build in that case and proceed with normal FTBS policy [0] if it fails.

[0] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fai...

>> Yeah, looks like mass rebuild just skips these packages: >> https://pagure.io/releng/blob/master/f/scripts/mass-rebuild.py#_125 >> >> I am wondering if it wouldn't make sense to do a scratch build in that >> case and proceed with normal FTBS policy [0] if it fails. > > The policy will eventually kick in. Recent changes make it so that packages > that haven't rebuilt for certain number of releases will be retired with > announcements. Even if releng have never attempted to do so. > > That means that if packages with noautobuild fail to build, nobody will > notice for ~year and than the maintainer have 6 weeks to fix it. \o/ > > I strongly suggest we should revisit all our noautobuild packages. For example, for tk, the commit says: 2014-05-21 Added noautobuild, tcl/tk-8.6 cannot be automatically rebuild now https://src.fedoraproject.org/rpms/tk/c/90966fa?branch=master But the package was rebuilt couple times in the last 5 years actually.