Barry, > It took me a while to determine what to do, > but after I had built and tested the package, I had no problems > building packages for subsequent Mailman releases. IIRC, the last > Mailman for which I built a package was 2.1.14. I do not know if > any changes since then would require changes to the package-build > process. I have details on what I did, if anyone is interested. >
Our Ubuntu server will need to take an upgrade from 2.1.14 to 2.1.18-1, so your instructions on building Debian packages will be very helpful to us at least. Thanks in advance. Terry Earley 801 810-4175 Donate to FitEyes <http://www.fiteyes.com/community/donate-to-fiteyes> On Thu, May 15, 2014 at 10:32 AM, Barry S. Finkel <bsfin...@att.net> wrote: > On 5/14/2014 2:40 PM, Sascha Rissel wrote: > >> Hello there, >> >> I am running a vServer on Debian6. >> Via "apt-get install mailman" I installed and set up Mailman 2.1.13, which >> is running fine with 5 mailing lists on my server. >> >> Motivated by all those discussions about Yahoo's DMARC on this list, I >> wondered whether I can upgrade my Mailman installation to a newer version. >> >> I tried "apt-get update" and "apt-get upgrade" but I did not receive a >> newer version of Mailman. >> >> Unfortunately I don't consider myself as good enough in Linux usage, to be >> able to build Mailman binaries from scratch on my own. Indeed I tried, but >> already upon executing "configure" (Step 3 in Mailman's installation >> guide<http://list.org/mailman-install/node7.html>) >> I got a python warning >> >>> Distutils is not available or is incomplete >>> >> which seems to tell me I should install another Python environment. >> >> So I came to the point when I decided that compiling Mailman on my own is >> too complicated for me, because in the end I definitely want a bug-free >> installation of Mailman. >> >> Is there maybe an easier way to get a more recent version of Mailman for >> my >> server? >> >> In advance, thanks for your help! >> Sascha. >> > > When I was running a Mailman server on an Ubuntu box, I was forced to > install via a package. But I did some research on the Debian/Ubuntu > package to see what was in it. There were many patches that were > undocumented, and there was one patch that deleted a library that, > in some cases, is required. So, I decided to build my own package > from the SourceForge source. That way, I would know EXACTLY what > the source was, and I could get support from this discussion list. > > It took me a while to determine what to do, > but after I had built and tested the package, I had no problems > building packages for subsequent Mailman releases. IIRC, the last > Mailman for which I built a package was 2.1.14. I do not know if > any changes since then would require changes to the package-build > process. I have details on what I did, if anyone is interested. > > --Barry Finkel > > > ------------------------------------------------------ > Mailman-Users mailing list Mailman-Users@python.org > https://mail.python.org/mailman/listinfo/mailman-users > Mailman FAQ: http://wiki.list.org/x/AgA3 > Security Policy: http://wiki.list.org/x/QIA9 > Searchable Archives: http://www.mail-archive.com/ > mailman-users%40python.org/ > Unsubscribe: https://mail.python.org/mailman/options/mailman-users/ > terry%40fiteyes.com > ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
