Mmm, COPR and Koji I think use the same mock configs but someone else would have to confirm that :)
It's definitely possible that one of a packages build dependencies pulls in something that a package /should/ depend on and then when it drops it suddenly the build fails. That's why I think we mostly want 'autogenerated' BuildRequires nowadays that are generated based on the upstream source or packaging format to make that less of a figuring out excercise.
Personally I feel a good way to get involved is to test updates in bodhi for those packages you care about, or to take part in the process that happens around release time where we go through several freeze cycles and have 'blocker bugs' that need their fixes to be validated: https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process
The activation of the virtualenv is unnecessary (one can execute pip/python directly from it), and the configuring of your local pyenv interpreter is also unnecessary, it can create a virtual environment with one directly:
Cool idea. I would be interested in knowing the concentration you achieve and flow rates (LPM/CFH). This wouldn't work in my workshop as we don't treat our equipment nicely enough and we don't have sparkies to tend to it.
> Roberts, 38, now only gets fast food "as a rare treat".
I feel that that is it should be? When I was young it was important enough to mention at the monday class circle if your grandparents had taken you to visit the Golden Arches and everyone would be very jealous.
I've often thought about why the default implementation of many randoms around programming languages is to use LSFRs, MTs, and other fast RNGs in the 2020s.
It seems to be better to err on the side of 'people dont know if they want a PRNG or a CSPRNG' and switch the default to the latter with an explicit choice for the former for people that know what they need :)
Really the only web interface I consider putting on my machines is this one as it uses the normal system as available instead of doing everything custom.
It sadly seems that information on the outage is slow and far in between, stuck on an update once every 8 or so hours apparently with a bunch of VMs sadly still being unreachable and unresponsive in the management console :(