So far you are the only voice I've heard, which does not convince me - yet - to take such dire measures.
There are no BZ tickets on this topic, no discussion.fp.o threads etc. related to this issue. My plan was to merge the PR and put it to BODHI with automatic push-to-stable disabled so I could gather substantially more feedback on it. I just haven't got a peer review on the PR yet. Since the fix is more my "best effort" than something I am able to test thoroughly myself, I definitely want a second engineering opinion on it. Until then, it would be great if you could test the scratch builds I've provided you with. (by installing the packages downloaded right from the Koji build system) I've also haven't reported it upstream just yet (it already has one upstream tracker opened), as I want to get a better sense of how severe the issue actually is in practice and how many people are affected. Michal -- Michal Schorm Senior Software Engineer Databases Team Red Hat -- On Mon, Jun 29, 2026 at 3:49 PM <[email protected]> wrote: > > Hi Michal, > > Looking at the fedora 44 status at > https://bodhi.fedoraproject.org/updates/?packages=mariadb-connector-c > I see this connector was not un-pushed and no new replacement was provided. > Doing 'dnf update' (after I downgraded) the bad version is still offered. > > Seeing the severity of the problem (I am not the only one encountering it) > should it still be offered? > > Regards, > Eyal > > On 28/6/26 23:02, Michal Schorm wrote: > > Hello, > > > > I am the maintainer of the package 'mariadb-connector-c'. > > I am sorry for your issue, thanks for letting me know. > > > > I analyzed your issue based on your description. It seems to be an > > unfortunate regression in the upstream code that causes the temporal > > data type to be stored with zero length, resulting in the symptoms you > > are observing. > > > > I will need MariaDB upstream to verify this and create a proper fix. > > Until then, I attempted to create a downstream patch: > > https://src.fedoraproject.org/rpms/mariadb-connector-c/pull-request/27 > > > > Could you please test the PR scratch build and check whether it solves > > the issue for you? > > Rawhide scratch build: > > https://koji.fedoraproject.org/koji/taskinfo?taskID=147147264 > > F44 scratch build: > > https://koji.fedoraproject.org/koji/taskinfo?taskID=147147459 > > > > > > Michal > > > > -- > > > > Michal Schorm > > Senior Software Engineer > > Databases Team > > Red Hat > > > > -- > > > > On Sun, Jun 28, 2026 at 1:35 PM <[email protected]> wrote: > >> > >> This version picked by my server today. fc44 on x86_64. > >> > >> I do not know what is responsible but downgrading to 3.4.8 solved the > >> problem. > >> > >> Maybe a clash between rpmfusion and fedora? > >> > >> It looks like it may me a major problem with handling date/time. All > >> "Previously Recorded" show a date in 2106... > >> > >> MythWeb, which directly accesses the db, works just fine. myth:6544 has > >> the problems, as does mythfrontend, and likely mythbackend (no recording > >> made). > >> Status shows "no upcoming". > >> > >> All schedules show start/end of 00:00:00. No "Program Guide" data showing. > >> No "Upcoming" (natch), and more. > >> > >> This update was in stable for two days now but I do not see any mention, > >> maybe it is something else on my server? > >> > >> -- > >> Eyal at Home ([email protected]) > >> > >> -- > -- > Eyal at Home ([email protected]) > -- _______________________________________________ users mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected] Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
