-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
gitea restore dump #2405
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
Comments
|
apt-get is being taken care of by @MTecknology, better keep
this ticket just for the `restore` command (if it's not
a duplicated already)
|
Looks like ticket for restore already exists: #1637
Close as duplicated ?
|
didnt find any word about "apt-get update" or something. |
@MasterDimmy That WIP is for the relevant Debian ITP. |
any progress? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions. |
Closing as restore command exists and we don't have the power to put Gitea into upstream Debian release (and there are many reasons listed on the linked report why it isn't easy/possible -- mainly that all of the proper dependencies will never be packaged/kept up to date in a way that works). #31 includes discussion on making a .deb build and some people have linked to ones they have created/maintain |
there are ways to install gitea via package mangager: https://docs.gitea.io/en-us/install-from-package/ |
We need ability to do:
The text was updated successfully, but these errors were encountered: