[CentOS-devel] CentOS Stream 8 is now ahead of RHEL 8

Wed Mar 15 18:27:37 UTC 2023
Ewoud Kohl van Wijngaarden <ewoud+centos at kohlvanwijngaarden.nl>

On Wed, Mar 15, 2023 at 12:34:57PM -0500, Brian Stinson wrote:
>
>On Wed, Mar 15, 2023, at 11:42, Ewoud Kohl van Wijngaarden wrote:
>> On Wed, Mar 15, 2023 at 04:42:48PM +0100, Adam Samalik wrote:
>>>I'm glad to announce we have resumed releasing
>>>CentOS Stream 8 updates, and that Stream 8
>>>is now following the same workflow as Stream 9.
>>>
>>>This is a follow up of
>>>https://lists.centos.org/pipermail/centos-devel/2023-February/142762.html
>>>
>>> ...
>>>
>>>We're finishing up cloud and container images,
>>>you will find them in the same places as before when ready.
>>
>> Will you also update https://app.vagrantup.com/centos/boxes/stream8?
>> It's now 2 years old. There is a more recent build (from 2022-09-13) on
>> https://cloud.centos.org/centos/8-stream/x86_64/images/ but that's still
>> quite old for something that should be rolling forward.
>>
>> https://bugs.centos.org/view.php?id=18028 is tracking this, but hasn't
>> seen an update in a long time.
>
>We'll be focusing on other image types before we decide how we want to handle vagrant images. For now, Stream 8 boxes are stored in the buildsystem, example: https://kojihub.stream.centos.org/koji/buildinfo?buildID=31089

Would it be possible to upload once manually so we at least have a 
semi-recent image?

>Stream 9 images, as usual, can be found on cloud.centos.org: https://cloud.centos.org/centos/9-stream/x86_64/images/

This is inconvenient since there simply isn't a centos/stream9 on 
https://app.vagrantup.com/centos which means every consumer needs to 
manually specify it. There also isn't a 
CentOS-Stream-Vagrant-9-latest.x86_64.vagrant-libvirt.box either which 
means manual work.

Is there any way I could help? Like providing a (Python) script to 
create the entries via the Vagrant Cloud API. I obviously just can't run 
it myself without credentials.