On Sun, Sep 29, 2019 at 02:43:21PM +0200, Paolo Greppi wrote: > I have imported the upstream patch in a new version 1.13.0-3: > https://salsa.debian.org/js-team/node-yarnpkg/commit/6808cd918e8c12182e14666c715bb1d372d82449/pipelines > > I have checked that it now uses https even if http links are present in > yarn.lock as follows: > > mkdir /tmp/qw > cd /tmp/qw > yarnpkg add string-width > rm -rf node_modules/ > sed -i 's/https:/http:/g' yarn.lock > yarnpkg cache clean strip-ansi > yarnpkg cache clean string-width > yarnpkg cache clean ansi-regex > yarnpkg cache clean emoji-regex > yarnpkg cache clean is-fullwidth-code-point > yarnpkg cache clean strip-ansi > > strace -s 256 yarnpkg install &> q > ping registry.yarnpkg.com # it's 104.16.22.35 > grep 104.16.22.35 q > > I get this: > connect(21, {sa_family=AF_INET, sin_port=htons(443), > sin_addr=inet_addr("104.16.22.35")}, 16) = -1 EINPROGRESS (Operazione ora in > corso) > connect(22, {sa_family=AF_INET, sin_port=htons(443), > sin_addr=inet_addr("104.16.22.35")}, 16) = -1 EINPROGRESS (Operazione ora in > corso) > connect(26, {sa_family=AF_INET, sin_port=htons(443), > sin_addr=inet_addr("104.16.22.35")}, 16) = -1 EINPROGRESS (Operazione ora in > corso) > connect(27, {sa_family=AF_INET, sin_port=htons(443), > sin_addr=inet_addr("104.16.22.35")}, 16) = -1 EINPROGRESS (Operazione ora in > corso) > connect(28, {sa_family=AF_INET, sin_port=htons(443), > sin_addr=inet_addr("104.16.22.35")}, 16) = -1 EINPROGRESS (Operazione ora in > corso) > > Should I upload this to unstable ?
Yes, either that or even uploading to the new upstream version fixing the issue, both will work here as bullseye is a long way away. > Will it automatically roll to stable ? No. But we need to decice if the update should go out via a DSA or if releasing it in a point release is enough. Regards, Salvatore
