[ZODB-Dev] Doc/zodb.pdf appears to be damaged in ZODB3-3.2.4 andZODB3-3.2.5

[Tim Peters]

[fdrake: does this ring any bells for you?]

[Rodrigo Dias Arruda Senra]
> This is no big deal,

I'll be the judge of that <wink>.

> but browsing through ZODB3-3.2.4 and ZODB3-3.2.5 I noticed that:
>
> $ xpdf zodb.pdf
> Error (0): PDF file is damaged - attempting to reconstruct xref table...
? Error: Couldn't find trailer dictionary
> Error: Couldn't read xref table
>
> $ xpdf -v
> xpdf version 3.00
> Copyright 1996-2004 Glyph & Cog, LLC
>
> There is no real harm, since (I presume) the same information is
> available as html inside /zodb subdir. Moreover, this behaviour is fixed
> in ZODB3-3.2 and ZODB3-3.3 releases. So I can totally live with it.
>
> I do not believe this is a xpdf 3.00 issue because Acrobat reader 5.0
> (win32 version) complains as well.

This is baffling to me so far.  The generated zodb.pdf (it's generated from
LaTeX source by Python's standard doc tools) is checked in to CVS, and I
always try bringing it up in Acrobat Reader before doing the checkin.  And,
indeed, the zodb.pdf on my box is fine.  But I just grabbed ZODB3-3.2.5.tgz
from zope.org, and the zodb.pdf in _that_ is only 352 bytes -- it is indeed
insane.

I don't know how that can happen, meaning that there are many steps that go
into building a release tarball, and anything from a Cygwin bug to a network
error could have caused this.  If it happened more than once, though,
presumption has to favor a systematic cause on my machine.

I've opened a Collector issue, here:

    http://dev.zope.org/Collectors/Zope/1676

Ah!  Ah!  CVS thinks it's a text file, and that's disastrous because the
checkin happens from a Windows box.  As soon as Fred reminds me how to
change a CVS file to binary after-the-fact, I'll repair it.  AFAICT, the CVS
info for this file has been wrong forever, but it didn't matter when Jeremy
was building tarballs (on Linux).

> best regards to the zodb dev team for the *outstanding* work, Senra

And thank you for the outstanding bug report <smile>.