-
-
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
Add Debian package registry #22854
Add Debian package registry #22854
Conversation
Upload/download/delete
TODO: Release/Package files
Referenced from github.com/esell/deb-simple
Apt-key is deprecated; use trusted.gpg.d instead. Use sources.list.d instead.
This comment was marked as off-topic.
This comment was marked as off-topic.
fixing them now |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Didn't look at the code in detail,
here's what I've seen while skimming through it as it seems to get merged soon.
debian.registry = Setup this registry from the command line: | ||
debian.registry.info = Choose <code><distribution></code> and <code><component></code> from the list below. | ||
debian.install = To install the package, run the following command: | ||
debian.documentation = For more information on the Debian registry, see <a target="_blank" rel="noopener noreferrer" href="https://docs.gitea.io/en-us/packages/debian/">the documentation</a>. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See above
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Even worse, the link is basically deprecated already as the move to .com
is already planned…
Erm what? |
Oh. |
This reverts commit bf77e21.
@KN4CK3R sorry we had to revert this because of accidential merge, please raise another PR with discussions resolved, it will be fast-tracked. |
New PR is #24426. |
Co-authored-by: @awkwardbunny This PR adds a Debian package registry. You can follow [this tutorial](https://www.baeldung.com/linux/create-debian-package) to build a *.deb package for testing. Source packages are not supported at the moment and I did not find documentation of the architecture "all" and how these packages should be treated. ![grafik](https://user-images.githubusercontent.com/1666336/218126879-eb80a866-775c-4c8e-8529-5797203a64e6.png) Part of #20751. Revised copy of #22854. --------- Co-authored-by: Brian Hong <[email protected]> Co-authored-by: techknowlogick <[email protected]> Co-authored-by: Giteabot <[email protected]>
Fixes #20751 This PR adds a RPM package registry. You can follow [this tutorial](https://opensource.com/article/18/9/how-build-rpm-packages) to build a *.rpm package for testing. This functionality is similar to the Debian registry (#22854) and therefore shares some methods. I marked this PR as blocked because it should be merged after #22854. ![grafik](https://user-images.githubusercontent.com/1666336/223806549-d8784fd9-9d79-46a2-9ae2-f038594f636a.png)
This PR adds an Alpine package registry. You can follow [this tutorial](https://wiki.alpinelinux.org/wiki/Creating_an_Alpine_package) to build a *.apk package for testing. This functionality is similar to the Debian registry (#22854) and therefore shares some methods. I marked this PR as blocked because it should be merged after #22854. ![grafik](https://user-images.githubusercontent.com/1666336/227779595-b76163aa-eea1-4a79-9583-775c24ad74e8.png) --------- Co-authored-by: techknowlogick <[email protected]> Co-authored-by: silverwind <[email protected]> Co-authored-by: Giteabot <[email protected]>
Had to de-assign the milestone in this case as there's the followup PR that has the same + a bit more that wasn't reverted, |
Co-authored-by: @awkwardbunny
This PR adds a Debian package registry. You can follow this tutorial to build a *.deb package for testing. Source packages are not supported at the moment and I did not find a documentation of the architecture "all" and how these packages should be treated.