Re: Akregator backport

On Sat, 31 Dec 2022 at 15:15:13 -0500, Jeff Sacksteder wrote:
> I sent this to debian-qt-kde as well but I don't think that's the best place.
> 
> As of 11.6, Stable continues to include Akregator 4:20.08.3-1, which includes
> this bug:
> 
> [1]https://bugs.kde.org/show_bug.cgi?id=429444
> [2]https://invent.kde.org/pim/akregator/-/commit/546db72108cba99a1881e97349ce55db5d1da88e
> 
> Testing includes 4:22.08.3-1 and presumably fixes this.
> 
> A backport would fix my issue, but it's not clear to me how to request updates
> be included into a future 11.7 Stable point release.

Please open a bug in the affected package (presumably akregator) by
running reportbug on an affected stable system, and provide the same
information you did here. The Qt/KDE maintainers should assess the balance
between the benefit of fixing the bug in stable and the regression risk
of making the changes.

The -backports list and suite are for whole new upstream feature
releases being backported in their entirety, like flatpak 1.14.x in
bullseye-backports. The goal of these backports is to get new features
and larger/higher-risk changes (refactoring, redesigns, etc.), not for
individual bug fixes.

Stable updates are for individual fixes being backported, like gtk+3.0
3.24.24-4+deb11u2 in bullseye, or for upstream stable-branch releases,
like flatpak 1.10.x in bullseye. This can either be for security fixes,
or for sufficiently high-importance and/or low-risk non-security bug
fixes. It seems like that is what you are requesting here, but these
requests are tracked on the bug tracking system, not the -backports list.

    smcv