Hi Tobias!
Thanks for takin time to reply!
On 28/10/2022 11:00, Tobias Frost wrote:
Hi Alec,
On Fri, Oct 28, 2022 at 10:15:49AM +0200, Alec Leamas wrote:
The core issue here is opencpn, wxsvg is a dependency. The problem with
opencpn is that it has a plugin universe, and updating the current 5.6.2
version to wxWidgets 3.2 would break the plugin ABI.
Is this breakage due to wxWidgets or due to other upstream changes?
If the latter, *it might be* possible to backport the wxWidgets patches,
however whether that is feasible I don't know…
The breakage is about wxWidgets, backporting wxWidgets patches is
certainly not possible. End even it it was, it just not worth it for a
window for about a month.
Don't see that as a threat. Sure it is annoying but testing removal
is temporary and as you package will be still in backports, people
should be able to install from there, if they are on stable…
If they are on testing, well, that is the peril of testing.
Ah... Feared being forced to pass the NEW queue if removed from testing.
Now less nervous...
More generally, any response to a release critical bug will restart
the removal timer. So if you reply to the bugs below, and document
the plan, this will reset the timer, so you can delay the automatic
removal a bit. However, that will not stop the release team for
manually removal; contrary, they might be unhappy if people using
this as tactic to delay autoremovals, as this creates work for them.
Said that, a reply to the bug laying out the plan should be done anyways,
because this is useful information for many… (If there is an upstream
discussion, set the Forwarded: BTS metainfo to link to that discussion)
I have already replied in the opencpn bug. Will do the same in the wxsvg
one, handle whatever replies turns up there and hope for the best.
Thanks for clarifying!
--alec
