Hi,
many times we've discussed the issues around scm.trinitydesktop.org
Entering 'main/applications/kpowersave/admin' fatal: unable to access 'http://scm.trinitydesktop.org/scm/git/tde-common-admin/': The requested URL returned error: 503 fatal: run_command returned non-zero status for main/applications/kpowersave/admin . fatal: run_command returned non-zero status while recursing in the nested submodules of main/applications/kpowersave .
I have this on different packages from time to time.
The problem is if I change the url to Gitea on my side git would complain that I have unstashed changes and will refuse to work.
What is the proper way to solve this?
thank you
On Tuesday 01 of October 2019 08:27:31 deloptes wrote:
Hi,
many times we've discussed the issues around scm.trinitydesktop.org
Entering 'main/applications/kpowersave/admin' fatal: unable to access 'http://scm.trinitydesktop.org/scm/git/tde-common-admin/': The requested URL returned error: 503 fatal: run_command returned non-zero status for main/applications/kpowersave/admin . fatal: run_command returned non-zero status while recursing in the nested submodules of main/applications/kpowersave .
I have this on different packages from time to time.
The problem is if I change the url to Gitea on my side git would complain that I have unstashed changes and will refuse to work.
What is the proper way to solve this?
thank you
Hi deloptes,
currently, the only reliable solution is to use TGW from htts://mirror.git.trinitydesktop.org/gitea/ instead of SCM from the primary server. We hope to move forward with migrating the existing primary server to the new tde-box in the near future. SCM will be one of the things we want to replace...
Cheers
Slávek Banko wrote:
currently, the only reliable solution is to use TGW from htts://mirror.git.trinitydesktop.org/gitea/ instead of SCM from the primary server. We hope to move forward with migrating the existing primary server to the new tde-box in the near future. SCM will be one of the things we want to replace...
Thank you Slavek, but how should I proceed with updating the source - cause if I change the source "git remote set-url origin" it then complains I have unstashed changes?
Or should I try from time to time until it succeeds - cause it worked few weeks ago.
regards
deloptes wrote:
Or should I try from time to time until it succeeds - cause it worked few weeks ago.
I found out some of the packages had left overs pointing to scm.trinitydesktop.org and the rest to Gitea. Seems when I was updating the sources time ago something went wrong for some of them. Luckily not many.
For example
tde/main/dependencies/akode$ cat .gitmodules [submodule "cmake"] path = cmake url = http://system@scm.trinitydesktop.org/scm/git/tde-common-cmake
but
tde/main/dependencies/akode$ cat ../../../.git/modules/main/dependencies/akode/modules/cmake/config [core] repositoryformatversion = 0 filemode = true bare = false logallrefupdates = true worktree = ../../../../../../../main/dependencies/akode/cmake [remote "origin"] url = https://mirror.git.trinitydesktop.org/gitea/TDE/tde-common-cmake fetch = +refs/heads/*:refs/remotes/origin/* [branch "master"] remote = origin merge = refs/heads/master
so change into tde/main/dependencies/akode/cmake and set-url to Gitea solves it
regards
-
deloptes -
Slávek Banko