Bug#844922: [Pkg-javascript-devel] Bug#844922: Bug#844922: Node-string-decoder

2016-11-23 Thread Ross Gammon
On 11/23/2016 08:59 AM, Jérémy Lal wrote:
> 2016-11-23 8:53 GMT+01:00 Ross Gammon :
>> Hi,
>>
>> This node module was originally packaged as it was a dependency of something
>> (I can't remember).
>>
>> If there is nothing depending on it, we should probably remove it from the
>> archive. The string-decoder function from the core nodejs should be used
>> instead (patching the module that needs it if required). Node-string-decoder
>> is mainly used when a nodejs project wants to stick to an old version of
>> this function.
>>
>> Regards,
> 
> All right, can you fill the ftp.debian.org RM request please ?
> 
> Jérémy
> 

Done!



signature.asc
Description: OpenPGP digital signature


Bug#844922: [Pkg-javascript-devel] Bug#844922: Node-string-decoder

2016-11-23 Thread Jérémy Lal
2016-11-23 8:53 GMT+01:00 Ross Gammon :
> Hi,
>
> This node module was originally packaged as it was a dependency of something
> (I can't remember).
>
> If there is nothing depending on it, we should probably remove it from the
> archive. The string-decoder function from the core nodejs should be used
> instead (patching the module that needs it if required). Node-string-decoder
> is mainly used when a nodejs project wants to stick to an old version of
> this function.
>
> Regards,

All right, can you fill the ftp.debian.org RM request please ?

Jérémy



Bug#844922: Node-string-decoder

2016-11-22 Thread Ross Gammon

Hi,

This node module was originally packaged as it was a dependency of 
something (I can't remember).


If there is nothing depending on it, we should probably remove it from 
the archive. The string-decoder function from the core nodejs should be 
used instead (patching the module that needs it if required). 
Node-string-decoder is mainly used when a nodejs project wants to stick 
to an old version of this function.


Regards,

Ross



Bug#844922: node-string-decoder: FTBFS: Tests failures

2016-11-18 Thread Lucas Nussbaum
Source: node-string-decoder
Version: 0.10.25-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> plan:
>   start: 1
>   end: 0
>   skipAll: true
> failures:
>   - tapError: 'Plan of 1..0, but test points encountered'
>   command: /usr/bin/nodejs
>   arguments:
> - test/simple/test-string-decoder-end.js
>   file: test/simple/test-string-decoder-end.js
>   ...
> 
> 1..1
> # failed 1 of 1 tests
> # time=158.079ms
> debian/rules:11: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   
http://aws-logs.debian.net/2016/11/18/node-string-decoder_0.10.25-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.