Issue 1071 - copy archive files from util/so_berkeleydb to external/berkeleydb
Summary: copy archive files from util/so_berkeleydb to external/berkeleydb
Status: CLOSED FIXED
Alias: None
Product: Infrastructure
Classification: Infrastructure
Component: _openoffice.org CVS (obsolete) (show other issues)
Version: current
Hardware: All All
: P1 (highest) Trivial (vote)
Target Milestone: ---
Assignee: Unknown
QA Contact: issues@www
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-06-20 17:05 UTC by Martin Hollmichel
Modified: 2003-12-06 14:52 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description Martin Hollmichel 2001-06-20 17:05:47 UTC
copy CVS archive files from util/so_berkeleydb to external/berkeleydb and add 
the alias berkeleydb external/berkeleydb to the CVSROOT/modules file.

util/so_berkeley can than deleted after publishing OpenOffice633.

external components will be move to the external project.
Comment 1 Unknown 2001-06-20 17:55:35 UTC
Accepting issue. The alias has been added to the modules file.
Comment 2 Unknown 2001-06-20 19:47:28 UTC
The directory issue is being tracked internally pcn4635
Comment 3 Unknown 2001-06-21 18:10:41 UTC
We are awaiting resource availability to copy the archive. I will keep you
updated and try to push this through as soon as possible.

Thank you
Kat 
Comment 4 Unknown 2001-06-22 04:43:28 UTC
The contents of util/so_berkeleydb has been copied to external/berkeleydb. I am
resolving the issue fixed for now. Please reopen it if there is a problem or
when you would like util/so_berkeley to be deleted.

Thank you
Kat
Comment 5 michael.bemmer 2003-03-24 08:30:22 UTC
As agreed by Louis I will close these resolved fixed kat (support)-owned issues
now. If you have trouble with that, please re-open the issue.
Comment 6 michael.bemmer 2003-03-24 08:32:09 UTC
As agreed by Louis I will close these resolved fixed kat (support)-owned issues
now. If you have trouble with that, please re-open the issue.