Re: PloneSoftwareCenter, pypi, re-releasing a product

Maurits van Rees, on 2009-10-23:
> For a bug fix release 1.2.1 you should create a completely new
> release.  I have not done that up till now with Poi.  Mea culpa.  I'll
> create a 1.2.7 release today to make up for that omission. :-)

Done. :-)


I used zest.releaser to do a fullrelease on pypi and plone.org.  For
reference, this is my ~/.pypirc:

===========================
[distutils]
index-servers =
  pypi
  plone

[pypi]
#pypi.python.org
username:maurits
password:secret

[plone]
repository:http://plone.org/products
username:maurits
password:secret
===========================

In the Poi 1.2.x series I am uploading old-style tarballs to plone.org
with just the Poi directory, so not with Products.Poi/Products/Poi.
So I removed the uploaded egg and manually created and uploaded such
an old-style tarball.  So I did not use the complete pypi integration,
but the registering of the new long description went fine.

I'll add some random notes, which someone might find helpful or might
inspire someone to do some fixes.

I got a UnicodeDecodeError uploading to the official pypi with
'python2.4 setup.py sdist upload' (and the proper [server-login]
section in my .pypirc), probably caused by an umlaut that I recently
added in the HISTORY.txt.  With 'python2.4 setup.py sdist mupload'
(using collective.dist) this went fine.

For testing I used my local PloneSoftwareCenter instance.  A
'python2.4 setup.py mregister' failed with Unauthorized.  
'python2.4 setup.py mregister sdist upload' however succeeded.
Nothing appeared in the error logs, even though I removed Unauthorized
from the ignored exceptions, was running the Plone instance in the
foreground and had this in zope.conf:
debug-mode on
security-policy-implementation python
verbose-security on

You can still manually create a release, say 2.0, in PSC for planning
purposes without adding any downloads.  When you do a release 2.0 from
the command line PSC will happily add your file in that existing
release.  Any alpha, beta or rc releases you register and upload from
the command line are not added to that 2.0 release, as PSC does not
realize they belong together.

>> Hm, then what is the difference between Poi and kupu here?  With Poi I
>> have set the distutils id in the edit form of the project.  I guess
>> kupu has not done that.
>
> The distutils id setting has nothing to do with it.

Since I added Products.Poi as distutils id in
http://plone.org/products/poi PSC correctly associated the setup.py
mregister/mupload of Products.Poi with the existing poi project.

Cheers,

-- 
Maurits van Rees | http://maurits.vanrees.org/
            Work | http://zestsoftware.nl/
"This is your day, don't let them take it away." [Barlow Girl]


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Plone-website mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/plone-website
The Wiki: http://plone.org/development/current/projects/WebsiteTeam