Another idea ...
what UMASK do you have set? Possible your directories are missing +w
attributes ....
v60x-so4[5:25pm][<secret>]>umask
2
is fine ...
Cheers,
Ivo
Ivo Hinkelmann wrote:
Hi ,
thanks for your exact and in detail information of this problem. The
logic in localize to handle write protected localize.sdf file is the
following:
-Merge the strings into a temp file
-Rename the write protected localize.sdf file to localize.sdf_backup
-Copy the temp file to localize.sdf
-Remove the localize.sdf_backup
-Remove the temp file
If any error occuried while copy/move/rename etc a error messgage will
be thrown. Now I am wondering while this does not work for the
-r--r--r-- files ...
I could build in a chmod 644 into the localize.pl
Cheers,
Ivo
dooteo wrote:
Hi Pavel,
please do not start new threads by replying to old mails. If you do
so, please do it correctly and do not set In-Reply-To and similar
headers.
Sorry, I didn't see any previous thread talking about this :(
On 31.5.2008, at 16:45, dooteo wrote:
Even a GSI file has all UI messages trsnalated, when I'm running:
localize -m -l eu -f GSI_eu.dfs
it not merge back messages into next file:
ooo_DEV300_m14_src/svtools/source/contnr/localize.sdf
Interesting. It does here in to-be-DEV300_m15. Does localize print
something for you? Does it merge into localize.sdf in other
directories in svtools?
The file is read-only in the CVS checkout - can you retest after
chmod 644 it before?
I found next files with not correct permissions (755 or 444) in CVS:
-rwxr-xr-x 1 dooteo dooteo 91628 api 17
21:47 ./desktop/source/deployment/unopkg/localize.sdf
-rwxr-xr-x 1 dooteo dooteo 977030 api 17
22:07 ./javainstaller2/src/Localization/localize.sdf
-rwxr-xr-x 1 dooteo dooteo 40229 api 17
22:16 ./scp2/source/winexplorerext/localize.sdf
-r--r--r-- 1 dooteo dooteo 330174 api 14
10:56 ./sfx2/source/explorer/localize.sdf
-r--r--r-- 1 dooteo dooteo 519696 api 17
22:20 ./svtools/source/contnr/localize.sdf
-r--r--r-- 1 dooteo dooteo 22568 api 14 10:59
./svtools/source/filepicker/localize.sdf
-r--r--r-- 1 dooteo dooteo 5141400 api 17 22:20
./svtools/source/misc/localize.sdf
-rwxr-xr-x 1 dooteo dooteo 408045 api 17 22:21
./svx/source/unodialogs/textconversiondlgs/localize.sdf
Not merged back files:
sfx2/source/explorer/localize.sdf
svtools/source/contnr/localize.sdf
svtools/source/filepicker/localize.sdf
svtools/source/misc/localize.sdf
Localize tool shows only a message saying that couln'd write in
svtools/source/contnr/localize.sdf file. But it looks that 'localize'
generates a new 'localize.sdf' file (and removes the original one),
because when I look for file permissions (after 'localize' tools is
runned) they are with 644.
Once original 'localize.sdf' files are chmod as 644, translated
messages are merged back succesfuly.
So I'm going to modify you're script (in local, of course :) to change
their premissions:
--- build 2008-05-30 20:52:25.000000000 +0200
+++ build_2 2008-06-02 12:31:12.000000000 +0200
@@ -393,6 +393,13 @@
cd ooo_${VERSION}_src
+# Change all 'localize.sdf' files permissions to 644 +
+for i in `find ./ -name 'localize.sdf' `; do + ls -l $i; +
chmod 644 $i; +done
+
# Prepare Windows-only requirements
[ ${OOO_BUILD_SYSTEM} = "Windows" ] && PrepareWindowsRequirements
I'm going to try to build again this night.
Thanks and best regards,
Dooteo
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
