Archived
15
23
Fork
You've already forked meta
6

Idea: Packaging for distributions / hosters #29

Closed
opened 2022年11月08日 15:59:14 +01:00 by Ryuno-Ki · 14 comments
Contributor
Copy link

As far as I know, many developers aren't responsible for packaging their distributions for all those different Linux flavours (or hosters).

But I was wondering, whether it would make sense to establish some relationship to the present communities doing this for Gitea at the moment.

The idea being that we ease the adoption for people to choose codename on, say, Yunohost or stuxhost or whatever they prefer.

As far as I know, many developers aren't responsible for packaging their distributions for all those different Linux flavours (or hosters). But I was wondering, whether it would make sense to establish some relationship to the present communities doing this for Gitea at the moment. The idea being that we ease the adoption for people to choose codename on, say, Yunohost or stuxhost or whatever they prefer.

Some distributions that I'm aware of, apart from Docker Hub and GitHub releases are:

  1. Yonohost
  2. Arch User Repository

Both distributions accept contributions. I can assist packaging for both distributions, if we are going to support them.

Some distributions that I'm aware of, apart from Docker Hub and GitHub releases are: 1. [Yonohost](https://yunohost.org/en/app_gitea) 2. [Arch User Repository](https://aur.archlinux.org/packages?K=gitea) Both distributions accept contributions. I can assist packaging for both distributions, if we are going to support them.
Author
Contributor
Copy link

Hm, Debian and Rocky Linux are most likely worth to reach out to.
Rocky Linux is about to succeed CentOS.

Thanks for your assistance, Aravinth!

Hm, Debian and Rocky Linux are most likely worth to reach out to. Rocky Linux is about to succeed CentOS. Thanks for your assistance, Aravinth!

I'm a Arch Linux user, so happy to help with the AUR packaging. @Ryuno-Ki do you happen to know if they have a process to submit new packages?

I'm a Arch Linux user, so happy to help with the AUR packaging. @Ryuno-Ki do you happen to know if they have a process to submit new packages?
Author
Contributor
Copy link

I would start at https://wiki.archlinux.org/title/Arch_package_guidelines but never used Arch myself.

I would start at https://wiki.archlinux.org/title/Arch_package_guidelines but never used Arch myself.

Ah sorry, I was referring to the other distros, I'm luckily familair with the AUR process.

Ah sorry, I was referring to the other distros, I'm luckily familair with the AUR process.

I can ask our debian packager if he would be interested. Although perhaps look at Reproducible builds as well.

I can ask our debian packager if he would be interested. Although perhaps look at Reproducible builds as well.

Gitea is currently reproducible (even with CGO being enabled for SQlite)

Gitea is currently reproducible (even with CGO being enabled for SQlite)

Spoke to a debian packager I know, who is also funded by reproducible builds.

His feedback:

The packager doesn't have much experience in in go packaging ... "Worried it might be similar to rust or nodejs in the sense that the community is moving a bit too fast to package and relies on language-specific tools

or tracking thousands of dependencies

it seems to have a build failure in archlinux because the certificate for building it will expire in the future https://tests.reproducible-builds.org/archlinux/community/gitea/build2.log

e.g. the build2 is performed in the future by adjusting the clock"

https://ismypackagereproducibleyet.org/?pkg=gitea&query=query

Spoke to a debian packager I know, who is also funded by reproducible builds. His feedback: The packager doesn't have much experience in in go packaging ... "Worried it might be similar to rust or nodejs in the sense that the community is moving a bit too fast to package and relies on language-specific tools or tracking thousands of dependencies it seems to have a build failure in archlinux because the certificate for building it will expire in the future https://tests.reproducible-builds.org/archlinux/community/gitea/build2.log e.g. the build2 is performed in the future by adjusting the clock" https://ismypackagereproducibleyet.org/?pkg=gitea&query=query

Additional comment "apparently archlinux has another site where they're testing it, and it built reproducibly"

But he did say earlier he would consider following up.

Test log:

https://reproducible.archlinux.org/api/v0/builds/354118/log

Additional comment "apparently archlinux has another site where they're testing it, and it built reproducibly" But he did say earlier he would consider following up. Test log: https://reproducible.archlinux.org/api/v0/builds/354118/log

FYI:

With my enquiries into the debian process and reproducible builds I appear to have caused some queries. But this has resulted in some useful links for reproducible builds.

Verification Builds

Binary artifacts are downloaded and compared to binaries built from source (using the official buildinfo file as additional build input, if the projects needs one for reproducible builds).

https://reproducible.archlinux.org/ (Arch Linux)
https://beta.tests.reproducible-builds.org/ (Debian, Qubes)
https://r-b.engineering.nyu.edu/ (Arch Linux)
https://rebuilderd.dustri.org/ (Tails)

Build Environment Fuzzing

The source code is downloaded and built 2+ times in a diverse set of environments.

https://tests.reproducible-builds.org/archlinux/
https://tests.reproducible-builds.org/coreboot/
https://tests.reproducible-builds.org/debian/
https://tests.reproducible-builds.org/freebsd/
https://tests.reproducible-builds.org/netbsd/
https://tests.reproducible-builds.org/openwrt/
https://reproducible-builds.openeuler.org/
https://www.yoctoproject.org/reproducible-build-results/

If any one is curious and want to join the mailing list for reproducible builds the mailing list address is:

rb-general@lists.reproducible-builds.org

FYI: With my enquiries into the debian process and reproducible builds I appear to have caused some queries. But this has resulted in some useful links for reproducible builds. ## Verification Builds Binary artifacts are downloaded and compared to binaries built from source (using the official buildinfo file as additional build input, if the projects needs one for reproducible builds). https://reproducible.archlinux.org/ (Arch Linux) https://beta.tests.reproducible-builds.org/ (Debian, Qubes) https://r-b.engineering.nyu.edu/ (Arch Linux) https://rebuilderd.dustri.org/ (Tails) ## Build Environment Fuzzing The source code is downloaded and built 2+ times in a diverse set of environments. https://tests.reproducible-builds.org/archlinux/ https://tests.reproducible-builds.org/coreboot/ https://tests.reproducible-builds.org/debian/ https://tests.reproducible-builds.org/freebsd/ https://tests.reproducible-builds.org/netbsd/ https://tests.reproducible-builds.org/openwrt/ https://reproducible-builds.openeuler.org/ https://www.yoctoproject.org/reproducible-build-results/ If any one is curious and want to join the mailing list for reproducible builds the mailing list address is: rb-general@lists.reproducible-builds.org
Author
Contributor
Copy link

Thanks for your effort, @onepict.

Thanks for your effort, @onepict.
Member
Copy link

FYI, @max@toot.envsys.com has added Forgejo to the Arch User Repository:

I've started a package in the Arch User Repository for installing forgejo on arch: https://aur.archlinux.org/packages/forgejo-git

It's cloned from the PKGBUILD for gitea and it's untested as of now.

FYI, [@max@toot.envsys.com](https://toot.envsys.com/@max) has added Forgejo to the Arch User Repository: > I've started a package in the Arch User Repository for installing forgejo on arch: https://aur.archlinux.org/packages/forgejo-git > > It's cloned from the PKGBUILD for gitea and it's untested as of now.
Contributor
Copy link

@caesar has created a curated list at https://delightful.club/delightful-forgejo/ and there's a forgejo-contrib now. Other than that requests for specific integrations should be forgejo repo issues, I guess.

@caesar has created a curated list at https://delightful.club/delightful-forgejo/ and there's a `forgejo-contrib` now. Other than that requests for specific integrations should be `forgejo` repo issues, I guess.

Agreed, I'll close that issue then.

Agreed, I'll close that issue then.
Commenting is not possible because the repository is archived.
No Branch/Tag specified
readme
No results found.
Labels
Clear labels
[Decision] Building proposal(s)
We're in a decision-making process, buiding one or more proposals to address the shared aim based on the criteria
[Decision] Gathering criteria
We're in a decision-making process, gathering criteria, considerations and needs
[Decision] Integrating concerns
We're in a decision-making process, working with a proposal, trying to integrate concerns and create modifications/support such that the proposal works for everyone
Accessibility
Relates to Accessibility (a11y) of product, project and process.
Agreement proposal
Forgejo agreement proposal, following a discussion
Communication
Relates to all channels, social media, website, blog posts.
Election
Process of appointing a person into a role or team (if choosing people just for a specific one-time task, use the Entrustment label)
Entrustment
Process of choosing/approving specific people to do a critical/high-impact one-time task (if choosing people for an ongoing role/team, use the Election label)
Governance
Relates to processes, procedures and decision-making.
Meeting
An upcoming team meeting
User research - Accessibility
Requires input about accessibility features, likely involves user testing.
User research - Blocked
Do not pick as-is! We are happy if you can help, but please coordinate with ongoing redesign in this area.
User research - Community
Community features, such as discovering other people's work or otherwise feeling welcome on a Forgejo instance.
User research - Config (instance)
Instance-wide configuration, authentication and other admin-only needs.
User research - Errors
How to deal with errors in the application and write helpful error messages.
User research - Filters
How filter and search is being worked with.
User research - Future backlog
The issue might be inspiring for future design work.
User research - Git workflow
AGit, fork-based and new Git workflow, PR creation etc
User research - Labels
Active research about Labels
User research - Moderation
Moderation Featuers for Admins are undergoing active User Research
User research - Needs input
Use this label to let the User Research team know their input is requested.
User research - Notifications/Dashboard
Research on how users should know what to do next.
User research - Rendering
Text rendering, markup languages etc
User research - Repo creation
Active research about the New Repo dialog.
User research - Repo units
The repo sections, disabling them and the "Add more" button.
User research - Security
User research - Settings (in-app)
How to structure in-app settings in the future?
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
7 participants Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
forgejo/meta#29
Reference in a new issue
forgejo/meta
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?