Re: [dev] building prolbem in "instsetoo_native" of OOE680_m6 with Cygwin

Canghua Qu wrote: > Hi, > I have a problem in building "instsetoo_native" (OOE680_m6) with cygwin on > Windows XP. > There is no error until building "basctl", and then errors come out > frequently, so I have to manually modify the files generated in > "\..\wntmsci11.pro\" ,then kept on build

Re: [dev] Re:Re:building prolbem in "instsetoo_native" of OOE680_m6 with Cygwin

Canghua Qu wrote: > [...] > What I have done are: > 1. change the line about # generate hid files in rules.mk (\solenv\inc\) > from: >+$(PERL) $(SOLARENV)$/bin$/mhids.pl $*.src $(SRS) $(PRJNAME) > $(CDEFS) $(INCLUDE) > To: > +$(WRAPCMD) $(PERL) $(SOLARENV)$/bin$

Re: [dev] RE:[dev] question about use XStorag

chensuchun wrote: [...] Sorry, there is no OwnSubFilter service in my openoffice, my openoffice is based on the source of OOB680 . [...] Why do you have to use such an old code base? I'd strongly recommend to update to f.e. OOF680 m18, the latest release. From my point of view it does

Re: [dev] Release Engineering IRC chat

Jörg Jahnke wrote: Hi, as Vladimir from the Hamburg Release Engineering team is currently in China, we are going to have a chat with him on the freenode IRC channel #dev.openoffice.org today at 10 am Hamburg time (GMT+1) / 4 pm Beijing time. Hopefully some of the colleagues from CH2000 will

Re: [dev] Release Engineering IRC chat

Jörg Jahnke wrote: Hi, as Vladimir from the Hamburg Release Engineering team is currently in China, we are going to have a chat with him on the freenode IRC channel #dev.openoffice.org today at 10 am Hamburg time (GMT+1) / 4 pm Beijing time. Hopefully some of the colleagues from CH2000 will

Re: [dev] Deprecated license SISSL in the source code again!

Frank Schönheit - Sun Microsystems Germany wrote: Hi Pavel, But we should not allow any new files with this license to be integrated! Do you suggest to enforce this by tooling? Yes. And not only by tools, but also by humans ;-) Oops ... how would this be look like. Will RE have guns under

Re: [dev] proposal for change of cws policies

Martin Hollmichel wrote: Eike Rathke wrote: [...] | A CWS must be built on at least two platforms in the "product" version | (Windows and one UNIX platform) How will we ensure that non-Hamburg based CWSs can be built on these platforms and install sets be made available? I'm not sure ab

Re: [dev] How to get a list of all CWS in a build?

Joe Smith wrote: I'm looking at cws "impress122" and I want to know if it has been integrated in the OOG680_mX builds. How can I do that? According to EIS, impress122 was integrated in m218 for 2.3: http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Path=SRC680%2Fimpress122 but that's a d

Re: [dev] Is someone still building OOo with tcsh?

Volker Quetschke wrote: [...] Hamburg uses [...] 4nt for Windows builds of OOo. The "community" uses bash[*] for all OOo builds and discourages the use of 4nt. This frequently leads to broken milestones for the community that seem to build fine and are OKed by RE and QA. That is a known pr

Re: [dev] Re: [Issue 82715] Use system gcc stl for all Linux ports except for "locked-in" ones

Stephan Bergmann wrote: : --- Additional comments from rene Thu Nov 8 09:21:22 + 2007 --- FWIW, Sun seems to plan to get rid of it (for 3.0), too: http://wiki.services.openoffice.org/wiki/OOo30_release_engineering_pla

[dev] Environment variables to be removed.

Hi, I'd like to remove some environment variables from config_office/set_soenv.in for SRC680 source tree: XPVERSION GVERDIR TF_PACKAGES TF_FILEURL TF_CFGDATA TF_SVDATA TF_SDBAPI TF_UCB STAR_RESOURCEPATH STAR_REGISTR

[dev] Environment variables to be removed.

Hi, I'd like to remove some environment variables from config_office/set_soenv.in for SRC680 source tree: XPVERSION GVERDIR TF_PACKAGES TF_FILEURL TF_CFGDATA TF_SVDATA TF_SDBAPI TF_UCB STAR_RESOURCEPATH STAR_REGISTRY

Re: [dev] Environment variables to be removed.

esMgr ? Kind regards, pl Rüdiger Timm wrote: Hi, I'd like to remove some environment variables from config_office/set_soenv.in for SRC680 source tree: XPVERSION GVERDIR TF_PACKAGES TF_FILEURL TF_CFGDATA TF_SVDATA TF_SDBAPI TF_UCB STAR_RESOURCEPATH STA

Re: [dev] Environment variables to be removed.

is is not necessary for thebuild environment anymore (which AFAIK was the original customer), is anyone else using it ? Or could I remove it form ResMgr ? Kind regards, pl Rüdiger Timm wrote: Hi, I'd like to remove some environment variables from config_office/set_soenv.in for SRC680 s

Re: [dev] A few questions on how to add a new code module on CVS (new module: icc)

Hi Giuseppe, Giuseppe Castagno wrote: Hi all, I have a question about the right procedure to follow to add a new module (sorry for the lengthy message). The module I'm adding is a follow up to issue 81093 [1]. I read the notes on the wiki [2] to have an idea on how to proceed. So far I've cr

[dev] Renaming current development code line 'SRC680' -> 'DEV300'

Development towards OpenOffice.org 3.0 currently takes place on code line SRC680. It is planned to rename that as DEV300 in the next but one week (calendar week 09). Rüdiger - To unsubscribe, e-mail: [EMAIL PROTECTED] For addi

[dev] Switch from SRC680 to DEV300: do not resync to SRC680 any more

This week's milestone m248 is the last milestone of master workspace SRC680. From now on development towards OpenOffice.org takes place on DEV300. In particular this means you must not resync any childworkspace to SRC680 any more. If you have a 3.0 targeted childworkspace and need to resync i

[dev] Re: Switch from SRC680 to DEV300: do not resync to SRC680 any more

Rüdiger Timm wrote: This week's milestone m248 is the last milestone of master workspace SRC680. From now on development towards OpenOffice.org takes place on DEV300. In particular this means you must not resync any childworkspace to SRC680 any more. If you have a 3.0 tar

Re: [dev] EIS Incompatible Modules

Stephan Bergmann wrote: To those who evaluate a CWS's "Incompatible Modules" data in EIS (i.e., Sun Hamburg Release Engineering): If I mark module A as incompatible, will you build A itself with local output trees removed, or only those modules that depend on A? Module A itself and all t

Re: [dev] New License and Contributor Agreement

The header I used on CWS changefilehader are as attached. Rüdiger Stephan Bergmann wrote: Stefan Taxhet wrote: To reflect the license change to LGPLv3 a new header for the source files will be introduced. Header templates[2] are linked from our guidelines for participation[3] and should be u

Re: [dev] difficult access debugging symbols

Terrence Enger schrieb: Greetings, I have built OOH680_m10 on ubuntu-Gutsy (7.10). Somewhere between creation of libraries in the solver and installing from the rpm's, I lose debugging symbols. I think libraries get stripped during deliver. That means, in your module output trees (e.g. sw/un

[dev] DEV300 m7: license header change and removal of external include guards

Milestone DEV300 m7 contains childworkspace changefileheader. That CWS combines two tasks: updating all file headers to LGPL 3 and removal of external include guards from c++ files. License Header Update = All file headers of our current code base have been updated. If you a

Re: [dev] deliver's verbosity

Frank Schönheit - Sun Microsystems Germany wrote: Hi, just noticed that in m18, deliver isn't as gossipy as before: doing a "deliver" in a module just prints deliver -- version 1.127 Module 'module' delivered successfully. x files copied, y files unchanged. Yes, that was me on CWS sh

Re: [dev] sandbox not exist

Hi! Two questions: - where di you get your sources from? OOo 2.4.0 ist not DEV300 m14 - how do you configure and how start your build? You apparently either are missing some module or the build order is incorrect. 'sandbox.jar' comes from OOo module called 'sandbox' which has to be built before s

Re: [dev] Troubles building DEv300_m20: dictmgr.hxx is missing

Giuseppe Castagno schrieb: Hi all, while building DEV300_m20 tag I came across this: ... lingucomponent/source/lingutil/lingutil.cxx:62:23: error: dictmgr.hxx: No such file or directory lingucomponent/source/lingutil/lingutil.cxx: In function '_STL::vector Get module 'hunspell'. Ruediger ---

Re: [dev] Trouble compiling DEV300_m19

For me this looks like http://www.openoffice.org/issues/show_bug.cgi?id=89973 If it is that issue it will still appear in m21, as the fix has not reached master workspace yet. :-( Try aplying the patch attached to that issue. Rüdiger Regina Henschel wrote: Hello, I try to compile DEV300_m

Re: [dev] cws sync m38 problems.

I now remember again ... The same may hold true for sw/uiconfig Rüdiger Jens-Heiner Rechtien wrote: Hi, the best way to resolve this problem (if you haven't change anything in that area): cd svx/uiconfig/ rm -rf layout svn update (which checks ouut the stuff again). This works because there

Re: [dev] cws sync m38 problems.

Kohei Yoshida wrote: On Tue, 2008-12-23 at 15:14 +, Caolán McNamara wrote: i.e. "Transmitting file data ...svn: Commit failed (details follow): svn: While preparing 'WORKSPACE/officecfg/registry/schema/org/openoffice/Office/makefile.mk' for commit svn: File '/cws/WORKSPACE/svx

Re: [dev] developing on Windows

Just out of curiosity: do you target libraries only or will that also handle resources (*.res files), configuration files, and other stuff? Would that mean deliver.pl has to read scp2 par files or setup_osl.inf to determine the correct destination? Rüdiger Robert Black wrote: Thanks for con

Re: [dev] moving psprint into vcl

Philipp Lohmann wrote: Hi all, for various reasons we (hdu and me in this case) would like to move the code now residing in psprint into vcl. reasons to do so: - font subsetting code is in psprint and on many platforms linked statically into vcl anyway. - future CUPS versions will migrate f

Re: [dev] moving psprint into vcl

Philipp Lohmann wrote: Rüdiger Timm wrote: I'm all in favour of this change. My only question would be about the time line. We are going to split off a separate OOo 3.1 code line soon. Only 3.1 tasks will be accepted there. Having psprint code inside vcl on TRUNK and in a separate modu

Re: [dev] to-be-DEV300_m40: cygwin mess

Pavel Janík wrote: On 24.1.2009, at 0:27, Pavel Janík wrote: - oowintool is in ./ and not in ./solenv/bin (configure) #i98423# Fixed by Rene. - guw directory is completely messed up: #i98424# Fixed by Rene. - to-be-DEV300_m40: setup_native merge error #i98425# Fixed, too.

[dev] New Release Branch OOO310

There is a new release branch (aka master workspace), named 'OOO310'. It has been created based on DEV300 m40. From now on bug fixing for our next release OOo 3.1 (*) will take place on OOO310, while DEV300 is heading towards OOo 3.2 and later releases. Rüdiger (*) http://wiki.services.openof

Re: [dev] Re: [cws-announce] SRC680_m126 ready for use.

Pavel Janík wrote: From: NAKATA Maho <[EMAIL PROTECTED]> Date: Sun, 28 Aug 2005 08:37:19 +0900 (JST) > have you already raised #IZ#? and do you think RE can do master fix? No. Surely early tomorrow. Sorry, we somehow missed this 'configure.in'. I just have regenerated and commited

Re: [dev] Documenting environment variables

Éric Bischoff wrote: Hi all, Quick link: http://www.go-oo.org/wiki/index.php/Environment_Variables [...] Hi Éric, A very interesting list, indeed. May I ask how/where you have found all these variables? Some of them for me sound really deprecated or for build time use only. Per

Re: [dev] Documenting environment variables

Eike Rathke wrote: Hi Rüdiger, On Thu, Sep 15, 2005 at 12:06:15 +0200, Rüdiger Timm wrote: A very interesting list, indeed. Great list, yes. May I ask how/where you have found all these variables? Some of them for me sound really deprecated or for build time use only. Perhaps we

[dev] CVS problems. Please do not cwsresync

We currently have CVS problems which may lead to silent errors as described in i56353. Please atm do no resync any childworkspace, otherwise you may risk damaging it. Rüdiger - To unsubscribe, e-mail: [EMAIL PROTECTED] For ad

Re: [dev] CVS problems. Please do not cwsresync

I have not seen that error since friday. Allthough i56353 is still 'new' and its cause is unknown, for know I see no direct threat. You may 'cwsresync' again. Rüdiger Rüdiger Timm wrote: We currently have CVS problems which may lead to silent errors as described in i563

Re: [dev] new incubator : Call for Name

Joerg Barfurth wrote: Hi, Laurent Godard wrote: - extensions.openoffice.org (already 3 votes) -1, We already have a cvs module named 'extensions' in the 'util' project. This situation (a module in one project is named like another project) is prone to cause confusion. Unfortunately we

Re: [dev] Build ID INSANITY...

Mathias Bauer wrote: Jens-Heiner Rechtien wrote: Here I disagree. The version shound contain only the regular version number, but why not showing the build version directly in the "About dialog" below the version (instead of asking for "CTRL-SDT to display it")? Yes, please let's do this.

Re: [dev] Completely lost in the building process...

Alexandre Laforest wrote: Hi all, [...] Thus, I have followed the instructions I found at: http://tools.openoffice.org/dev_docs/build_windows_tcsh.html#BuildingaFullBuildofOpenOffice, but got stuck at the /Generating the Build Environment and Build Tools /step: I can not seem to get the

Re: [dev] workspace handling

Martin, Could you shed some light on this? What's the current policy for nominating / holding back childworkspaces? In 'releases' you announced a 'code freeze' date, but that's not reached yet. http://wiki.services.openoffice.org/wiki/OOoRelease204 Rüdiger Jens-Heiner Rechtien wrote: Hi C

Re: [dev] Re-opening a milestone that has been announced as "ready for CWS usage"?

While talking about exceptions: even a possible rule of marking single milestones as not usable for accepting child workspaces needs exceptions. For example, there are childworkspaces working on build problems, code cleanup (license, remove obsolete files, ...), or CWS or build related tools wh

Re: [dev] Re: All smoketests are equal but some smoketests are more equal than others

Kai Backman wrote: On 9/4/06, Stefan Taxhet <[EMAIL PROTECTED]> wrote: Components covering our code base are tied to CVS modules and/or projects. The form(s) at http://qa.openoffice.org/issue_handling/submission_gateway.html tries to help with finding the best component. Interestingly enough

Re: [dev] A word about (missing) Specification Documents and (late) Feature Mails

Hi Frank, Frank Schönheit - Sun Microsystems Germany wrote: Hi Michael, [...] Other people could have told you that integrating the CWS on 2006-11-06, one day after the UI freeze, could cause trouble with translation (I don't think it did it this case). while you made some valid points, this

Re: [dev] Error 65280

Mikaël De Bie wrote: Hello, I get an error when I try to compile OpenOffice, I got the sources by cvs (SRC680 OpenOffice2). Please do not use tag 'SRC680'. Better specify a milestone such as 'SRC680_m190' instead. Unfortunately, 'SRC680' is not a well maintained tag, it holds files long r

Re: [dev] Open Office build doesn't create the package !!

Kevin Williams wrote: I have been trying to compile and install Open Office 2.0.3 on BLFS system using gcc-4.1.1. The first time I tried it balked out on epm. As I have epm installed, open office setup tried to package it with epm and epm complained about the package name having characters othe

Re: [dev] Open Office build doesn't create the package !!

Hi Kevin, First, we should really move this discussion to dev@installation.openoffice.org to get the experts on board. Kevin Williams wrote: Thanks for the response, If not tar.gz, I should be able to get the unpackaged product, which I can simply copy it over to the destination. In fact thi

Re: [dev] Open Office build doesn't create the package !!

Sorry, Kevin, I hadn't seen your latest mail of success. So, just ignore this one. And gratulations for finally reaching your goal! Rüdiger Rüdiger Timm wrote: [...] - To unsubscribe, e-mail: [EMAIL PROTECTED

[dev] New Master Workspace for OOo 2.2 Release opened

New Master Workspace for OOo 2.2 Release opened === OpenOffice.org release 2.2 is approaching, see http://wiki.services.openoffice.org/wiki/OOoRelease22 This brings some changes in CWS handling: *Choosing CWS Release* -- Owners o

Re: [dev] SISSL is *really* deprecated

Issue #73721# only mentions files from 'cppu' and 'jurt'. Who'll take care of the rest? Rüdiger Stephan Bergmann wrote: Pavel Janík wrote: Hi, the following files still reference the license SISSL (files from helpcontent2 are not included on purpose): [...] cppu/source/uno/IdentityMappin

Re: [dev] Extending the binfilter Module

Kay Ramme - Sun Germany - Hamburg wrote: FYI Matthias Huetsch, Malte Timmermann, Michael Brauer and I recently had a discussions regarding how to deal with binfilter in case of incompatible changes of modules used by binfilter. We came up with the following recipe: For every request of an

Re: [dev] Extending the binfilter Module

Thorsten Behrens wrote: Caolan McNamara <[EMAIL PROTECTED]> writes: On Fri, 2007-02-02 at 14:18 +0100, Pavel Janík wrote: What about making binfilter SO only module? ;-) -1 Unfortunately .sdw etc documents exist and are a fact of life, we do still need to import them. e.g. my performance

Re: [dev] Extending the binfilter Module

Mathias Bauer wrote: Rüdiger Timm schrieb: Kay Ramme - Sun Germany - Hamburg wrote: FYI Matthias Huetsch, Malte Timmermann, Michael Brauer and I recently had a discussions regarding how to deal with binfilter in case of incompatible changes of modules used by binfilter. We came up with

Re: [dev] Extending the binfilter Module

Frank Schönheit - Sun Microsystems Germany wrote: Hi Rüdiger, being late to the thread, and being the one who implicitly initiated this ... Why would you copy additional stuff into binfilter? Because binfilter has a code base which lives several years in the past, whilst the current code b

Re: [dev] Extending the binfilter Module

Kay Ramme - Sun Germany - Hamburg wrote: Hi Ruediger, Rüdiger Timm wrote: Mathias Bauer wrote: I think the problem is that you can't give a fixed order for 2,3 and 4. This must be checked for every single case. Perhaps Kay should point this out in the wiki. OK, accepted. But from my

Re: [dev] Extending the binfilter Module

Rüdiger Timm wrote: Kay Ramme - Sun Germany - Hamburg wrote: Hi Ruediger, Rüdiger Timm wrote: Mathias Bauer wrote: I think the problem is that you can't give a fixed order for 2,3 and 4. This must be checked for every single case. Perhaps Kay should point this out in the wik

Re: [dev] Extending the binfilter Module

Armin Le Grand wrote: [...] That's the right way to go. Please take in mind what kind of code is/will be moved to binfilter: - code that is no longer used in the 'living' office modules, but needed by the old binary filter mechanisms - code that is completely rearranged and cannot be ada

Re: [dev] OOo w/o URE

Caolan McNamara wrote: On Tue, 2007-02-13 at 09:54 +0100, Stephan Bergmann wrote: FYI: Yeah, I'm very much in favour of this myself. Split the build into two parts the API stable ure stuff, and the rest. I'm trying to home

Re: [dev] OOo w/o URE

Mathias Bauer wrote: Rüdiger Timm schrieb: Caolan McNamara wrote: On Tue, 2007-02-13 at 09:54 +0100, Stephan Bergmann wrote: FYI: <http://odftoolkit.openoffice.org/servlets/ReadMsg?list=dev&msgNo=32> [...] Second reason is that (curently) this does not fit our development st

[dev] CWS Handling: Binary Incompatible Changes

Change in CWS Handling == Summary: When you are doing binary incompatible changes in your CWS, please mark those modules 'incompatible' in EIS. Detailed Description: - *Background*: For all current cod

Re: [dev] CWS Handling: Binary Incompatible Changes

Stephan Bergmann wrote: Rüdiger Timm wrote: *New Policy*: Mark modules where you have done binary incompatible changes. What about those infamous cases as adding an idl file to udkapi and thus having to rebuild offapi, offuh, ridljar---do we just continue to keep these dependencies

Re: [dev] Re: Errors while building m202 on windows, ask for help

Perhaps the path name is too long. Try setting TEMP dir to something more basic, f.e. /cygdrive/c/temp Ruediger blueeagle wrote: > Hello all,Hello Martin, > I am building the M205 now. this error occured too. Wish you can give me some > advices. > Regards, > LiuTao > >> Hello Martin, >> Thank

Re: [dev] build error

Jim Watson wrote: On 24/03/2007, at 8:33 AM, Jim Watson wrote: On 24/03/2007, at 4:50 AM, Mathias Bauer wrote: nandan k wrote: Hi All, Where can I find the corresponding .idl for the header file XTextAppendAndConvert.hpp? 16:33 it's not under com/sun/star/text directory in solver also

Re: [dev] Re: Trial Version creation

Maulik Gordhandas wrote: hi is there any method through which one can create a trail version of openoffice.. i heard about product=demo.. but can anyone explain how to make use of this function!! thanks As we've told you on IRC, there is no such function for OOo. If you really heard about pr

Re: [dev] IMPORTANT ANNOUNCEMENT: HEDABU DOESN'T EXIST ANYMORE

Bjoern Milcke wrote: Hi Vladimir, IMPORTANT IMPORTANT IMPORTANT IMPORTANT IMPORTANT IMPORTANT === Hi all, the ongoing SRC680 m209 build brings important change to our build environment. Since that milestone hedabu procedure will not wo

Re: [dev] IMPORTANT ANNOUNCEMENT: HEDABU DOESN'T EXIST ANYMORE

Frank Schönheit - Sun Microsystems Germany wrote: Hi Mathias, In case you wonder how you can find out which header files you might have changed: use cwsanalyze to find all changes in your CWS. This is the best way to avoid problems, it is known that not all possible combinations of header chan

Re: [dev] Removed hedabu: Some non-existant headers in svx delivered

Bjoern Milcke wrote: Hi, I noticed that many headers in svx were delivered twice in svx/prj/d.lst. After the hedaburemove01 CWS was integrated some of those remained, one fixed and one in the old version. The following headers are affected: svdattr.hxx xhatch.hxx xoutx.hxx xpoly.hxx I pr

[dev] IMPORTANT: cwsresync currently does not work

Since the OOo site upgrade cwsresync does not work. There are two issues. For one of them a fix is available, the other one is still in evaluation. http://www.openoffice.org/issues/show_bug.cgi?id=76821 "cwsresync after site upgrade" Changes in CVS require adaptions in output parsing. This has

Re: [dev] IMPORTANT: cwsresync currently does not work

Rüdiger Timm wrote: Since the OOo site upgrade cwsresync does not work. There are two issues. For one of them a fix is available, the other one is still in evaluation. http://www.openoffice.org/issues/show_bug.cgi?id=76821 "cwsresync after site upgrade" Changes in CVS require ad

Re: [dev] IMPORTANT: cwsresync currently does not work

Rüdiger Timm wrote: Rüdiger Timm wrote: Since the OOo site upgrade cwsresync does not work. There are two issues. For one of them a fix is available, the other one is still in evaluation. http://www.openoffice.org/issues/show_bug.cgi?id=76821 "cwsresync after site upgrade" Chan

Re: [dev] Re: [qa-dev] Can we do more regression testing?

Jörg Jahnke wrote: Hi, the reason why the Wiki page speaks of mandatory tests I have mentioned in a previous mail: Jörg Jahnke schrieb: The problem with such tests not being mandatory is that, sooner or later, some tests would break. That again would lead to a state where the user of th

Re: [dev] Re: [qa-dev] Can we do more regression testing?

Mathias Bauer wrote: [...] Anything else would be insane. I took that for granted. But I also want to believe that running several hours of tests for e.g. automatic styles would be worth the effort. This is a good example where I suspect that possible regressions would stay unnoticed by automa

Re: [dev] Re: [qa-dev] Can we do more regression testing?

Jörg Jahnke wrote: Hi Hennes, Hennes Rohling schrieb: ... But don't make everything mandatory. If I change a string in the setup or change platform dependend code for systemintegration I don't want to do a mandatory test that tests whether all dialogs in the Calc still work. - Hennes T

Re: [dev] pdb files for official build

Hi Martin On 24.11.2010 11:54, Martin Hollmichel wrote: On 11/23/2010 01:16 PM, Knut Olav Bøhmer wrote: Hi, Is it possible to get the pdb files for the official build (3.2.1 and 3.2.0) generally speaking, I would say yes, maybe somebody @releng may have a look, if any sensitive data are incl

Re: [dev] SSH access to Mercurial

On 30.11.2010 14:33, Pavel Laštovička wrote: Hello, how do I get write access to Mercurial? I have created an issue (98488) and have added it it as a dependency to issue 94002. It has been a week since then. Hi Pavel, No need to worry, you did it right (assumed you also have signed the Copyr