On Fri, Nov 15, 2024 at 1:42 AM Ryan Bach via devel <devel@xxxxxxxxxxxxxxxxxxxxxxx> wrote: > https://release-monitoring.org/project/1887/ > 11.7.1 For MySQL I tried to configure the upstream release monitoring to only pick the latest version of the same major version, but I reached a conclusion that's a complexity way out of the tool's current capability. (even by having a new separate monitoring config for e.g. 'mysql8.0' specifically, to not mess with other consumers of the current config) For both MariaDB and MySQL, I'd be happier to have the tool to update a BZ about the latest release of the current major version, in which I could be more (re)active. As it is currently, I only have it as a recurring notification that the upstream release window is here. If there are some masters of Anitya-fu present, I'm happy to hear suggestions :) -- On Fri, Nov 15, 2024 at 6:00 AM pgnd <pgnd@xxxxxxxxxxxx> wrote: > it's entirely possible there's an up-to-date/reliable solution from distro, and i've missed it. > i don't bother to keep up with it anymore. I'm sorry to hear the upgrade path that should be seamless from user POV haven't worked for you. I would be happy to hear suggestions on how to improve the current handling of the 'mariadb10.11' package so users won't notice. > upstream MariaDB project _does_ provide binaries. including dnf repos for Fedora. or at least they did ... > they're of course authoritative for the _sources_. > i don't find their packaging reliable for Fedora -- in the past repos version-lagged for months+ on release, often in a broken state. fedora packaging never seemed a priority. There is the MariaDB Corporation and the MariaDB Foundation. Priority of the first one is making money, priority of the second one is keeping it open-source. (and more: https://mariadb.com/kb/en/mariadb-foundation/) Similar to Linux distributions or other such projects, much of the work of the Foundation is on a best effort basis. I share your observation and I'm long-term trying to address the situation at least by reporting it and poking here and there, making suggestions and asking for improvements. But as with anything in the FOSS world, the biggest change you can make is to start directly contributing fixes to what pains *you*. > i no longer use any MDB from distro. especially not for any server/enterprise use. > > otoh, DIY builds @ COPR, or locally with mock, are fairly straightforward. for both LTS and current releases. > my own LTS builds for F41 behave well here in operation. atm, > > mariadb -V > mariadb from 11.4.5-MariaDB, client 15.2 for Linux (x86_64) using readline 5.1 > > galera does give me occasional build problems; typically for rawhide ... > > ymmv -- and you get the +/- of DIY, as usual. I would be happy to find a contributor willing to maintain continual contributions to some version of MariaDB in Fedora. You seem like you do the maintenance work yourself anyway - would you like to see the 11.4 LTS available to all of the Fedora users too? Once the Fedora Review of the new package (mariadb11.4) is done (not yet started), the patches or PR workflow would be ideal for me. > on the + side, upstream community _will_ talk to you if you've built from source, or use their bins. Yes, the MariaDB community is great, welcoming and enthusiastic. I'm happy to hear you enjoy it too. Michal -- Michal Schorm Software Engineer Databases Team Red Hat -- -- _______________________________________________ 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
