Hi,
Am 07.03.24 um 20:33 schrieb Eric Valette:
On 07/03/2024 19:58, Rene Engelhard wrote:
> My point also was that your reopening of the bug is wrong since the
maintainer can't do anything about it.
E.g. if libreoffice wasn't rebuilt against most t64 r-deps since it a)
also has libraries needing the rename which I b) did when the transition
starts c) had a new release anyway. If that did't happen and LO wasn't
rebuilt for the t64 libraries it now needs I'd have reacted the same way
as for the bug you reopened. Can't do anything about that, the binNMUs
will happen somwehen when ready.
And you probably need to get out of your amd64 bubble, see below
My "bubble" probably represent in volume 99% of debian
users/installations so that is a big bubble!
True. My laptop also is one (but incidentially runs stable as main
system until the freeze when it will start running testing. rinse and
repeat). I personally have a sid only in said sid VM.
I admit that unstable installation volume is far less than stable but
the proportion of people using unstable on arm/xxx is probably
identical as stable.
I don't think so, actually. It's probably lesser on sid for arm than
the stable vs. unstable ratio of amd64. But it doesn't really matter
anyway. arm* is release architectures and so need to get the rebuilds
anyway at some time.
I completely can understand that the RT doesn't do those bin-NMUs per
arch (when?) but just when it's actually ready.
Well well, you annoy 99% of unstable debian users.
unstable is unstable. Don't use it if you can't handle stuff like this.
And yes, be it even for more days or however it takes.
Regards,
Rene
