]] Didier 'OdyX' Raboud
> There are _plenty_ of changes that one needs to care about in a stable
> upgrade: things like mandatory postfixing of Apache configuration files,
> removal
> of specific Python3 versions, removal of upstart, etc. Having to change a
> shebang isn't a big deal given th
Le 1 septembre 2017 14:16:14 GMT+02:00, Mattia Rizzolo a
écrit :
>On Fri, Sep 01, 2017 at 11:41:36AM +0100, Ian Jackson wrote:
>> One thing you I would consider is that it would be nice if scripts in
>> Debian packages were made more portable to other distros. So Debian
>> packages should grad
On Fri, Sep 01, 2017 at 11:41:36AM +0100, Ian Jackson wrote:
> One thing you I would consider is that it would be nice if scripts in
> Debian packages were made more portable to other distros. So Debian
> packages should gradually change to use /usr/bin/node. I am very
> conservative about these
Jérémy Lal writes ("Re: Bug#754462: Bug#862051: nodejs (6.11.2~dfsg-1)
experimental; urgency=medium"):
> So, a short NEWS entry explaining /usr/bin/node is now available by default,
> and that /usr/bin/nodejs will stay available indefinitely ?
> Or even nothing and just a c
On Thursday, 31 August 2017 13:08:58 CEST Sam Hartman wrote:
> There are cases where people mix stderr and stdout. There are cases
> where people treat any unexpected output on stderr as a failure in
> automated scripts.
I rest my case. Thanks for the explanation. :-)
All the best
2017-08-31 19:08 GMT+02:00 Sam Hartman :
> > "Dominique" == Dominique Dumont writes:
>
> Dominique> On Thursday, 31 August 2017 13:58:23 CEST Thorsten Glaser
> wrote:
> >> > How about printing a "nice" warning explaining it would be a
> >> good idea to > move to /usr/bin/node ?
>
> "Dominique" == Dominique Dumont writes:
Dominique> On Thursday, 31 August 2017 13:58:23 CEST Thorsten Glaser wrote:
>> > How about printing a "nice" warning explaining it would be a
>> good idea to > move to /usr/bin/node ?
>>
>> That will break scripts that do:
>>
> "Julien" == Julien Puydt writes:
Julien> Hi, Le 31/08/2017 à 13:52, Jérémy Lal a écrit :
>> How about printing a "nice" warning explaining it would be a good
>> idea to move to /usr/bin/node ? Then in next next release drop
>> the nodejs symlink.
Julien> May I suggest t
On Thursday, 31 August 2017 13:58:23 CEST Thorsten Glaser wrote:
> > How about printing a "nice" warning explaining it would be a good idea to
> > move to /usr/bin/node ?
>
> That will break scripts that do:
>
> x=$(nodejs somescript)
This kind of script won't break if the deprecation warning is
Hi,
Le 31/08/2017 à 13:52, Jérémy Lal a écrit :
> How about printing a "nice" warning explaining it would be a good idea to
> move to /usr/bin/node ? Then in next next release drop the nodejs symlink.
May I suggest to have /usr/bin/nodejs print a nice deprecation warning
to use /usr/bin/node, and
On Thu, 31 Aug 2017, Julien Puydt wrote:
> May I suggest to have /usr/bin/nodejs print a nice deprecation warning
> to use /usr/bin/node, and just *never* remove it?
On Thu, 31 Aug 2017, Didier 'OdyX' Raboud wrote:
> Le jeudi, 31 août 2017, 13.52:00 h CEST Jérémy Lal a écrit :
> > How about pri
Le jeudi, 31 août 2017, 13.58:23 h CEST Thorsten Glaser a écrit :
> Do not drop it before *after* the next release, so people have,
> at the very least, one full release of time to switch their
> scripts in a way that works with both the old and new names
> *first*, gradually.
They have Stretch fo
Le jeudi, 31 août 2017, 12.25:50 h CEST Ian Jackson a écrit :
> Philip Hands writes ("Bug#862051: nodejs (6.11.2~dfsg-1) experimental;
urgency=medium"):
> > I guess that one could do something like moving the symlink into another
> > -legacy style package, and recomend t
On Thu, 31 Aug 2017, Jérémy Lal wrote:
> How about printing a "nice" warning explaining it would be a good idea to
> move to /usr/bin/node ?
That will break scripts that do:
x=$(nodejs somescript)
Or even ./somescript when that has a #!/usr/bin/env nodejs shebang.
> Then in next next release d
2017-08-31 13:25 GMT+02:00 Ian Jackson :
> Philip Hands writes ("Bug#862051: nodejs (6.11.2~dfsg-1) experimental;
> urgency=medium"):
> > I guess that one could do something like moving the symlink into another
> > -legasy style package, and recomend that from the main
Philip Hands writes ("Bug#862051: nodejs (6.11.2~dfsg-1) experimental;
urgency=medium"):
> I guess that one could do something like moving the symlink into another
> -legasy style package, and recomend that from the main package for one
> release to keep upgrades h
Ian Jackson writes:
> Jérémy Lal writes ("Bug#862051: nodejs (6.11.2~dfsg-1) experimental;
> urgency=medium"):
>> Maybe i didn't express myself properly: the idea is to keep /usr/bin/nodejs
>> until it's no longer needed - be it other debian packages or
Jérémy Lal writes ("Bug#862051: nodejs (6.11.2~dfsg-1) experimental;
urgency=medium"):
> Maybe i didn't express myself properly: the idea is to keep /usr/bin/nodejs
> until it's no longer needed - be it other debian packages or other user
> scripts.
Earlier you sai
Jérémy Lal writes:
> 2017-08-30 11:50 GMT+02:00 Philip Hands :
>
>> Jérémy Lal writes:
>>
>> > 2017-08-29 21:39 GMT+02:00 Didier 'OdyX' Raboud :
>> >
>> >> Le mardi, 29 août 2017, 17.46:22 h CEST Thorsten Glaser a écrit :
>> >> > Leave /usr/bin/nodejs there for at least one more release.
>> >>
>
2017-08-30 11:50 GMT+02:00 Philip Hands :
> Jérémy Lal writes:
>
> > 2017-08-29 21:39 GMT+02:00 Didier 'OdyX' Raboud :
> >
> >> Le mardi, 29 août 2017, 17.46:22 h CEST Thorsten Glaser a écrit :
> >> > Leave /usr/bin/nodejs there for at least one more release.
> >>
> >> I'll just note for the purp
Jérémy Lal writes:
> 2017-08-29 21:39 GMT+02:00 Didier 'OdyX' Raboud :
>
>> Le mardi, 29 août 2017, 17.46:22 h CEST Thorsten Glaser a écrit :
>> > Leave /usr/bin/nodejs there for at least one more release.
>>
>> I'll just note for the purpose of the TC discussion that as of nodejs
>> 6.11.2~dfsg-
2017-08-29 21:39 GMT+02:00 Didier 'OdyX' Raboud :
> Le mardi, 29 août 2017, 17.46:22 h CEST Thorsten Glaser a écrit :
> > Leave /usr/bin/nodejs there for at least one more release.
>
> I'll just note for the purpose of the TC discussion that as of nodejs
> 6.11.2~dfsg-3 (the version currently in u
Le mardi, 29 août 2017, 17.46:22 h CEST Thorsten Glaser a écrit :
> Leave /usr/bin/nodejs there for at least one more release.
I'll just note for the purpose of the TC discussion that as of nodejs
6.11.2~dfsg-3 (the version currently in unstable) , the /usr/bin/nodejs → node
symlink still exists
On Tue, 29 Aug 2017, Didier 'OdyX' Raboud wrote:
> I'm quite convinced that large parts of the Node.js ecosystem will cope well
> without any /usr/bin/nodejs available in stretch.
>
> So I'm not convinced it's really worth the trouble to keep it around for
> another stable release; I'd probably
> "Didier" == Didier 'OdyX' Raboud writes:
Didier> For good reasons, Debian forcibly introduced a special-case
Didier> when Node.js first appeared in a stable release through only
Didier> shipping it under /usr/bin/nodejs. That forced hundreds of
Didier> projects to cope wit
Le mardi, 29 août 2017, 12.32:19 h CEST Sam Hartman a écrit :
> > "Thorsten" == Thorsten Glaser writes:
> Thorsten> Hi,
>
> >> * Restore /usr/bin/node following CTTE #862051 Let's try to drop
> >> /usr/bin/nodejs before buster. Replaces and Conflicts
> >> nodejs-legacy. Clos
> "Thorsten" == Thorsten Glaser writes:
Thorsten> Hi,
>> * Restore /usr/bin/node following CTTE #862051 Let's try to drop
>> /usr/bin/nodejs before buster. Replaces and Conflicts
>> nodejs-legacy. Closes: #754462.
Thorsten> please do NOT completely replace an ABI betwee
Hi,
> * Restore /usr/bin/node following CTTE #862051
> Let's try to drop /usr/bin/nodejs before buster.
> Replaces and Conflicts nodejs-legacy.
> Closes: #754462.
please do NOT completely replace an ABI between releases.
Leave /usr/bin/nodejs there for at least one more release.
Th
28 matches
Mail list logo
