On 8/29/20 9:29 PM, Stephen J. Turnbull wrote: > Dennis Putnam writes: > > > Since Centos 7 is way behind on mailman rpm (2.1.15 is the only > > available rpm) and mailman is currently at 2.1.34 I need to do a manual > > update. While I know how to install software, I am concerned that just > > doing a manual install from the tarball will mess up current > > settings, > > Perhaps the most straightforward procedure is to backup mm_cfg.py and > the data in the archives, data, lists, logs, messages, and qfiles > folders under /var/lib/mailman. Then get the source rpm, unpack it, > delete the old source tree and replace it with the new source tree. > Review the patches and delete any that apply to executable Mailman > code, keep only those that make the Mailman installation conform to > Centos layout. Fixup the rpm control file (Mailman version, build, > and list of patches), and build an installable rpm and a srpm. Then > install the rpm. Finally, check that the files backed up above have > not been corrupted, and start Mailman.
Much more snipped. Steve has given lots of good info, but also see <https://wiki.list.org/x/8486953>, <https://mail.python.org/pipermail/mailman-developers/2004-October/017343.html> and the patch attached to the latter. The latter can also be found at <https://mail.python.org/archives/list/mailman-develop...@python.org/message/TNSLSSV7KSJGXHZE5RWVCOPHZR5SMAVG/> -- Mark Sapiro <m...@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ 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/
