#10154 Untag modules/ruby stream master from fedora-modular-{33,34} repo
Closed: Can't Fix 2 years ago by mohanboddu. Opened 2 years ago by jackorp.

  • Describe the issue

modules/ruby master stream builds should not be present in fedora-modular-{33,34} repo as it is not a valid branch, and the master stream does not have a valid default profile.

untagging these two builds should be enough:
* F33: module-ruby-master-3320200820044938-601d93de
* F34: module-ruby-master-3420200820044938-058368ca

Relevant rhbz: https://bugzilla.redhat.com/show_bug.cgi?id=1748895
Relevant issue: https://pagure.io/releng/issue/10139

  • When do you need this? (YYYY/MM/DD)

2021-06-10 (The sooner the better.)

  • When is this no longer needed or useful? (YYYY/MM/DD)

  • If we cannot complete your request, what is the impact?

Ruby module master stream remains in mentioned Fedoras, without default profile, and because of the current state concerning master branches, without any maintenance.


Metadata Update from @mohanboddu:
- Issue tagged with: low-gain, low-trouble, ops

2 years ago

This cannot be fixed as we are not running any composes out of f34-modular or f33-modular tag as that is the GA content.

Lets discuss on how to fix the issue in #10139 as untagging is not an option.

Metadata Update from @mohanboddu:
- Issue close_status updated to: Can't Fix
- Issue status updated to: Closed (was: Open)

2 years ago

Login to comment on this ticket.

Metadata
Boards 1
Ops Status: Backlog