Hello Nikos,you might want to first upload the fork in new queue, providing
the same binary, so the removal becomes a cruft later
I mean, to not disrupt our userbase:
with moving src:a providing a to src:b providing b
create a new src:b with new fork, but provide a and provide b, since it should
be a drop-in replacement, right?wait for it to go in testing
ask to remove only src:a because the binary is taken over by another package
does this make sense?
in case the fork is not a drop-in replacement, probably providing the old
binary name is not worth the effort, in this caseyou can do whatever you prefer
:)
G.
Il lunedì 1 luglio 2019, 13:46:28 CEST, Nikos Tsipinakis
<ni...@tsipinakis.com> ha scritto:
On 01/07, Gianfranco Costamagna wrote:
> there is an upstream fix in a fork called newsboat
>
> I'm attaching both patches to this bug report, please apply them!
I apologise for ignoring this issue earlier. I initially intended to convert
newsbeuter to a stub package pointing to newsboat but missed the buster
deadline.
Given that upstream is abandoned and there is a functionally identical fork I
intend to remove newsbeuter from the archive. It doesn't make sense to become a
pseudo-upstream to keep it in Debian.
I'll file a removal request for it next week after the Buster release.
