DNF modules let you install multiple different versions of Python 3, and the
`alternatives` tool lets you change which is the default version invoked by
`/usr/bin/python3`.
However, at least for *Enterprise Linux 8, it seems a lot of packages were
built assuming the distro's default Python 3.6,
I should have done this a long time ago; I don't have the time or energy to
maintain my packages anymore 🙁
If anyone is interested in any of these, you're welcome to take them.
https://src.fedoraproject.org/user/terrycloth/projects
Applications:
* BleachBit (bleachbit) -- delete traces of your
> Does "fedpkg gitbuildhash" do what you want?
Hmm, not by itself, mostly because I need to already know the version-release
numbers I'm looking up.
However, it could immensely simplify the regex I was using. Now it should look
more like
- `koji list-history --package="$pkg_name"`
- grep for t
I'm interested in looking up the source used for different builds on Koji --
particularly the exact commit to the spec file's repo, when building from SCM
-- in a scriptable way.
`koji list-history` has the most filtering options, so it seems like it *ought*
to work... but I can't figure out ho
