Bernstein, Noam CIV USN NRL (6393) Washington DC (USA)
2020-Dec-15 17:09 UTC
[CentOS] What are the differences between CentOS Linux and CentOS Stream?
> On Dec 15, 2020, at 12:07 PM, Phil Perry <pperry at elrepo.org> wrote: > > 3. 'dnf downgrade foo' doesn't work as only latest/one copy of each package in Stream repository so no opportunity to downgrade/roll back broken packages.Really? I hadn't appreciated that. How does one the contribute back to RH/the community by checking at what point something broke?
Matthew Miller
2020-Dec-15 17:13 UTC
[CentOS] What are the differences between CentOS Linux and CentOS Stream?
On Tue, Dec 15, 2020 at 05:09:39PM +0000, Bernstein, Noam CIV USN NRL (6393) Washington DC (USA) via CentOS wrote:> > 3. 'dnf downgrade foo' doesn't work as only latest/one copy of each package in Stream repository so no opportunity to downgrade/roll back broken packages. > Really? I hadn't appreciated that. How does one the contribute back to RH/the community by checking at what point something broke?I don't know the answer here but it's a good point to raise. In Fedora, we don't keep all updates on our mirrors either, but we _do_ make them accessible forever from our build system (https://koji.fedoraproject.org/koji/), and there's a command-line tool for easily pulling the packages from a build. -- Matthew Miller <mattdm at fedoraproject.org> Fedora Project Leader
Phil Perry
2020-Dec-15 17:16 UTC
[CentOS] What are the differences between CentOS Linux and CentOS Stream?
On 15/12/2020 17:09, Bernstein, Noam CIV USN NRL (6393) Washington DC (USA) via CentOS wrote:>> On Dec 15, 2020, at 12:07 PM, Phil Perry <pperry at elrepo.org> wrote: >> >> 3. 'dnf downgrade foo' doesn't work as only latest/one copy of each package in Stream repository so no opportunity to downgrade/roll back broken packages. > > Really? I hadn't appreciated that. How does one the contribute back to RH/the community by checking at what point something broke?No idea. I assume it might be related to repository size, as once daily updates start flowing into Stream, repo size could get rather large rather quickly? But it doesn't sit well being asked to test (and feedback) on testing packages with no way to roll back / downgrade when things break. 'dnf downgrade' isn't something I (thankfully) have to use often, but when you need it, it's a lifesaver. Seems like a regression to me.