Updates policy exception for go2rpm #3610

Closed
opened 2026-05-12 13:53:32 +00:00 by gotmax23 · 15 comments
Owner

Hi, I'd like to request an Updates Policy exception for go2rpm, the specfile generator used by packagers in the Go ecosystem, as I expect to make some changes that technically could be considered breaking upstream and release them across stable branches. Note that this request only concerns the go2rpm CLI interface that packagers can optionally use to generate specfiles. This is not about the Go RPM macros which are part of a separate package. It's important to Go packagers that the same version of go2rpm is available across all Fedora releases with consistent behavior so I'd like to be able to keep versions in sync.

Hi, I'd like to request an Updates Policy exception for [go2rpm](https://gitlab.com/fedora/sigs/go/go2rpm), the specfile generator used by packagers in the Go ecosystem, as I expect to make some changes that technically could be considered breaking upstream and release them across stable branches. Note that this request only concerns the go2rpm CLI interface that packagers can optionally use to generate specfiles. This is **not** about the Go RPM macros which are part of a separate package. It's important to Go packagers that the same version of go2rpm is available across all Fedora releases with consistent behavior so I'd like to be able to keep versions in sync.
Owner

+1

+1
Owner

Metadata Update from @decathorpe:

  • Issue tagged with: updates policy exception
**Metadata Update from @decathorpe**: - Issue tagged with: updates policy exception
Owner

+1

+1
Owner

Given that you are upstream, could you commit to making an announcement on fedora-devel list ahead of landing any such breaking changes in the stable repos, similarly to how someone would pre-announce a soname bump in Rawhide? It will help reduce surprises.

+1

Given that you are upstream, could you commit to making an announcement on fedora-devel list ahead of landing any such breaking changes in the stable repos, similarly to how someone would pre-announce a soname bump in Rawhide? It will help reduce surprises. +1
Owner

+1

+1
Owner

+1

+1

+1

+1
Owner

+1

+1
Owner

After 7 days:
APPROVED(+7, 0, 0)

After 7 days: APPROVED(+7, 0, 0)
Owner

Metadata Update from @siosm:

  • Issue tagged with: document it, pending announcement
**Metadata Update from @siosm**: - Issue tagged with: document it, pending announcement

Metadata Update from @fale:

  • Issue untagged with: pending announcement
**Metadata Update from @fale**: - Issue **un**tagged with: pending announcement
Announced https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/KDZUYE4YHI5PQVKNBVLUVISRRSAZ4553/
Author
Owner
https://forge.fedoraproject.org/fesco/docs/pulls/141
Owner

PR merged. Thanks!

PR merged. Thanks!
Owner

Metadata Update from @decathorpe:

  • Issue untagged with: document it
  • Issue close_status updated to: Accepted
  • Issue status updated to: Closed (was: Open)
**Metadata Update from @decathorpe**: - Issue **un**tagged with: document it - Issue close_status updated to: Accepted - Issue status updated to: Closed (was: Open)
Sign in to join this conversation.
No milestone
No project
No assignees
8 participants
Notifications
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
fesco/tickets#3610
No description provided.