Different problem with mirroring / sync #3895

@jayjupdhig commented on GitHub (Sep 4, 2019):

And "private" seems to have nothing to do with the "read-only" / 403 problem.

Is "private" the option that prevents the read-only-access for everyone. (Similar to GitHub i think?)

Regards, Jan

@jayjupdhig commented on GitHub (Sep 4, 2019): And "private" seems to have nothing to do with the "read-only" / 403 problem. Is "private" the option that prevents the read-only-access for everyone. (Similar to GitHub i think?) Regards, Jan

GiteaMirror commented

https://discourse.gitea.io/t/external-git-server/1425/13

@jayjupdhig commented on GitHub (Sep 6, 2019):

After a few day i saw the problem (which is not really) with the "Synchronize" button for remote repo in Gitea:

**_"On the repo main page, there is only 1 entry in vertical direction - even if there are more than 1 commit. So i saw, you have to click on “x Commits” to view all of them…

But the “remote repository is read-only” problem still persists - and no, the remote repo is NOT read-only… how i should done the first (initial) commit when it’s read only…?

And i’m still able to commit on the remote repo when i’m directly connected to it. But not if Gitea is connected to it.

And the http basic auth url stored in gitea works when i copy/paste it to browser bar:

http://admin:password@192.168.80.20/WHATEVER

And SourceTree, where i can commit to the repo (directly, no over Gitea) also uses that http basic auth.

So problem 1 i not really a problem, but problem 2 is still unsolved!

How to solve it?

Thank you for your feedbacks,
Jan"_**

....ok, so the "remote repo is readonly" is sill present. I can't say it is a bug, but so it seems it is.

Maybe somebody can proof the opposite - that it's not a bug? If yes, i think we can close that issue.

Regards,
Jan

@jayjupdhig commented on GitHub (Sep 6, 2019): After a few day i saw the problem (which is not really) with the "Synchronize" button for remote repo in Gitea: https://discourse.gitea.io/t/external-git-server/1425/13 **_"On the repo main page, there is only 1 entry in vertical direction - even if there are more than 1 commit. So i saw, you have to click on “x Commits” to view all of them… But the “remote repository is read-only” problem still persists - and no, the remote repo is NOT read-only… how i should done the first (initial) commit when it’s read only…? And i’m still able to commit on the remote repo when i’m directly connected to it. But not if Gitea is connected to it. And the http basic auth url stored in gitea works when i copy/paste it to browser bar: http://admin:password@192.168.80.20/WHATEVER And SourceTree, where i can commit to the repo (directly, no over Gitea) also uses that http basic auth. So problem 1 i not really a problem, but problem 2 is still unsolved! How to solve it? Thank you for your feedbacks, Jan"_** ....ok, so the "remote repo is readonly" is sill present. I can't say it is a bug, but so it seems it is. Maybe somebody can proof the opposite - that it's not a bug? If yes, i think we can close that issue. Regards, Jan

GiteaMirror commented

@jayjupdhig commented on GitHub (Sep 6, 2019):

How to make font bold and/or italic here?

There are "markers" like '_**', but they don't change the text format and will be show as plain text

@jayjupdhig commented on GitHub (Sep 6, 2019): How to make font bold and/or italic here? There are "markers" like '_**', but they don't change the text format and will be show as plain text

GiteaMirror commented

@jayjupdhig commented on GitHub (Sep 6, 2019):

maybe the workaround it to commit/push only and directly to the remote repo. never push/commit to gitea.

but it's really really sub-optimal and nothing else..

@jayjupdhig commented on GitHub (Sep 6, 2019): maybe the workaround it to commit/push only and directly to the remote repo. never push/commit to gitea. but it's really really sub-optimal and nothing else..

GiteaMirror commented

@jayjupdhig commented on GitHub (Sep 10, 2019):

No anwser??

@jayjupdhig commented on GitHub (Sep 10, 2019): No anwser??

GiteaMirror commented

@lunny commented on GitHub (Sep 11, 2019):

Which one is your current problem?

@lunny commented on GitHub (Sep 11, 2019): Which one is your current problem?

GiteaMirror commented

@jayjupdhig commented on GitHub (Sep 11, 2019):

“remote repository is read-only”

But it's NOT read-only... when i connect with SourceTree, it isn't.

@jayjupdhig commented on GitHub (Sep 11, 2019): “remote repository is read-only” But it's NOT read-only... when i connect with SourceTree, it isn't.

GiteaMirror commented

@lafriks commented on GitHub (Sep 11, 2019):

It is not really understandable from Your description where error is shown in Gitea or in SourceTree?

@lafriks commented on GitHub (Sep 11, 2019): It is not really understandable from Your description where error is shown in Gitea or in SourceTree?

GiteaMirror commented

@jayjupdhig commented on GitHub (Sep 20, 2019):

create a repo on non git server A
do an initial commit
do a new migration on git server B, that server is with github
create a new migration with "mirror" option to the repo on git server A
set up the git repo from server B, the one with gitea
trying to commit & pull to the git repo on server B (gitea) will fail on that read-only problem

If there are any questions, don't hesitate to ask me.

@jayjupdhig commented on GitHub (Sep 20, 2019): 1. create a repo on non git server A 2. do an initial commit 3. do a new migration on git server B, that server is with github 4. create a new migration with "mirror" option to the repo on git server A 5. set up the git repo from server B, the one with gitea 6. trying to commit & pull to the git repo on server B (gitea) will fail on that read-only problem If there are any questions, don't hesitate to ask me.

GiteaMirror commented

@jayjupdhig commented on GitHub (Oct 3, 2019):

"It is not really understandable from Your description where error is shown in Gitea or in SourceTree?"

Gitea...

@jayjupdhig commented on GitHub (Oct 3, 2019): "It is not really understandable from Your description where error is shown in Gitea or in SourceTree?" Gitea...

GiteaMirror commented

@6543 commented on GitHub (Oct 3, 2019):

giteas repo type "mirror" only mirrors a contend !
if you like to work with it you can converte it to a normal repository - but then it wont mirror a other repository

gitea akts like a real mirror - you CAN change things in the real world but the mirror only display a inverted version wich CANT BE MODIFIED

@6543 commented on GitHub (Oct 3, 2019): giteas repo type "mirror" only mirrors a contend ! if you like to work with it you can converte it to a normal repository - but then it wont mirror a other repository gitea akts like a real mirror - you CAN change things in the real world but the mirror only display a inverted version wich CANT BE MODIFIED

GiteaMirror commented