On 06.12.2022 10:41, Lassi Kortela wrote:
>> I have an issue regarding gitea.scheme.org, is there already a place
>> where i could post it?
>>
>> If not, may I suggest a repository under schemeorg organization named
>> gitea.scheme.org? I could then post my issue there.
>
> Sure! There is now
> https://github.com/schemeorg-community/gitea.scheme.org. Probably a
> good idea to keep on GitHub instead of Gitea; otherwise, if the latter
> malfunctioned, it would prevent you from complaining about it :)

I agree that it makes sens to have it in GitHub. However I do not have
GitHub account so I hope you dont mind if I tell you about the issues
here anyway. :)

One reason I would prefer issues of git repo over mailing list is that
if there is an issue and answer is "This issue is known but we cant/wont
do anything aboout it because of reason X" then people who run into the
issue again can search the issues and see that this has already been
adressed. So if any of my issues is one of those feel free to ad it as
an issue to GitHub. Sorry in advance for extra work.

# Cloning repository with SSH
When trying to clone repository with SSH the address is displayed as
xxxxxx@localhost:Username/repository.git which I assume should be
xxxxxx@gitea.scheme.org:Username/repository.git?

But even after I change the address to correct one on my machine it
says:

```
Cloning into 'Instructions'...
xxxxxx@gitea.scheme.org: Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
```

Even when I have the ssh key added in my account settings.

I will send the other issue in other thread because it is related to
backups.

Please do note that I do not expect anyone to hurry or even fix these
things at all and last thing I want to add is stress.