[Pkg-javascript-devel] sockjs-client is in Debian but needs update (Was: [covid-19] shiny-server (Was: dependencies Re: ITP: streamlit))
Andrius Merkys
merkys at debian.org
Fri Feb 25 13:27:43 GMT 2022
Hello,
Replying to Nilesh and Andreas in the same mail.
On 2022-02-25 07:49, Andreas Tille wrote:
> Am Fri, Feb 25, 2022 at 03:09:36AM +0530 schrieb Nilesh Patra:
>>> Sure. It would be nice to get ACK from Pirate, though, as he owns the ITP.
>> I am a bit confused, why would you need ack from someone who ITP'ed it, even if you need the ack, you'd ask this to the maintainer, right?
> Yes. The ITP should have been closed manually long before. The fact
> that this not happened yet is IMHO a sign that the original maintainer
> does not care any more for the package (and forgot to orphan it).
I admit I got confused a bit. There is an orphaning bug [1] without an
owner and ITP bug [2] owned by Pirate Praveen. I think I will merge
these and close them with the upload.
[1] https://bugs.debian.org/836492
[2] https://bugs.debian.org/886155
>> But in any case, this does not seem to have any reverse dependencies so this should be safe to upload. As far as I know Praveen, he will not stop you until it breaks something (the package is in a bitrot anyway)
> Yes.
>
>>> FYI, the upload will have to go through NEW due to both source and binary
>>> package renaming.
>> Although this does not make much sense to do this here but still if you want to play extra safe, you might want to upload it targetting experimental.
> You might even consider using the old name for an upload to unstable and
> at the same time push a renamed package to experimental via new. This
> would enable to keep on working on shiny-server (despite I'm not sure
> whether we need to be in a hurry here ... I personally have other things
> on my table unfortunately).
Since there are no reverse dependencies on libjs-sockjs and we are not
in a hurry with shiny-server (we can still work on that with local
node-sockjs-client package), I would like to avoid experimental. This
way I would not have to deal with Breaks+Replaces due to same locations
occupied by two different packages.
Best,
Andrius
More information about the Pkg-javascript-devel
mailing list