faulty releases and pypi access

We have another case of faulty released eggs.

I reviewed the first that popped up for me, which was
zope.app.publication:

  - someone uploaded a stable 3.4.1 egg, but this is just a snapshot
    from the trunk, there is no tag for this release.

  - the egg does not contain data files correctly. unpacking the egg
    misses the zcml files.

  - the 3.4.0 egg is invalid as well as the zcml files are missing too

I did:

  - create a tag for the brown-bagged 3.4.1 release
  - removed the uploaded files from the cheeseshop as I don't have newer
    replacements immediately available.

The whole list of things that might be relevant here is:

- zope.securitypolicy
- zope.session, zope.app.session
- zope.app.authentication
- zope.app.i18n
- zope.i18nmessageid
- zope.app.applicationcontrol
- zope.app.appsetup

I'll go through those now and try to fix it up.

This is IMHO a good example why we shouldn't go for 'everyone can make a
release'.

Christian

-- 
gocept gmbh & co. kg - forsterstrasse 29 - 06112 halle/saale - germany
www.gocept.com - [email protected] - phone +49 345 122 9889 7 -
fax +49 345 122 9889 1 - zope and plone consulting and development

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQBG+hVndUt9X/gknwIRAla9AJ4i3giAnzu3QGPI1ytwnEIlNw1ukgCaA84A
b2ETxKiNPi1XaXHsVXYA4Zk=
=C8Te
-----END PGP SIGNATURE-----