-
Ticket
-
Resolution: Done
-
Normal
-
None
-
None
-
None
-
None
-
None
-
False
-
-
False
-
None
-
3
-
None
-
OCPNODE Sprint 253 (Blue)
In the rhel9 candidate tags of 4.15 and 4.16, it currently looks like this:
| tag | build |
|---|---|
| rhaos-4.15-rhel-9-candidate | conmon-2.1.7-3.1.rhaos4.14.el9 |
| rhaos-4.15-rhel-9-candidate | cri-o-1.28.2-9.rhaos4.15.git6d902a3.el9 |
| rhaos-4.15-rhel-9-candidate | cri-tools-1.28.0-1.1.el9 |
| rhaos-4.15-rhel-9-candidate | crun-1.12-2.rhaos4.15.el9 |
| rhaos-4.15-rhel-9-candidate | ignition-2.16.2-1.1.rhaos4.14.el9 |
| rhaos-4.15-rhel-9-candidate | podman-4.4.1-10.1.rhaos4.14.el9 |
| rhaos-4.15-rhel-9-candidate | skopeo-1.11.2-20.1.rhaos4.15.el9 |
| rhaos-4.16-rhel-9-candidate | conmon-2.1.7-3.1.rhaos4.14.el9 |
| rhaos-4.16-rhel-9-candidate | cri-o-1.28.2-9.rhaos4.15.git6d902a3.el9 |
| rhaos-4.16-rhel-9-candidate | cri-tools-1.29.0-1.el9 |
| rhaos-4.16-rhel-9-candidate | crun-1.12-2.rhaos4.15.el9 |
| rhaos-4.16-rhel-9-candidate | ignition-2.16.2-1.1.rhaos4.14.el9 |
| rhaos-4.16-rhel-9-candidate | podman-4.4.1-10.1.rhaos4.14.el9 |
| rhaos-4.16-rhel-9-candidate | skopeo-1.11.2-10.1.rhaos4.14.el9 |
Both 4.15 and 4.16 have builds with 4.14 in their name. They are here either through direct tagging, or through brew inheritance:
⫸ brew list-tag-inheritance rhaos-4.16-rhel-9-candidate | head
rhaos-4.16-rhel-9-candidate (132994)
.... └─rhaos-4.16-rhel-9 (132993)
.... └─rhaos-4.15-rhel-9 (121787)
.... └─rhaos-4.14-rhel-9 (119080)
.... └─rhaos-4.13-rhel-9 (114085)
.... └─rhaos-4.12-rhel-9 (106594)
⫸ brew list-tag-inheritance rhaos-4.15-rhel-9-candidate | head
rhaos-4.15-rhel-9-candidate (121788)
.... └─rhaos-4.15-rhel-9 (121787)
.... └─rhaos-4.14-rhel-9 (119080)
.... └─rhaos-4.13-rhel-9 (114085)
.... └─rhaos-4.12-rhel-9 (106594)
It would be pretty, but also prevent some potential for calamities, if every brew tag had a build of its own, even if there are no code or compiler changes.