Issue 7924 - unable to upload to /developer as the directory is read only
Summary: unable to upload to /developer as the directory is read only
Status: CLOSED FIXED
Alias: None
Product: Infrastructure
Classification: Infrastructure
Component: Downloads (show other issues)
Version: current
Hardware: Sun SunOS
: P1 (highest) Trivial (vote)
Target Milestone: ---
Assignee: Unknown
QA Contact: issues@www
URL:
Keywords:
Depends on: 7802
Blocks:
  Show dependency tree
 
Reported: 2002-09-27 14:47 UTC by sander_traveling
Modified: 2003-12-06 14:52 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description sander_traveling 2002-09-27 14:47:06 UTC
this is a stopper for teh 643 release - the directory /developer/643 cannot be
created as /developer is read only. hence no files for teh release can be uploaded
Comment 1 sander_traveling 2002-09-27 15:14:29 UTC
reassigning to support@openoffice.org
Comment 2 Unknown 2002-09-27 15:41:40 UTC
accepting this issue.
Comment 3 Unknown 2002-09-27 16:59:48 UTC
I have opened an internal issue to deal with the /developer directory.

Stefan - Why is this assigned to issues@, when Sander's comments say
that it he assigned it to support@?  There is nothing in the issue
activity showing it was re-assigned.
Comment 4 Unknown 2002-09-27 17:38:09 UTC
updating whiteboard
Comment 5 Unknown 2002-09-27 18:43:27 UTC
Please check on the /developer directory now.
Comment 6 stx123 2002-09-30 10:22:29 UTC
> Why is this assigned to issues@, when Sander's comments say
> that it he assigned it to support@?
I don't know; because Sander tried to reassign, but didn't?
Comment 7 Unknown 2002-10-01 22:33:11 UTC
Closing
Comment 8 michael.bemmer 2003-03-24 08:21:13 UTC
As agreed by Louis I will close these resolved fixed support-owned issues now.
If you have trouble with that, please re-open the issue.
Comment 9 michael.bemmer 2003-03-24 08:25:34 UTC
As agreed by Louis I will close these resolved fixed support-owned issues now.
If you have trouble with that, please re-open the issue.