On November 12, 2021 1:11 pm, Henry-Nicolas Tourneur wrote:
>
>
> Le ven 12 nov 2021 à 10:18, Fabian Grünbichler
> a écrit :
>> On November 12, 2021 6:38 am, Peter Green wrote:
>>> Package: rust-tokio-signal
>>> Version: 0.2.7-2
>>> Severity: serious
>>>
>>> rust-tokio-signal (build-)depends on version 0.1 of rust-futures.
>>> Upstream seems to
>>> have abandoned the project, there was an alpha release supporting
>>> futures 0.2, but
>>> the code appears to have been removed from the tokio git
>>> repository. So I presume
>>> it is abandoned upstream.
>>>
>>> There are no reverse dependencies in testing, there is a single
>>> reverse dependency
>>> in unstable which is rc buggy and also appears to be abandoned
>>> upstream.
>>>
>>> If there are no objections in a few weeks, I intend to file a
>>> removal request.
>>
>> same here, tokio-signal is now tokio+signal ;) accordingly, it can be
>> RMed with the rest of the legacy tokio 0.1 crates once tokio 1.0 has
>> been uploaded
>>
>
> I would not even wait for tokio 1.0 upload and request removal of
> tokio-signal could be done right away.
>
> As it stands, it is broken due to unsastifiable build dependencies and
> it has no reverse dependencies, as Peter explained.
>
> Fabian, I see no point in keeping tokio-signal in the archive in its
> current state and the package is going away anyway as you mentionned it
> being superseeded by tokio+signal.
>
> Do you see any reasons to keep it until tokio 1.0 upload?
no, the RMs can be filed now as well of course, I just figured it's
easier to see which ones (also third-party related crates) go into the
RM pile once the successors are packaged, which means less effort for
all involved parties. but doing the first batch (those part of the
original tokio 0.1 release itself - see the tokio-process bug) now is
fine as well, we can always do a second batch post-uploads for any
remaining stuff.
