-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Import Unadopted repositories - nothing happens #21632
Comments
Is the repo searched in the unadopted repositories UI? |
Could you check if the repository does exist? |
I'm not sure what you actually mean. From the beginning I was able to git clone it, once again : backlog
But after clicking Yes repository remains unimported What I have found so far : |
Update And, yes, it works in 1.15.11. So, something happened between 1.15.11 and 1.16.0 |
I couldn't reproduce this in my macOS.
|
Know nothing about macos, my install is on windows. ini file is renamed to txt to make it attachable to github. So far workaround for initial migration to Gitea
No workaround for existing installations |
A bug was introduced in go-gitea#17865 where filepath.Join is used to join putative unadopted repository owner and names together. This is incorrect as these names are then used as repository names - which shoud have the '/' separator. This means that adoption will not work on Windows servers. Fix go-gitea#21632 Signed-off-by: Andrew Thornton <art27@cantab.net>
A bug was introduced in #17865 where filepath.Join is used to join putative unadopted repository owner and names together. This is incorrect as these names are then used as repository names - which shoud have the '/' separator. This means that adoption will not work on Windows servers. Fix #21632 Signed-off-by: Andrew Thornton <art27@cantab.net>
Backport go-gitea#21646 A bug was introduced in go-gitea#17865 where filepath.Join is used to join putative unadopted repository owner and names together. This is incorrect as these names are then used as repository names - which shoud have the '/' separator. This means that adoption will not work on Windows servers. Fix go-gitea#21632 Signed-off-by: Andrew Thornton <art27@cantab.net>
Backport go-gitea#21646 A bug was introduced in go-gitea#17865 where filepath.Join is used to join putative unadopted repository owner and names together. This is incorrect as these names are then used as repository names - which shoud have the '/' separator. This means that adoption will not work on Windows servers. Fix go-gitea#21632 Signed-off-by: Andrew Thornton <art27@cantab.net>
Backport #21646 A bug was introduced in #17865 where filepath.Join is used to join putative unadopted repository owner and names together. This is incorrect as these names are then used as repository names - which shoud have the '/' separator. This means that adoption will not work on Windows servers. Fix #21632 Signed-off-by: Andrew Thornton <art27@cantab.net>
Backport #21646 A bug was introduced in #17865 where filepath.Join is used to join putative unadopted repository owner and names together. This is incorrect as these names are then used as repository names - which shoud have the '/' separator. This means that adoption will not work on Windows servers. Fix #21632 Signed-off-by: Andrew Thornton <art27@cantab.net>
Description
I`ve copied existing bare repository from Gitblit server. Put it into folder as said in #18390 . Now I have repository searched through UI.
After clicking on Yes, Adopt - nothing happens, UI brings me back to repository list.
In DevTools I see unadpted/303, and after redirect - repos/200.
In logs there are only templates lines
2022/10/30 12:08:17 ...s/context/context.go:219:HTML() [D] [635e3f01] Template: admin/repo/unadopted
2022/10/30 12:09:29 ...s/context/context.go:219:HTML() [D] [635e3f49-2] Template: admin/repo/list
Tried to set dev RUN_MODE - nothing changed.
Tried to check repository if it is valid bare -
git clone as.git
Cloning into 'as'...
done.
Happens under windows.
My username is Administrator, but disk path is administrator/as.git.
Also tried to rename user to all-lowercase, all the same.
Gitea Version
1.17.3
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
Nothig notable to share
Git Version
2.38
Operating System
Windows server 10.0
How are you running Gitea?
Fresh download, as service and from command line
Database
SQLite
The text was updated successfully, but these errors were encountered: