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

[shirish शिरीष]

at bottom :-

On 18/10/2019, Jérémy Lal <kapouer at melix.org> wrote:
> Actually you already have that information, but let me be clear about it:
> - nodejs transitions in same Major versions are uncoordinated - they are
> supposed to go well.
> - nodejs transitions to other Major version - 12 here - are going to cause
> troubles (even if not that much) so will be announced.
>
> Does this answer your question?
>
> Le ven. 18 oct. 2019 à 20:57, shirish शिरीष <shirishag75 at gmail.com> a
> écrit :
>
>> 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.
>>


Hi Jeremy,
It actually does not. What I forgot to mention is also this info. that
I see on tracker.debian.org/nodejs  .

  excuses:

    Migration status for nodejs (10.15.2~dfsg-2 to 10.16.3~dfsg-1):
BLOCKED: Maybe temporary, maybe blocked but Britney is missing
information (check below)
    Issues preventing migration:
    missing build on mips64el
    missing build on mipsel
    Additional info:
    Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nodejs.html
    Should wait for tests relating to nodejs 10.16.3~dfsg-1, but
forced by elbrus
    autopkgtest for node-unicode-data: amd64: Test in progress
    37 days old (needed 5 days)
    Not considered

Now do we need for auto-icu migration to happen and complete which we
don't know will start when, as libicu65 is in experimental atm :(

https://tracker.debian.org/pkg/icu

Looking forward to knowing more.

-- 
          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