Friday, October 6, 2006, 9:06:39 AM, you wrote:
> I'm suspecting that Adam, who built the 3.2.x releases, was executing
> the wrong command when building the tarball, because zope.conf.in on the
> 3.2.x branch doesn't contain the formatter line. It's zope.conf.in on
> the 3.3.x branch that does.
Yeah, now I'm even more puzzled. Indeed there is nowhere a formatter line
in any zope.conf.in, but in the
(after the build)
I'm still trying to figure out how it comes.
> http://dev.zope.org/Zope3/MakingARelease says you should be making a
> tarball with
> ../../zpkgtools/bin/zpkg -r Zope-3.3.0b1 -C Zope.cfg Zope
> but of course you need to replace Zope-3.3.0b1 with the current tag
> (which is 3.2.2). My suspicion is that Adam forgot to do that and so he
> built a tarball of 3.2.2, but with zopeskel from 3.3.x.
I'm sorry, but I did it. But the required command is not exactly the
says that I should run
python ..\zpkg\bin\zpkg -C releases\Zope.cfg -v 3.1.0c1 -t Zope-win
I'll investigate further as soon as I have time.
Adam mailto:[EMAIL PROTECTED]
Quote of the day:
According to my best recollection, I don't remember.
Zope3-dev mailing list