Am 07.03.24 um 19:21 schrieb Eric Valette:
On 07/03/2024 18:57, Rene Engelhard wrote:
That one is tracked and will get appropriate bin-NMUs from the
release team, I am sure.
It is right that this uninstallability is "being part of the normal
things due to transition".
I'm sure it will be done at some point. However, I just point out that
on amd64
Maybe, though in my sid VM with all tasks installed plasma-workspace
fails to upgrade, claiming about gdb-minmal | gdb not to be installed
whereas both of that install, but that doesn't help it futher. Didn't
debug, no KDE person.
My point also was that your reopening of the bug is wrong since the
maintainer can't do anything about it. He will not schedule the bin-NMU
(actually can't, and a manual binary only build will just make it
blocked from entering testing, requiring a bin-NMU _again_). As he said
it IS "being part of the normal things due to transition".
Even if it it like that for a week now or longer.
And you probably need to get out of your amd64 bubble, see below
this is the last set of packages that are uninstallable currently on
all my systems (except the one when i manually edited the control
file) and this has been so since 29 february.
And I guess it will be for some longer since the archs where t64
actually matters (armel/armhf) has most of the affected packages not
being rebuilt since it's stuck behind uninstallable stuff and needs
manual bootstrap uploads.
I completely can understand that the RT doesn't do those bin-NMUs per
arch (when?) but just when it's actually ready.
Regards,
Rene
