Include minor version number in packaged Python shebangs
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, but at runtime only invoke "Python 3", not 3.6 specifically. It seems that I still need Python 3.6 for most packages installed via DNF on EL8, but I also definitely need Python 3.8+ for multiple packages I use installed with PIP. So, the workaround to having both installed on my system at the same time would be to edit the shebangs to include the minor version of Python that each application requires. ...Right? I wanted a sanity check before I bother sending spam to EPEL package maintainers. Or, is this even a reasonable thing to ask package maintainers to change, or should I just start patching the local shebangs myself? Or is there a better solution? ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Retiring/orphaning my packages
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 computer activity and other junk files to free disk space and maintain privacy * Lector (lector) -- ebook reader and collection manager * MuseScore (mscore) -- WYSIWYG sheet music composition/notation/playback -- I was only a comaintainer, but I imagine that jjames would appreciate another comaintainer in my place, as builds of this app can be a little tricky... Libraries: * python-djvulibre -- Python wrapper for djvulibre, which gives open-source implementation of the djvu document file format (mostly used by Lector, I think) GNOME Shell Extensions: * Activities Configurator (gnome-shell-extension-activities-configurator) -- customize the top bar and Activities button * Do Not Disturb Button (gnome-shell-extension-do-not-disturb-button) -- toggle do-not-disturb-mode with a top bar button and configurable hot key * Freon (gnome-shell-extension-freon) -- show realtime system temperatures and other info * HistoryManager Prefix Search (gnome-shell-extension-historymanager-prefix-search) -- better autocompletions for the Alt+F2 run dialog * No Topleft Hot Corner (gnome-shell-extension-no-topleft-hot-corner) -- simply disables the top-left hot corner (mostly for EPEL, now, which doesn't yet have a new enough version of GNOME Shell to do this in regular settings) * TopIcons Plus (gnome-shell-extension-topicons-plus) -- add app "system tray" icons back into the top bar (arguably obsoleted by AppIndicator, but might still work better for certain apps) * WindowOverlay Icons (gnome-shell-extension-windowoverlay-icons) -- add app logo icons over the window thumbnails in Activities Overview ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Koji query to get the source commit for a build
> 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 the full NVR string... - feed that to `fedpkg gitbuildhash` ...Yeah, this could work. I hadn't considered querying with fedpkg, so thanks a lot for the tip! ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Koji query to get the source commit for a build
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 how to make it include the source. Possibly with the `--xkey` or `--show` switches? But neither `--xkey=source` nor `--show=source` seems to do anything. I can't tell what the property name would be to get the source commits for a given build here. Or, `koji list-tasks` does show the commits -- but it can't filter by package name, and the full NVR and source commit are on separate lines, so I'm in regular-expression hell trying to figure out how to grep or sed the output such that it will show matching pairs of NVRs and source commits... Any ideas? ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
