[Pkg-javascript-devel] debian-js at lists.debian.org, nodejs transition

[shirish शिरीष]

Hi all,

I have been observing nodejs for quite sometime and also seeing the
archives, but the archives do not tell what is happening.

While as Utkarsh shared in at
https://alioth-lists.debian.net/pipermail/pkg-javascript-devel/2019-October/036552.html

>From an outsider one is unable to know what is going to happen and how.

For e.g. there is an automated nodejs transition which doesn't tell
what is going to transition and when except for these lines -

    Affected: .depends ~ /\b(libnode72|libnode64)\b/
    Good: .depends ~ /\b(libnode72)\b/
    Bad: .depends ~ /\b(libnode64)\b/

Now how does a person who isn't a nodejs expert know what is going to
happen and when ?

For e.g. -

$ node --version
v10.15.2

While apt-cache policy tells of three versions of nodejs -

$ apt-cache policy nodejs
nodejs:
  Installed: 10.15.2~dfsg-2
  Candidate: 10.15.2~dfsg-2
  Version table:
     12.10.0~dfsg-2 100
        100 http://cdn-fastly.deb.debian.org/debian experimental/main
amd64 Packages
     10.16.3~dfsg-1 100
        100 http://cdn-fastly.deb.debian.org/debian unstable/main amd64 Packages
 *** 10.15.2~dfsg-2 900
        900 http://cdn-fastly.deb.debian.org/debian testing/main amd64 Packages
        100 /var/lib/dpkg/status

Now should we be waiting for nodejs 10.16.3 or 12.10 I don't know. As
there is no transition bug to follow I cannot even know when the
transition is going to start or not. Could somebody help in untangling
this mess.

-- 
          Regards,
          Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com

E493 D466 6D67 59F5 1FD0 930F 870E 9A5B 5869 609C