Your message dated Tue, 17 Feb 2015 00:34:10 +0100
with message-id <[email protected]>
and subject line Re: Bug#778576: unblock: node-tap/0.4.13-2
has caused the Debian Bug report #778576,
regarding unblock: node-tap/0.4.13-2
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 [email protected]
immediately.)


-- 
778576: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778576
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: [email protected]
Usertags: unblock

Please unblock package node-tap

The bug that caused this package to be scheduled for autoremoval is
fixed with this small patch which disables a single test.

This does not affect the behavior of the package itself in any way.

diff -Nru node-tap-0.4.13/debian/changelog node-tap-0.4.13/debian/changelog
--- node-tap-0.4.13/debian/changelog    2014-10-20 00:01:44.000000000 +0000
+++ node-tap-0.4.13/debian/changelog    2015-02-16 22:53:56.000000000 +0000
@@ -1,3 +1,9 @@
+node-tap (0.4.13-2) unstable; urgency=medium
+
+  * Patch fixing failing test FTBFS (Closes: #775627)
+
+ -- Jérémy Lal <[email protected]>  Mon, 16 Feb 2015 23:52:37 +0100
+
 node-tap (0.4.13-1) unstable; urgency=low
 
   * Initial release (Closes: #765988)
diff -Nru node-tap-0.4.13/debian/patches/mitigate_test_segv.patch 
node-tap-0.4.13/debian/patches/mitigate_test_segv.patch
--- node-tap-0.4.13/debian/patches/mitigate_test_segv.patch     1970-01-01 
00:00:00.000000000 +0000
+++ node-tap-0.4.13/debian/patches/mitigate_test_segv.patch     2015-02-16 
22:53:00.000000000 +0000
@@ -0,0 +1,30 @@
+Description: exit code of segv test depend on platform - do not check it
+ For reasons yet to be discovered, the assumption in segv test is wrong on
+ the platform used for https://bugs.debian.org/775627.
+Last-Update: 2015-02-16
+Author: Jérémy Lal <[email protected]>
+Forwarded: no, need more info
+--- a/test/segv.js
++++ b/test/segv.js
+@@ -37,9 +37,7 @@
+       , { 'id': 1,
+           'ok': false,
+           'name': ' ././segv',
+-          'exit': null,
+           'timedOut': true,
+-          'signal': process.platform === 'linux' ? 'SIGSEGV' : 'SIGTERM',
+           'command': '"./segv"' }
+       , 'tests 1'
+       , 'fail  1' ]
+@@ -47,11 +45,6 @@
+   tc.on('data', function (d) {
+     var e = expect.shift()
+ 
+-    // specific signal can be either term or bus
+-    if (d.signal && e.signal)
+-      e.signal = d.signal === "SIGTERM" || d.signal === "SIGBUS" ?
+-        d.signal : e.signal
+-
+     t.same(d, e)
+   })
+   tc.on('end', function () {
diff -Nru node-tap-0.4.13/debian/patches/series 
node-tap-0.4.13/debian/patches/series
--- node-tap-0.4.13/debian/patches/series       2014-10-20 00:01:40.000000000 
+0000
+++ node-tap-0.4.13/debian/patches/series       2015-02-16 22:53:00.000000000 
+0000
@@ -1,3 +1,4 @@
 nodejs_rename.patch
 use_available_modules.patch
 sbuild_disable_tests.patch
+mitigate_test_segv.patch

unblock node-tap/0.4.13-2

-- System Information:
Debian Release: 8.0
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 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 ---
Le 2015-02-17 00:07, Andrew Kelley a écrit :
Package: release.debian.org
Severity: normal
User: [email protected]
Usertags: unblock

Please unblock package node-tap

The bug that caused this package to be scheduled for autoremoval is
fixed with this small patch which disables a single test.


Unblocked.

Thanks for your work!

P.S.: This will also close 778568 as well.

Regards,

--
Mehdi

--- End Message ---

Reply via email to