Your message dated Fri, 6 Nov 2015 16:55:29 +0100 with message-id <563CCD71.10307@mail.dk> and subject line Re: Bug#804252: [Pkg-javascript-devel] Bug#804252: RFS: node-readable-stream/2.0.3-1 [ITP] has caused the Debian Bug report #804252, regarding RFS: node-readable-stream/2.0.3-1 [ITP] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 804252: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804252 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: RFS: node-readable-stream/2.0.3-1 [ITP]
- From: Ross Gammon <rossgammon@mail.dk>
- Date: Fri, 06 Nov 2015 16:27:35 +0100
- Message-id: <[🔎] 20151106152735.11391.66602.reportbug@localhost>
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "node-readable-stream" * Package name : node-readable-stream Version : 2.0.3-1 Upstream Author : Streams WG Team <christopher.s.dickinson@gmail.com> * URL : https://github.com/nodejs/readable-stream#readme * License : Expat Section : web It builds this binary package: node-readable-stream - Streams3, a user-land copy of the stream library from iojs v2.x To access further information about this package, please visit the following URL: http://mentors.debian.net/package/node-readable-stream Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/n/node-readable-stream/node- readable-stream_2.0.3-1.dsc Debian packaging can be found here: http://anonscm.debian.org/cgit/pkg-javascript/node-readable-stream.git Changes since the last upload: * Initial release (Closes: #796355) Regards, Ross Gammon -- System Information: Debian Release: jessie/sid APT prefers vivid-updates APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 'vivid'), (100, 'vivid-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.19.0-31-generic (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: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
- To: Jérémy Lal <kapouer@melix.org>, 804252-done@bugs.debian.org
- Subject: Re: Bug#804252: [Pkg-javascript-devel] Bug#804252: RFS: node-readable-stream/2.0.3-1 [ITP]
- From: Ross Gammon <rossgammon@mail.dk>
- Date: Fri, 6 Nov 2015 16:55:29 +0100
- Message-id: <563CCD71.10307@mail.dk>
- In-reply-to: <[🔎] CAJxTCxyfK=C2TEeK3pGjUNP27-Le8kZcDrZTx0yqSOUY+Fs1iQ@mail.gmail.com>
- References: <[🔎] 20151106152735.11391.66602.reportbug@localhost> <[🔎] CAJxTCxyfK=C2TEeK3pGjUNP27-Le8kZcDrZTx0yqSOUY+Fs1iQ@mail.gmail.com>
On 11/06/2015 04:37 PM, Jérémy Lal wrote: > You don't need this, we have nodejs 4 in debian now, and > require('readable-stream') can be patched > away easily. > > However, i'm all in favor of declaring that nodejs package Provides > node-readable-stream, > and place the shim in /usr/lib/nodejs, because i'm bored too. > > nodejs could provide > /usr/lib/nodejs/readable-stream/index.js > ``` > exports.Readable = require('stream').Readable; > ``` Yes, I did consider just patching concat-stream to use the node stream. But as you say, it is an often required patch! I thought with readable-stream mapping to the current nodejs LTS, it was worth packaging to keep around for backwards compatibility in the future. But that is probably stretch +1. I will quickly close the RFS with this mail before it gets sponsored. Then you are free to "provide" it in nodejs. The packaging is always there on Alioth if we need to resurrect it. Thanks, RossAttachment: signature.asc
Description: OpenPGP digital signature
--- End Message ---