On Wed, Aug 14, 2019 at 07:22:47PM +0100, Jonathan Wiltshire wrote:
> I think your summary is fine. However, this is not my area of expertise and
> I'm rather hoping Julien or Ansgar will chime in with an update.
>
> It certainly wouldn't be appropriate for me to remove a block put in place
> by someone else without extenuating circumstances.
Julien,
I am still waiting for some constructive engagement over this.
As Jonathan's comment above makes clear and is echoed by this exchange on
#debian-release yesterday:
<LeePen> Hello. #934132 is still outstanding and is now preventing resolution
of RC bug in bullseye #939101. [12:13]
<LeePen> Can we find a resolution to #934132? Thanks. [12:17]
<h01ger> weasel: zwiebelbot is missing here [12:34]
<jmw> jcristau: ^ (#934132) [13:12]
<jcristau> jmw: well i still think shipping this thing is a bad idea. but i'm
ok with somebody else removing the block. [13:21]
<jmw> I don't know enough about it to make a call on that
<jmw> but I think LeePen would appreciate some sort of response
it is obvious and completely understandable that other members of the Release
Team will not overrule your hint blocking elogind migration to bullseye. So,
resolution of this bug (and the resulting FTBFS in bullseye) is down to you.
I have tried to answer your concerns in detail. If you think my answers are
inadequate or still think there are issues that need to be addressed, please
specify them. If not, please remove your block of elogind's migration to
testing.
Thank you.
Mark
