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

2009-01-19 Thread Barry Warsaw

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

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


* Barry Warsaw ba...@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-
___
Mailman-Developers mailing list
Mailman-Developers@python.org
http://mail.python.org/mailman/listinfo/mailman-developers
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: 
http://www.mail-archive.com/mailman-developers%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9


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

2009-01-19 Thread Patrick Ben Koetter
* Barry Warsaw ba...@list.org:
 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.

It worked, more or less:

  Ran 29 tests with 0 failures and 4 errors in 0.407 seconds.
Tearing down left over layers:
  Tear down zope.testing.testrunner.layer.UnitTests in 0.000 seconds.

Test-modules with import problems:
  eggs.lazr.config-1.1-py2.6.egg.lazr.config.tests
  eggs.lazr.delegates-1.0-py2.6.egg.lazr.delegates.tests
  eggs.zc.buildout-1.1.1-py2.6.egg.zc.buildout.tests
  eggs.zc.buildout-1.1.1-py2.6.egg.zc.buildout.testselectingpython
  eggs.zc.recipe.egg-1.1.0-py2.6.egg.zc.recipe.egg.tests
  eggs.zc.recipe.testrunner-1.1.0-py2.6.egg.zc.recipe.testrunner.tests
  
eggs.zope.interface-3.5.0-py2.6-linux-x86_64.egg.zope.interface.common.tests.test_idatetime
  
eggs.zope.interface-3.5.0-py2.6-linux-x86_64.egg.zope.interface.common.tests.test_import_interfaces
  
eggs.zope.interface-3.5.0-py2.6-linux-x86_64.egg.zope.interface.tests.test_adapter
  
eggs.zope.interface-3.5.0-py2.6-linux-x86_64.egg.zope.interface.tests.test_advice
  
eggs.zope.interface-3.5.0-py2.6-linux-x86_64.egg.zope.interface.tests.test_declarations
  
eggs.zope.interface-3.5.0-py2.6-linux-x86_64.egg.zope.interface.tests.test_document
  
eggs.zope.interface-3.5.0-py2.6-linux-x86_64.egg.zope.interface.tests.test_element
  
eggs.zope.interface-3.5.0-py2.6-linux-x86_64.egg.zope.interface.tests.test_interface
  
eggs.zope.interface-3.5.0-py2.6-linux-x86_64.egg.zope.interface.tests.test_odd_declarations
  
eggs.zope.interface-3.5.0-py2.6-linux-x86_64.egg.zope.interface.tests.test_sorting
  
eggs.zope.interface-3.5.0-py2.6-linux-x86_64.egg.zope.interface.tests.test_verify
  eggs.zope.testing-3.7.1-py2.6.egg.zope.testing.tests
  eggs.zope.testing-3.7.1-py2.6.egg.zope.testing.testrunner.tests
Total: 94 tests, 0 failures, 4 errors in 11.174 seconds.


Proceed to create mailman.cfg or wait for workaround?

p...@rick

-- 
state of mind
Agentur für Kommunikation, Design und Softwareentwicklung

Patrick KoetterTel: 089 45227227
Echinger Strasse 3 Fax: 089 45227226
85386 Eching   Web: http://www.state-of-mind.de

Amtsgericht MünchenPartnerschaftsregister PR 563
___
Mailman-Developers mailing list
Mailman-Developers@python.org
http://mail.python.org/mailman/listinfo/mailman-developers
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: 
http://www.mail-archive.com/mailman-developers%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9


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

2009-01-19 Thread Barry Warsaw

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Jan 19, 2009, at 3:08 PM, Patrick Ben Koetter wrote:


* Barry Warsaw ba...@list.org:
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.


It worked, more or less:

 Ran 29 tests with 0 failures and 4 errors in 0.407 seconds.
Tearing down left over layers:
 Tear down zope.testing.testrunner.layer.UnitTests in 0.000 seconds.

Test-modules with import problems:
 eggs.lazr.config-1.1-py2.6.egg.lazr.config.tests
 eggs.lazr.delegates-1.0-py2.6.egg.lazr.delegates.tests
 eggs.zc.buildout-1.1.1-py2.6.egg.zc.buildout.tests
 eggs.zc.buildout-1.1.1-py2.6.egg.zc.buildout.testselectingpython
 eggs.zc.recipe.egg-1.1.0-py2.6.egg.zc.recipe.egg.tests
 eggs.zc.recipe.testrunner-1.1.0-py2.6.egg.zc.recipe.testrunner.tests
 eggs.zope.interface-3.5.0-py2.6-linux- 
x86_64.egg.zope.interface.common.tests.test_idatetime
 eggs.zope.interface-3.5.0-py2.6-linux- 
x86_64.egg.zope.interface.common.tests.test_import_interfaces
 eggs.zope.interface-3.5.0-py2.6-linux- 
x86_64.egg.zope.interface.tests.test_adapter
 eggs.zope.interface-3.5.0-py2.6-linux- 
x86_64.egg.zope.interface.tests.test_advice
 eggs.zope.interface-3.5.0-py2.6-linux- 
x86_64.egg.zope.interface.tests.test_declarations
 eggs.zope.interface-3.5.0-py2.6-linux- 
x86_64.egg.zope.interface.tests.test_document
 eggs.zope.interface-3.5.0-py2.6-linux- 
x86_64.egg.zope.interface.tests.test_element
 eggs.zope.interface-3.5.0-py2.6-linux- 
x86_64.egg.zope.interface.tests.test_interface
 eggs.zope.interface-3.5.0-py2.6-linux- 
x86_64.egg.zope.interface.tests.test_odd_declarations
 eggs.zope.interface-3.5.0-py2.6-linux- 
x86_64.egg.zope.interface.tests.test_sorting
 eggs.zope.interface-3.5.0-py2.6-linux- 
x86_64.egg.zope.interface.tests.test_verify

 eggs.zope.testing-3.7.1-py2.6.egg.zope.testing.tests
 eggs.zope.testing-3.7.1-py2.6.egg.zope.testing.testrunner.tests
Total: 94 tests, 0 failures, 4 errors in 11.174 seconds.


Proceed to create mailman.cfg or wait for workaround?


That's the failure I get too.  It looks to me like zope.testing is  
putting some bogus eggs on sys.path.  I need to contact the distutils  
sig to find out what the problem is.


In the meantime, remove the buildout artifact directories (basically  
anything that 'bzr ignored' spits out), then add the following in your  
~/.buildout/default.cfg file (creating the directory if necessary):


[buildout]
eggs=directory=/home/you/.buildout/eggs
download-cache=/home/you/.buildout/download-cache

Then rebuild.  This basically just moves the eggs out of a location  
that seems to confuse testrunner.


- -Barry

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

iQCVAwUBSXTmOHEjvBPtnXfVAQIQNAP/YSthTDsS8GisTwoq4xo1D5T0K+Gqxtxh
EjXuqcFDCEVYDzz65xPPq7BrjeEvUlQw8cy+PO6ECswd18+cY5IxN6Rh2B0o59ei
dY78bkVpMpluGvUctLLvlT8SezH7sLdHWCSbdJDbE5i3N9wBTzUpt5qc7a6JkM6V
luokXRTZX0A=
=jxsk
-END PGP SIGNATURE-
___
Mailman-Developers mailing list
Mailman-Developers@python.org
http://mail.python.org/mailman/listinfo/mailman-developers
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: 
http://www.mail-archive.com/mailman-developers%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9


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

2009-01-18 Thread Patrick Ben Koetter
* Barry Warsaw ba...@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.

p...@rick

-- 
state of mind
Agentur für Kommunikation, Design und Softwareentwicklung

Patrick KoetterTel: 089 45227227
Echinger Strasse 3 Fax: 089 45227226
85386 Eching   Web: http://www.state-of-mind.de

Amtsgericht MünchenPartnerschaftsregister PR 563
___
Mailman-Developers mailing list
Mailman-Developers@python.org
http://mail.python.org/mailman/listinfo/mailman-developers
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: 
http://www.mail-archive.com/mailman-developers%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9


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

2009-01-18 Thread Mark Sapiro
Patrick Ben Koetter wrote:

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.


It seems to be a real error. I don't see that branch on launchpad, and
I can't get it either.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

___
Mailman-Developers mailing list
Mailman-Developers@python.org
http://mail.python.org/mailman/listinfo/mailman-developers
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: 
http://www.mail-archive.com/mailman-developers%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9