* Kevin Fenzi: > On Wed, Oct 26, 2022 at 10:23:40AM +0200, Florian Weimer wrote: >> * Zbigniew Jędrzejewski-Szmek: >> >> > On Tue, Oct 25, 2022 at 10:05:52AM -0400, Ben Cotton wrote: > > ...snip... > >> >> == How To Test == >> > >> > As discussed by others, this needs to explain how to opt-in for early >> > testing, and also how to opt-out in packages, how to opt-out as a user >> > (if the default touches users), etc. >> >> The challenge with that is that I've been told not to do this work in >> Fedora proper by release engineering, and a request for a long-living >> side tag with a suitable compiler has not been approved: >> >> Long-term side tag for toolchain experiment >> <https://pagure.io/releng/issue/10392> > > Sorry that got dropped... > > The thread about it I suggested copr, some other folks thought that > might work, and I don't recall ever hearing if that would work for you > or not. So, seems communication broke down here somewhere. > > I suppose it's too late now for this to matter aside from us trying to > not have it happen again? In the future, if a releng issue gets stuck, > please do drop by the releng and infra standups (mon/tue/wed/thu) at > 18UTC in #fedora-meeting-3 / meeting-3:fedoraproject.org and bring up > the issue. Okay, I'll keep this in mind, thanks. >> More recently, I was explicitly told not to keep the compiler changes on >> a branch in Fedora dist-git. >> >> It is not really possible to get realistic testing through compiler flag >> injection because crufty old code that is problematic for these changes >> often does not inject flags properly. Certain likely changes cannot be >> modeled through -Werror= options (but can be patched into GCC). Some >> build systems explicitly filter out -Werror= options during the >> configure stage (generally a good idea, but not helpful here). >> >> So I'm a bit at a loss what to do here. Maybe releng can reconsider >> their approach. > > So, can you say that copr definitely will not work for this? As far as I can tell, COPR doesn't do scratch builds. So if I publish a repository in COPR with everything required in it, Fedora developers still cannot run a single command that uploads some SRPMs and runs a build with the right buildroot configuration. They have to create their own COPR project first and build into that. Maybe it's possible to script this in some way. Maybe it's also possible to provide a reference mock configuration for local builds. But I think it's going to be less convenient for packagers than running a scratch build against Koji. Thanks, Florian _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
