On Sun July 21 2019 21:15:31 Michele Calgaro via trinity-devel wrote:

https://mirror.git.trinitydesktop.org/gitea/TDE/tde follow instruction in readme.md that is display at the end of the page above :-)

Hi Michele,

Thanks for the pointer.

Unfortunately it still requires the main repo in order to pull in the scripts to get started (see below).

I have to take be offline for an hour or two but I will try later to clone the scripts directly from the mirror and then use them as described in readme.md.

--Mike

$ git clone https://mirror.git.trinitydesktop.org/gitea/TDE/tde Cloning into 'tde'... remote: Counting objects: 96209, done. remote: Compressing objects: 100% (31922/31922), done. remote: Total 96209 (delta 67541), reused 90043 (delta 62746) Receiving objects: 100% (96209/96209), 33.94 MiB | 485.00 KiB/s, done. Resolving deltas: 100% (67541/67541), done. $ cd tde $ git submodule init -- scripts Submodule 'scripts' (https://system@scm.trinitydesktop.org/scm/git/scripts) registered for path 'scripts' $ git submodule update -- scripts Cloning into '/cache/TDE/tde/scripts'... fatal: unable to access 'https://system@scm.trinitydesktop.org/scm/git/scripts/': The requested URL returned error: 503 fatal: clone of 'https://system@scm.trinitydesktop.org/scm/git/scripts' into submodule path '/cache/TDE/tde/scripts' failed Failed to clone 'scripts'. Retry scheduled Cloning into '/cache/TDE/tde/scripts'... ^C $ git --version git version 2.20.1

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512

On 2019/07/22 04:14 PM, Mike Bird wrote:

Thanks for the pointers. This seems to work for cloning the mirror repo when the main repo is unavailable for retrieving scripts:

git clone https://mirror.git.trinitydesktop.org/gitea/TDE/tde git clone https://mirror.git.trinitydesktop.org/gitea/TDE/scripts cd tde ./scripts/switch_all_submodules_to_head_and_clean anonymous rm -rf ../scripts

Glad it helped :-)Cheers Michele

Dne po 22. července 2019 Slávek Banko napsal(a):

Dne po 22. července 2019 Mike Bird napsal(a):

...

Thanks for the pointers. This seems to work for cloning the mirror repo when the main repo is unavailable for retrieving scripts:

git clone https://mirror.git.trinitydesktop.org/gitea/TDE/tde git clone https://mirror.git.trinitydesktop.org/gitea/TDE/scripts cd tde ../scripts/switch_all_submodules_to_head_and_clean anonymous rm -rf ../scripts

--Mike

Here is one simplification:

git clone https://mirror.git.trinitydesktop.org/gitea/TDE/tde git clone https://mirror.git.trinitydesktop.org/gitea/TDE/scripts tde/scripts cd tde ../scripts/switch_all_submodules_to_head_and_clean anonymous

...because scripts can be cloned directly to the desired location in the main 'tde' module, so we can remove git submodule init and update from the original instructions.

I think that this way we can edit it in Readme.md. What is your opinion?

Cheers

...of course it was supposed to be "./scripts/...", as in the original instructions. So once again and correctly:

git clone https://mirror.git.trinitydesktop.org/gitea/TDE/tde git clone https://mirror.git.trinitydesktop.org/gitea/TDE/scripts tde/scripts cd tde ./scripts/switch_all_submodules_to_head_and_clean anonymous

Cheers

Dne po 22. července 2019 Mike Bird napsal(a):

On Mon July 22 2019 05:37:18 Slávek Banko wrote:

...

...because scripts can be cloned directly to the desired location in the main 'tde' module, so we can remove git submodule init and update from the original instructions.

I think that this way we can edit it in Readme.md. What is your opinion?

The reason I didn't try that is because I don't know whether git can convert a .git directory in scripts to a .git regular file when scripts becomes a submodule.

I've got a test running but it will take a few hours.

--Mike

I can confirm that it works. If the git repository already exists in the destination folder, then call "git submodule init" uses this repository and will simple write the information to the ".git/config" file in the master repository. As a result, the only difference is that "scripts/.git" will not just be a file, but a regular git folder - the same as it would be in ".git/modules/scripts" if the initial cloning would be done using git submodule init + git submodule update. And this is no problem at all, everything works fine. After all, in this way the submodules were placed in older versions of the git.

Cheers

Dne po 22. července 2019 Mike Bird napsal(a):

On Mon July 22 2019 09:18:47 Slávek Banko wrote:

...

I can confirm that it works. If the git repository already exists in the destination folder, then call "git submodule init" uses this repository and will simple write the information to the ".git/config" file in the master repository. As a result, the only difference is that "scripts/.git" will not just be a file, but a regular git folder

• the same as it would be in ".git/modules/scripts" if the initial

cloning would be done using git submodule init + git submodule update. And this is no problem at all, everything works fine. After all, in this way the submodules were placed in older versions of the git.

If anyone wants convert the scripts submodule afterwards to match the others they can "git submodule absorbgitdirs".

--Mike

Nice - I didn't know this command. As I see in the documentation, this command is new from GIT 2.12 (my GIT is 2.11). At the same time I see information that git directories was part of submodules before git 2.7.8.

There seems to be no objection to modifying the instructions in Readme.md for cloning scripts into tde/scripts, as I mentioned in an earlier mail.

Cheers