golang-vitess and golang-sigs-k8s-kustomize were retired a few months ago in https://gitlab.com/fedora/sigs/go/package-data/-/commit/bb016bfab8f8d5a270043d1d3ac663a0e07476f1#5d57c6b3040139804da769d6fc4a8373e2be1947_1709_1707
golang-vitess
golang-sigs-k8s-kustomize
These created the following leaves:
golang-github-adalogics-fuzz-headers golang-github-aquarapid-vaultlib golang-github-buger-jsonparser golang-github-howeyc-gopass (already retired) golang-github-martini-contrib-auth golang-github-martini-contrib-gzip golang-github-martini-contrib-render golang-github-monochromegane-gitignore golang-github-opentracing-contrib-grpc golang-github-pires-proxyproto golang-github-planetscale-pargzip golang-github-planetscale-tengo golang-github-sjmudd-stopwatch golang-github-z-division-zookeeper golang-gopkg-ldap-2
Checking dependencies with last available spec:
golang-github-adalogics-fuzz-headers golang-github-aquarapid-vaultlib golang-github-buger-jsonparser golang-github-howeyc-gopass (already retired) golang-github-martini-contrib-auth golang-github-martini-contrib-gzip golang-github-martini-contrib-render golang-github-opentracing-contrib-grpc golang-github-pires-proxyproto golang-github-planetscale-pargzip golang-github-planetscale-tengo golang-github-sjmudd-stopwatch golang-github-z-division-zookeeper golang-gopkg-ldap-2
golang-github-monochromegane-gitignore
Metadata Update from @mikelo2: - Issue assigned to mikelo2
Metadata Update from @mikelo2: - Issue assigned to gotmax23 (was: mikelo2)
Announced in https://lists.fedoraproject.org/archives/list/golang@lists.fedoraproject.org/thread/G4S6FHGRGKY7RXOPQ4LZYDG4RSAZUUJ2/
Done. Thanks everyone!
Metadata Update from @gotmax23: - Issue status updated to: Closed (was: Open)
I wasn't aware of this (not a member of Go SIG). My package (golang-github-buger-jsonparser) was retired without notification. No FTBFS bug was open, either. I'm not sure I understand what's going on here? Do you retire packages that are leaves even if they build fine? I'm not sure I agree with such policy. Why don't you remove the SIG from maintainers instead if it's not a primary maintainer of a package?
golang-github-buger-jsonparser
Regarding how this was communicated, we announced this on the mailing list and agreed on this in the meeting. We definitely should've notified maintainers individually, as well. I apologize for not doing that.
Regarding the issue itself, starting with https://fedoraproject.org/wiki/Changes/Mass_Retire_Golang_Leaves (which involved many more packages and was the first time we did anything like this, thus warranting a full-on Change proposal), the SIG has made a concerted effort to remove unused libraries to reduce the large maintenance burden shared amongst such few packagers. We keep a continually updated record of all leaf packages in https://gitlab.com/fedora/sigs/go/package-data/-/blob/main/leaves?ref_type=heads, and here we identified some that had been in the list for a while and formally discussed the issue in the SIG meeting before proceeding.
Hi,
I'm not completely sure why kustomize was retired, but I would like to maintain the package. As it's very useful in a GitOps setup where kustomize build the deployments and it's verified with kubeconform using Flux CRD schema both on develop laptop and in CI pipelines on merge requests.
Hi, I'm not completely sure why kustomize was retired, but I would like to maintain the package. As it's very useful in a GitOps setup where kustomize build the deployments and it's verified with kubeconform using Flux CRD schema both on develop laptop and in CI pipelines on merge requests.
kustomize was retired due to the complexity maintaining k8s related packages have.
I'm working to restore it as vendored package and should be ready soon™.