[Pkg-javascript-devel] Bug#841981: nodejs should recommend ca-certificates
> > Apart from that, is there a good reason to use Recommend instead of Depend > ? I'm not sure. wget and libcurl3-gnutls both "Recommend" rather than "Depend" on ca-certificates. I think it's because wget still mostly works without it, it's just TLS/SSL connections that fail. Node.js behaves the same way, all of Node.js works without ca-certificates except for TLS connections. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#841981: nodejs should recommend ca-certificates
Package: nodejs Version: 4.6.0~dfsg-2 Severity: normal Dear Maintainer, When CA certificates are not available, Node.js scripts that try to connect to remote servers using TLS/SSL fail with "Error: unable to get local issuer certificate". Other packages that rely on TLS (such as wget and libcurl3-gnutls) recommend the ca-certificates package, so nodejs should probably also do this. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (750, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-openvz-042stab108.8-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages nodejs depends on: ii libc62.23-4 ii libgcc1 1:6.1.1-10 ii libicu57 57.1-2 ii libssl1.0.2 1.0.2h-1 ii libstdc++6 6.1.1-10 ii libuv1 1.9.1-1 ii zlib1g 1:1.2.8.dfsg-2+b1 nodejs recommends no packages. nodejs suggests no packages. -- no debconf information -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#841980: nodejs should recommend ca-certificates
Package: nodejs Version: 4.6.0~dfsg-2 Severity: normal Dear Maintainer, When CA certificates are not available, Node.js scripts that try to connect to remote servers using TLS/SSL fail with "Error: unable to get local issuer certificate". Other packages that rely on TLS (such as wget and libcurl3-gnutls) recommend the ca-certificates package, so nodejs should probably also do this. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (750, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-openvz-042stab108.8-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages nodejs depends on: ii libc62.23-4 ii libgcc1 1:6.1.1-10 ii libicu57 57.1-2 ii libssl1.0.2 1.0.2h-1 ii libstdc++6 6.1.1-10 ii libuv1 1.9.1-1 ii zlib1g 1:1.2.8.dfsg-2+b1 nodejs recommends no packages. nodejs suggests no packages. -- no debconf information -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] /usr/bin/nodejs vs /usr/bin/node
Hello Debian JavaScript maintainers! I'm one of the developers on Yarn (https://yarnpkg.com/), a new package manager for JavaScript designed to replace the "npm" client. As part of our launch, I created Debian packages and am hosting them in our own repository. For the initial release, I used #!/usr/bin/nodejs as the shebang, due to the fact that the Debian Node.js release calls its binary "nodejs" instead of "node". However, this caused issues on systems where people have installed Node.js through other installation methods. In an ideal world, all dependencies would be installed through dpkg/apt-get, but unfortunately that's not the case in the Node.js ecosystem. Some people install Node.js through an application called "nvm" (https://github.com/creationix/nvm), which is designed to allow the user to toggle between different Node.js versions. This is useful for developers to easily test their code on multiple different Node.js versions, as using the Debian Node.js package does not allow multiple versions to be installed concurrently. Since nvm uses the upstream Node.js releases directly, its binaries are named "node" instead of "nodejs". This means that I needed to modify Yarn to use a shell script that checks for both "node" (for users of nvm and Node.js on non-Debian platforms) and "nodejs" (for users of the Debian node.js packages). This works for Yarn itself, but there's many many scripts and packages on npm that rely on the binary being called "node" rather than "nodejs" and totally fall apart on Debian/Ubuntu. A lot of users end up symlinking /usr/local/bin/node to /usr/bin/nodejs to get a usable environment. Given the amount of complexity stemming from Debian renaming this binary and the fact that it breaks parts of the Node.js ecosystem, is there any chance it will be renamed back to "node" in the future, or for /usr/bin/node to be symlinked to /usr/bin/node (perhaps using the update-alternatives system to allow the user to choose whether they want to symlink nodejs or ax25-node, in case they have both installed)? Thank you! Kind Regards, Daniel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
