Re: CentOS Stream suitability as a production webserver

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



On 1/7/21 9:53 AM, Phil Perry wrote:
> On 07/01/2021 09:47, Jamie Burchell wrote:
>> Didn't the CentOS Vault repo ensure that every package ever published
>> was still available?
>>
> 
> Yes, it did, but that is not the intention for CentOS Stream moving
> forward. Only packages in CentOS Linux are moved to the vault at point
> release time. CentOS Stream only ever has the LATEST package version and
> nothing else.
> 
> There is a bug filed for this issue here:
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=1908047
> 
> If it is likely to be an issue for you, please make that known. The more
> people this affects, the more likely it may be addressed.
> 
> 

This exists:

https://composes.centos.org/

I think at some point there is a plan to make builds from koji also
available, though we can't right nwo (only the production instance is
available and we can't open it to alld/l because of bandwidth).


>>> On 7 Jan 2021, at 07:03, Gordon Messmer <gordon.messmer@xxxxxxxxx>
>>> wrote:
>>>
>>> On 1/6/21 8:01 PM, Strahil Nikolov via CentOS wrote:
>>>> - No chance to "yum history undo last" as there are no older packages
>>>
>>>
>>> I've seen that mentioned as a change pretty frequently, but I don't
>>> think it is in any meaningful sense.
>>>
>>> In CentOS Stream, package versions may be rebased periodically, and
>>> the public repos will no longer have older packages to install when
>>> using "undo" or "rollback".
>>>
>>> In CentOS, package versions may be rebased at minor releases, and the
>>> public repos will no longer have older packages to install when using
>>> "undo" or "rollback".
>>>
>>> It's true that you might be able to roll back a simple patch in
>>> CentOS in between minor releases, but those are the updates that
>>> everyone seems to regard as being the safest, and least likely to
>>> cause problems, and therefore the least likely to need
>>> undo/rollback.  The only rational conclusion I can come to is that it
>>> doesn't matter if you're talking about CentOS today or Stream in the
>>> future: If you want to be able to roll back, you need a private
>>> mirror that keeps the package versions that you use.  If you don't
>>> want a mirror, then you need to build, test, and deploy complete
>>> images rather than making incremental changes to mutable systems. 
>>> None of this is new, it's always been this way and people have just
>>> accepted it.
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
https://lists.centos.org/mailman/listinfo/centos




[Index of Archives]     [CentOS]     [CentOS Announce]     [CentOS Development]     [CentOS ARM Devel]     [CentOS Docs]     [CentOS Virtualization]     [Carrier Grade Linux]     [Linux Media]     [Asterisk]     [DCCP]     [Netdev]     [Xorg]     [Linux USB]


  Powered by Linux