[Mailman-Developers] ANNOUNCE: GNU Mailman 3.0a2 (Grand Designs)

[Barry Warsaw]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Jan 18, 2009, at 2:59 PM, Patrick Ben Koetter wrote:

> * Barry Warsaw <barry at list.org>:
>> For detailed information on 3.0a2, please read docs/ALPHA.txt.  This
>> file explains how to build Mailman and run the test suite.  The docs/
>> NEWS.txt file contains high level descriptions of what's changed  
>> since
>> 3.0a1.  Most notably are the new configuration system, the better  
>> test
>> suite and installation process, and the new LMTP support.  Mailman 3
>> also contains extensive doctests which explain how certain subsystems
>> work.
>
> I'm having problems to build MM3 and I am unexperienced enough with  
> Python
> (including bzr) to tell if its me or any program standing in the way.
>
> So far I have successfully built Python 2.6 on a vanilla Ubuntu/ 
> Hardy virtual
> machine.
>
> Then I followed docs/ALPHA.txt from mailman-3.0.0a2 and tried to  
> checkout
> megamerge. I get this and believe I shouldn't:
>
> # bzr branch lp:~barry/lazr.config/megamerge
> bzr: ERROR: Not a branch: "https://code.launchpad.net/".
>
> I can't tell if its a configuration error on my side or a real  
> error. Any
> help greatly appreciated.

The megamerge branch was merged into lazr.config proper and release as  
lazr.config 1.1. So you don't need this branch.  The bzr branch of  
mm3.0 is up-to-date now, but from the tarball, you should just skip  
this step and edit buildout.cfg so that the "develop" line only  
contains a single dot.

Note that bin/test may break for you.  If it does, I have a  
workaround, but I don't yet know if the problem is in buildout or  
mailman.

- -Barry

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)

iEYEARECAAYFAkl0j3UACgkQ2YZpQepbvXHMpQCgkUn18wfHD/CzyYFdHwGP5FPC
dFkAniwvzKfba/02c4xWtaF53Rz2+acA
=dlOn
-----END PGP SIGNATURE-----