Debian bug report logs - #977
Python documentation bug

Message received at debian-bugs:

From nigel.vnet.net!johnsonm Sat Jun 10 17:30:43 1995
Return-Path: <johnsonm@nigel.vnet.net>
Received: from pixar.com by mongo.pixar.com with smtp
	(Smail3.1.28.1 #15) id m0sKavK-0005z9C; Sat, 10 Jun 95 17:30 PDT
Received: from vnet.net (elvis.vnet.net) by pixar.com with SMTP id AA07197
  (5.67b/IDA-1.5 for debian-bugs-pipe@mongo.pixar.com); Sat, 10 Jun 1995 17:29:11 -0700
Received: from nigel.vnet.net by vnet.net with SMTP id AA01353
  (5.67b/IDA-1.5 for <debian-bugs@pixar.com>); Sat, 10 Jun 1995 19:30:17 -0500
Received: from nigel.vnet.net (localhost [127.0.0.1]) by nigel.vnet.net (8.6.11/8.6.9) with ESMTP id UAA12562 for <debian-bugs@pixar.com>; Sat, 10 Jun 1995 20:27:14 -0500
Message-Id: <199506110127.UAA12562@nigel.vnet.net>
To: debian-bugs@pixar.com
Reply-To: johnsonm@nigel.vnet.net
Subject: Python documentation bug
Date: Sat, 10 Jun 1995 20:27:13 -0500
From: "Michael K. Johnson" <johnsonm@nigel.vnet.net>


Package: python
Version: 1.2-0

(Debian release .93R5)

/usr/doc/python/fix_hack.gz isn't executable.  If the consensus
is that fix_hack.gz shouldn't be executable, then it should not
be compressed and should be made exectuable.  Making the
documentation fails until this is made executable.  Actually,
this could also be fixed by changing /usr/doc/python/Makefile
to call "sh ./fix_hack" instead of just "./fix_hack".

It might make sense to include pre-built postscript
documentation, which would make the point not as important. If
not, then it could depend on or at least recommend TeX, LaTeX,
makeindex, etc., or on latex2html (which I assume isn't yet a
package; I don't recall seeing it, and my net connection just
went down for some reason so I can't check now...) so that the
documentation can be built one way or the other.

michaelkjohnson