Closed
Bug 310659
Opened 20 years ago
Closed 20 years ago
2.20.x documents are missing
Categories
(Bugzilla :: bugzilla.org, defect)
Bugzilla
bugzilla.org
Tracking
()
RESOLVED
FIXED
People
(Reporter: msampair, Assigned: justdave)
References
()
Details
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6
None of the bugzilla 2.20 documentation links are working.
Reproducible: Always
Comment 1•20 years ago
|
||
Confirming!
Assignee: documentation → justdave
Status: UNCONFIRMED → NEW
Component: Documentation → bugzilla.org
Ever confirmed: true
OS: MacOS X → All
Hardware: Macintosh → All
| Assignee | ||
Comment 2•20 years ago
|
||
*** Bug 310764 has been marked as a duplicate of this bug. ***
| Assignee | ||
Comment 3•20 years ago
|
||
The documentation is compiled into HTML and PDF and so forth on the website from
the XML sources by a cron job, and the cron job seems to be busted. I'm on it.
Status: NEW → ASSIGNED
| Assignee | ||
Comment 4•20 years ago
|
||
cron job output is spewing this:
jade:E: cannot open "/usr/share/doc/openjade-1.3.1/pubtext/xml.dcl" (No such
file or directory)
I'm betting we picked up a new version of Jade with a security update and since
the paths are all hardcoded...
| Assignee | ||
Comment 5•20 years ago
|
||
Yep, that was exactly what happened. Script was looking for 1.3.1 and we had
1.3.2 on the server.
libpng doesn't like bzLifecycle.png, so the PDFs are busted, but everything else
is there.
The version numbers seem to be messed up, but that's how it is in CVS, so
someone just has to fix those in CVS.
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Comment 6•20 years ago
|
||
You can fix the libpng thing by grabbing and building the latest libpng from
Fedora Core 4, version 1.2.8. That fixed it on landfill.
http://download.fedora.redhat.com/pub/fedora/linux/core/4/SRPMS/libpng-1.2.8-2.src.rpm
You need to log in
before you can comment on or make changes to this bug.
Description
•