PKG,BLD: Koji, COPR repo

[westurner]

A fedora Koji or COPR RPM build would rebuild with new releases; there's automation to limit time to patch.

• https://docs.fedoraproject.org/en-US/package-maintainers/New_Package_Process_for_New_Contributors/

  If you want to make ad-hoc builds available for users while you are getting the package into the official repositories, consider using Copr. It is a lightweight automated build system that can create repositories using the SRPM you upload. You can use this Copr space to point reviewers to your src.rpm and spec.

  • https://pagure.io/fedpkg
• https://docs.fedoraproject.org/en-US/package-maintainers/Package_Maintenance_Guide/#_do_a_local_build_of_the_current_state
• https://docs.fedoraproject.org/en-US/quick-docs/publish-rpm-on-copr/
  • https://github.com/rpm-software-management/tito

[jonathanspw]

There's already a COPR repo: https://copr.fedorainfracloud.org/coprs/jonathanspw/headscale/

[westurner]

Thanks, shouldve searched harder. Repology has PKG version badges for a README.md that i think works with COPR in addition to the fedpkg Fedora repos: https://repology.org/project/linux/badges

…

On Wed, Mar 27, 2024, 5:37 PM Jonathan Wright ***@***.***> wrote: There's already a COPR repo: https://copr.fedorainfracloud.org/coprs/jonathanspw/headscale/ — Reply to this email directly, view it on GitHub <#6 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAMNSYTECLAIJIEI6VLJ33Y2M3Z3AVCNFSM6AAAAABFLURWVSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRUGAZTINRSG4> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[jonathanspw]

repology doesn't work with COPR, but I did add a basic build status badge to the README.md so it will appear on the front of this repo.

Once the new version is out (0.23) I will probably package it officially for Fedora, and maybe EPEL. I hesitate on EPEL only due to required Go versions. I can overcome the old versions in COPR but not in EPEL.

[westurner]

https://docs.fedoraproject.org/en-US/epel/#what_packages_and_versions_are_available_in_epel :

• https://packages.fedoraproject.org/search?query=golang
• https://src.fedoraproject.org/rpms/golang
• https://pkgs.org/search/?q=golang
• https://rpms.remirepo.net/rpmphp/zoom.php?rpm=golang
• https://github.com/conda-forge/go-feedstock/blob/main/recipe/meta.yaml ,

EPEL Next:

• https://docs.fedoraproject.org/en-US/epel/epel-about-next/#example_workflow
• https://docs.fedoraproject.org/en-US/epel/epel-about-next/#can_i_use_epel_next_to_provide_a_newer_version_of_a_package_than_whats_in_epel

https://docs.fedoraproject.org/en-US/epel/#communicating_with_epel :

• https://www.google.com/search?q="epel-devel"+"golang"
• https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/
• https://forums.rockylinux.org/t/go-development-with-vim-and-vim-go-on-rocky-linux-9/9901/4

https://github.com/golang/build :

• https://rpms.remirepo.net/rpmphp/zoom.php?rpm=golang-x-build
  • 2022: https://src.fedoraproject.org/rpms/golang-x-build/c/c55913fdaba2289b863b745e397d74b5be5b6c66?branch=rawhide

[jonathanspw]

I'm a bit confused by your reply.

I'm already a Fedora/EPEL packager and am familiar with the Go versions available in each. I think I'm missing your point, can you elaborate?

[westurner]

Just preparing the docs links for later reference. Thanks for considering a fedpkg package in addition to of another COPR repo in /etc/yum.repos.d/ with an includepkgs to minimally maintain: https://docs.ansible.com/ansible/latest/collections/ansible/builtin/yum_repository_module.html#parameter-includepkgs