Re: why is npm not in debian-backports ?
at bottom :-
On 24/10/2018, Pirate Praveen <praveen@onenetbeyond.org> wrote:
> On 10/24/18 5:42 PM, shirish शिरीष wrote:
>> I was documenting a mozilla add-on
>>
>> https://github.com/RequestPolicyContinued/requestpolicy/wiki/Build-Requirements
>>
>> when I was made aware that npm is not in backports.
>
> npm backporting is in progress,
> https://salsa.debian.org/js-team/npm/wikis/home
>
> I guess in 2-3 weeks we can have npm in stretch-backports (usually it
> takes a week's time to get a package in backports NEW to enter
> stretch-backports and all build dependencies should be already in
> stretch-backports to be able to add package to backports NEW).
>
Dear Praveen,
Any update/news on the npm backporting front ?
I did see https://salsa.debian.org/js-team/npm/wikis/home and saw that
you last updated
the page a week ago.
While it seems there is still some ways to go -
I am curious about the 'probably Ok' entries.
node-marked, probably OK
node-marked-man, probably OK
What would make them migrate from probably OK to the Ok queue ?
Looking forward to see npm in stretch-backports. Thank you for working on this.
--
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
EB80 462B 08E1 A0DE A73A 2C2F 9F3D C7A4 E1C4 D2D8
Reply to: