Greetings dev listers: I've been lurking on the dev mailing list and Element (@eashley:matrix.org) for a while now. I'm an experienced C/C++ and Java developer with years of porting experience for a 4GL RDBMS b-tree package. At peak we ported between DOS, Windows, VAX VMS and 29 *IX variants. I have a touch of experience with sqlalchemy for accessing the FairCom c-tree SQL Server and thought this could be a good starting point for me.
I'm attempting to set up a FAF build environment locally, but with python3-wtforms-sqlalchemy being retired, I'm in a chicken-and-egg situation. Has anyone updated the python3-wtforms-sqlalchemy to wtforms 3.1 and sqlalchemy 2.x, both of which were breaking changes? I found missing postgresql testing rpms on Koji for f43 but noone seems to have built the wtforms sqlalchemy code since fc40 when it retired. I'm too busy ATM to bring wtforms and sqlalchemy up to date sufficiently to build it. If no one has it available, I guess I'll spin up a VM with FC40, install FAF and start upgrading the OS, then start on the packages to get them current. I'll send a proper introduction message later. Thanks in advance, Eric -- Secured with Tuta Mail: https://tuta.com/free-email Mar 18, 2026, 06:50 by [email protected]: > On Tue, Mar 17, 2026 at 4:21 PM Kevin Fenzi <[email protected]> wrote: > >> >> > >> > Right, thanks. I think the problem is we need someone new to help out with >> > this, hence my mail. :-) >> > I think the old Abrt team no longer has the time or interest to continue >> > with it. >> > I can try to reach out to them, though I can guess what they might say >> > based on what I've heard. >> >> I'm not sure just enabling f43/f44 is worth doing. If the upstream >> development is not happening, there's lots of other things needing >> attention not being addressed, perhaps it's better to just retire it >> gracefully. >> >> Of course if there's interested parties to take over upstream >> development and work on those things thats another story. >> > > That would be a shame. I have found it quite useful in the past to > look at packages to look for common crashes - even with historical > data and graphs that show when they started happening, and with what > versions. > > Fabio > -- > _______________________________________________ > devel 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 > -- _______________________________________________ devel 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
