Closed Bug 18698 Opened 25 years ago Closed 20 years ago

Fresh install of Bonsai from CVS has problems

Categories

(Webtools Graveyard :: Bonsai, defect, P2)

x86
Linux
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jmeskill, Assigned: tara)

Details

after doing a new install from CVS trying to rebuild cvs history from the
administration menu yeilds

Software error:
Couldn't open data/legaldirs: No such file or directory at globals.pl line 306.
Status: NEW → ASSIGNED
tara@tequilarista.org is the new owner of Bugzilla and Bonsai.  (For details,
see my posting in netscape.public.mozilla.webtools,
news://news.mozilla.org/38F5D90D.F40E8C1A%40geocast.com .)
Assignee: terry → tara
Status: ASSIGNED → NEW
[Just installed bonsai on our site today.]
You have to run ./createlegaldirs.pl <treename> (in most cases, default) from
bonsai directory.
Matt's the default QA for this component, and he got left off somehow (probably 
the bug was reported before bonsai had a default QA).  Matt, should this be 
resolved/invalid?  or should this bug be redirected towards fixing the 
documentation on this item? :)  I also just installed bonsai, and the previous 
comment before mine is correct.
Dave, I'm mainly the Bonsai QA because I got handed QA for most of Webtools when
I volunteered for Bugzilla, because no one else was doing it.  I don't know too
much more about Bonsai than what I can see on bonsai.mozilla.org.

So, basically, the answer to your question in this case is "Who, me?".
QA Contact: matty
now, what ?
There's some known problems around this.  The workaround is pretty simple. 
Create a file called "legaldirs" in your data dir and make sure it's writable by
whatever is running bonsai--nobody/apache/or if you don't care about security,
777.

Corallary--if you see this when creating additional bonsai pages other than
"default", you need to create the legaldirs file in each page's subdirectory.
QA Contact: matty → timeless
Priority: P3 → P2
Running createlegaldirs.pl is listed as a step in INSTALL so I'm going to assume
that this was just a documentation bug.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Product: Webtools → Webtools Graveyard
You need to log in before you can comment on or make changes to this bug.