Hi Sebastian,

On Sun, Feb 14, 2021 at 02:49:27PM +0100, Sebastian Ramacher wrote:
> The upload of 0.12.0-2 just started a transition. Note that we are in
> soft freeze and hence transitions are no longer acceptable for bullseye.

Apologies for this: I had discussed this on #debian-devel on 2020-02-04
with (amongst others) elbrus, at which time I pinged the maintainers of
wlroots on IRC, but waited 10 days before the upload and missed that
the soft freeze window had started.

The delay & forgetting was mostly due to some mess elsewhere in Debian
eating up all my energy; I can tell you privately if it's relevant, but
it might suffice to say that antiharassment@ and DAM were involved. >_>'


> The purpose of this bug is to block wlroots from migrating to testing.

Makes sense.


> Please either revert to 0.11.0 or keep this bug open until after the
> release of bullseye.

Would it still be possible (assuming that's also Guido's preferred
solution) to request an unblock?

I uploaded at the same time a version of sway that works with it (which I've
been running for >1 month, so it's been tested) and confirmed that phox builds
against wlroots 0.12 too.  Guido mentionned he is running phox against wlroots
0.12, so that is tested too.


For reference, the ABI breakage & soname change is due to wlroots making
some part of its API private, and removing obsolete & unstable functionality
(functions wlr_xdg_*_v6_*), which account for the largest part of the diff.
I attached the debdiff, and upstream's changelog is there:
  https://github.com/swaywm/wlroots/releases/tag/0.12.0

I believe that having the same ABI and API as upstream's in Bullseye would make
maintaining wlroots easier, but I'll of course yield to Guido's opinion on this.


Again, apologies to everyone involved for the poor coordination; as I
mentionned, I'm recovering from dealing with something else, but I still
should have held back on kicking off this transition & re-checked with
everyone involved.


Best,

  nicoo

Attachment: signature.asc
Description: PGP signature

Reply via email to