Hi.

Issue is not hardware based -- indeed, code runs as a VM, and I've got
other VMs running F41.  It's not a technical issue; it's mostly a matter
of time & effort.  Yes, F29 is old.  I know that.  But upgrading is not an
easy or fast operation.

Code runs a bunch of services, and I'd have to migrate each and every one
of them.  The last time I did this it took me a few weeks, and that was a
relatively minor update!  Also, back then, I had more time (see below).

Just as a case in point, the IETF, which has a cadre of professionals who
are PAID to manage their services, took over a year to migrate their
mailing lists from mailman2 to mailman3.  They had to back out of the
update multiple times.  They had to write special scripts to perform the
migration.  And I believe they STILL run a custom front-end UI.   I don't
know if ANY of that code/effort was donated back to the MM3 team.

I'm just one guy, with a full time $DayJob.  I manage the GnuCash server
in my spare time, which has grown smaller and smaller as my kids have aged
up into the range where they are doing sports nearly every weekend.  While
I have time to maintain the status quo, I don't have time for a major
project like a MM2 -> MM3 migration.

I tend to only upgrade the distro every couple years.  "If it aint
broke...."  So THAT is why code is still running such an old distro.  It
was built in 2017 with F25.  It took a week to build and test the system
before I migrated the data from the previous system.  Another few weeks to
stabilize the system.. I then upgraded to F29 in 2019.   After that, well,
Covid and Real Life hit.   I haven't looked back because "it works", and
then because MM2 was "removed" in F35.  This means I could only update up
to F34 -- but what's the point now?

I hope this explains the current status.

Thanks,

-derek

On Fri, February 14, 2025 9:11 am, Brad Morrison wrote:
> Hi David/Bo/Derek/GNUCash users,
>
> FWIW, the current version of Fedora is 41, so 29 is quite, uh, old...
> https://fedoramagazine.org/announcing-fedora-linux-41/ &
> https://distrowatch.com/table.php?distribution=fedora
>
> I do not know if the issue with upgrading Fedora to the current version
> is hardware related, but if it is, maybe those interested in upgrading
> to Fedora 41 in order to upgrade to the current version of Mailman
> (01-Oct-2024 Mailman 3.3.10 (Tom Sawyer) - https://www.list.org/) could
> chip in a donation to https://gnucash.org/donate.phtml
>
> ---
> Thanks,
>
> Brad - https://www.facebook.com/brad.morrison.12327/ &
> https://nextdoor.com/profile/01mP46jj8KCzj3sP4 &
> https://norcal.social/@BradMorrison
>
> On 2025-02-12 19:46, David Carlson wrote:
>
>> In defense of Derek, I just checked the Mailman website.  Mailman 2.1 is
>> still the default version.  Release 3, while it is considered reliable,
>> it
>> is treated as if it is beta software, at least in the sense that there
>> is
>> no clearly automated migration path due partly to different
>> infrastructure
>> configuration.  see <https://docs.mailman3.org/en/latest/migration.html>
>> He has life as we all do, and he may not have the time to plan, test and
>> execute a migration to release 3.whatever of mailman.
>>
>> On Wed, Feb 12, 2025 at 9:19 PM flywire <flywi...@gmail.com> wrote:
>>
>> https://lists.gnucash.org/search/?idxinfo=gnucash-user is useless and
>> should be replaced with
>> https://www.mail-archive.com/gnucash-user@gnucash.org/maillist.html
>> before
>> updating the wiki.
>>
>> Bo Buckley wrote
>> https://lists.gnucash.org/pipermail/gnucash-user/2025-February/115450.html
>> :
>>
>> In the docs: https://wiki.gnucash.org/wiki/GnuCash_Forum It claims:
>> * The *GnuCash project* does *not* use ancient *forum* software for its
>> *>* online user support. It uses mailing list technology.*
>
> It's absurd. Let's call it alternative facts: eMail is 50 years old
> and Mailman is 25 years old, even Mailman 2.1.19 is from 2018.
>
> I raised https://bugs.gnucash.org/show_bug.cgi?id=797702 about
> upgrading to Mailman 3 and received the following reply:
>
>> Derek Atkins 2020-04-25 18:32:15 EDT
>> Code runs Fedora 29.  Mailman 3 isn't available on F29.
>> When code gets upgraded, mailman will be upgraded.
>> As for turning off the reminder; you can turn it off yourself.
>> Thank you.
>
> Of course Mailman 3 had run on Fedora 29 for years. My recollection of
> Derek's signature at the time:
>
>> Derek Atkins                 617-623-3745
>> de...@ihtfp.com             www.ihtfp.com [1]
>> Computer and Internet Security Consultant
>
> In addition to not emailing passwords back to users in clear text I
> highlighted through the mailing list Mailman 3 has a forum-like
> interface with search facilities.
>
> I understand Derek manages the Mail server for the community and the
> configuration isn't public.
>
> Lastly, I acknowledge and thank Derek for the time and effort he
> freely gives to me as a member of the community in support of Gnucash.
>
> Regards
> _______________________________________________
> gnucash-user mailing list
> gnucash-user@gnucash.org
> To update your subscription preferences or to unsubscribe:
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> -----
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.
>
>
> Links:
> ------
> [1] http://www.ihtfp.com
> _______________________________________________
> gnucash-user mailing list
> gnucash-user@gnucash.org
> To update your subscription preferences or to unsubscribe:
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> -----
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.
>


-- 
       Derek Atkins                 617-623-3745
       de...@ihtfp.com             www.ihtfp.com
       Computer and Internet Security Consultant

_______________________________________________
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Reply via email to