[Mailman-Users] Re: Where's the installation directions / source, etc, please?
Barry S. Finkel writes: > And I wanted to get support from Mark and this list, instead of > from Debian. So, I figured out how to create a package from the > Mailman source. This was on an older version of Mailman, but I > assume that my technique should work with the latest Mailman 2 > source. Contact me personally for details. It is not complicated. I second this method if you're not interested in keeping the source tree around. It keeps your system tidy, and I'm pretty sure most distros (specifically Debian does) support a configuration to look in a local package archive for packages before going out to the main distro repos. So do it each time you upgrade and you always have a way to back out to the previous working system. Steve -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/ Member address: arch...@jab.org
[Mailman-Users] Re: Where's the installation directions / source, etc, please?
On 7/19/2023 1:46 AM, Stephen J. Turnbull wrote: Steven Jones writes: > I feel the same way, hence still running Mailman2 (on RHEL8). It is > simple and low CPU hit, however Red Hat stops it support in May > 2024. That's fine with us. Mailman 2 is pretty bulletproof and low- maintenance from our point of view too. > Containers are really useful where done well but I tried 2 or > times to get mailman3 going on RHEL9 with podman and even docker > and failed. Not sure what containers have to do with anything, to be honest. In any case, we don't really support containers AIUI. Abhilash provides multiple containers in a configuration that's convenient for him to distribute, but the container environment isn't something we support, nor can we. A lot of people have difficulty configuring the network with multiple containers. I would recommend configuring everything (except perhaps the database) in a single "host" (hardware, VM, or container), unless you're willing to take on all that complexity. > I think Debian12 does mailman3? worth a go if so. In my case I am > not allowed to run an unsupported OS and app. Current Debian is pretty close to most recent release (maybe at this point it is the most recent release). But as you say, if you need a supported OS, you're probably going to end up with a pretty old version of Mailman. Steve As for the last paragraph - When I was a Mailman administrator some years ago on an Ubuntu system, I was told that I had to install Mailman from a package. I looked at the Debian package, and I saw patches that were undocumented, so I had no idea what they did. And Debian, in one patch, deleted a library that is needed in some situations. And I wanted to get support from Mark and this list, instead of from Debian. So, I figured out how to create a package from the Mailman source. This was on an older version of Mailman, but I assume that my technique should work with the latest Mailman 2 source. Contact me personally for details. It is not complicated. --Barry Finkel -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/ Member address: arch...@jab.org
[Mailman-Users] Re: Python 2.7.15, etc, vs Python3...
rich...@karmannghia.org writes: > (Maybe! How do we know they won't abandon Python3 like they did > Python2? They supported Python 2 for most of a decade after the release of Python 3. Not only does that bode well for longterm Python 3 support, there also will not be another break like Python 3 vs. Python 2. Nobody has the stamina to accept that much abuse again. There once was talk of going from Python 3.9 to Python 4.0, but that would have been just Python 3.10 by another name, just as backward compatible. > I mean, whatever happened to Python1?! It gracefully evolved into Python 2. There were a couple of small compatibility breaks (introduction of true Boolean values was one, I think), which justified a few years with both Python 1 (with the Unicode type bolted on in v1.6) and Python 2 (with the compatibility breaks and a number of new syntaxes, and a more thorough integration of Unicode) being supported and distributed at the same time. > Why isn't it just "Python"?) To let people know that there are definitely backward incompatibilities. Steve -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/ Member address: arch...@jab.org
