ti 23.9.2025 klo 8.56 Daniel Richard G. ([email protected]) kirjoitti: > > On Tue, 2025 Sep 23 01:03-04:00, Martin-Éric Racine wrote: > > > > I might consider pushing out a backport. Alternately, if you can > > figure out exactly which upstream Git commit fixed the issue, I might > > consider adding it to the next updates release. > > I don't have a good way of bisecting this issue, given that it occurs on > boot. The project's release notes don't hint at a fix, either. If you'd > rather just apply a minimal patch, I'd suggest the workaround in > ipv4_deladdr().
I definitely won't put in a quick workaround. > > However, pushing newer upstream versions into updates or security is a > > big no-no for Debian. > > It depends on the circumstances of the change. The chromium package > regularly goes to *-proposed-updates as a whole. Same as Firefox and Linux. In both cases bugfix releases by a large enough upstream team to have the resources to produce targeted fixes to earlier releases. Martin-Éric
