On Tue, 23 Jan 2024, at 16:19, Faidon Liambotis wrote: > I think that's big enough to make me at least a bit uncomfortable about > a cherry-pick to stable. Could you elaborate on your use case? It sounds > like this manifests only with a large number of layers, and I'm not sure > how common this is.
Thanks for taking a look. I'm just running the home-assistant container ghcr.io/home-assistant/home-assistant. > The alternative to a stable update is a backport of the latest podman > version (currently 4.8.3), plus associated packages like > containers/storage, of course. It's a moderate amount of work; Reinhard > who's been doing the version updates in unstable could speak more to the > work he's been putting into package updates etc. It would help with > bringing in a lot of more fixes from what I'd consider a very active > upstream. We also have #1059496, as another recent, concrete example. > > I'm still unsure and debating targeted s-p-u fixes vs. a backport. My > concern is basically that we may start playing whack-a-mole. A quick > peek at the upstream changelog reveals tons of fixed bugs in every > release, and us trying to keep up by cherry-picking fixes to two years > of upstream development may prove futile... > > Thoughts? I think backporting makes sense to me. In fact I built my own podman from upstream in the meantime.. Actually, I initially submitted a backport request. But gibmat thought it would be better to have it fixed in stable so everyone benefits, although I agree it's not a common thing to run into. -- Hao Wei
