You know as well as I do that breakages of entirely unrelated packages cannot be found via devel branches. Ultimately Factory staging cannot be duplicated there, at least due to the package build limit per project. I did not see these two two ring packages raised before by staging. But now that we know, and the rings-must-build requirement is clear, we can have a look, like @pluskalm and myself did for others.

We could use openSUSE:Factory:Staging:O for such experiments, but neither @mimi_vx or me can commit there to see what else breaks

you can use ANY branch - OBS is really cool :)

for pkg in $(osc whatdependson openSUSE:Factory scons standard x86_64 | awk '{print $1}'); do
  osc branch openSUSE:Factory $pkg home:pluskal:sconsbranch;
done

It's only 25 packages in total.

Right, because I did not know that obs was cool.

Yep - I have to admit that I did not expect that much issues with scons

And as I see in https://build.opensuse.org/project/monitor/home:pluskalm:python3 most of scons packages will need fixing :(

I'll be taking care of gpick - maybe you can post to the factory ML about this change with a list of the packages that are failing and need work?

The ones in the ring are mandatory to be solved before the scons change can be accepted, but it is definitivley nice to work with the maintainers, giving them a chance to fix their things upfront.

whereas I buy this argument for things like gcc and glibc, I have a fair amount of trouble believing it for scons.

osc whatdependson openSUSE:Factory scons lists only 25 packages and such an intrusive thing as changing python interpreter it's really not too much to ask from maintainers/developers to branch those 25 packages together into a workspace and have scons changed.

It is not too much to ask, and certainly a straightforward thing to do once flagged by by staging. As I repeatedly pointed out, are looking at the failures. I am not sure if obvious CLI snippets are required.