[Pkg-javascript-devel] Bug#881882: libuv1-dev: [hurd-i386] undefined references to uv__io_poll et al.

2017-11-15 Thread Aaron M. Ucko 
Package: libuv1-dev
Version: 1.11.0-2
Severity: important
Tags: upstream
User: debian-h...@lists.debian.org
Usertags: hurd-i386
Control: affects -1 src:libstorj

The build of libstorj for hurd-i386 (admittedly not a release
architecture) failed because libuv had undefined references to symbols
it should have defined internally:

/usr/lib/i386-gnu/libuv.so: undefined reference to `uv__io_check_fd'
/usr/lib/i386-gnu/libuv.so: undefined reference to `uv__platform_loop_delete'
/usr/lib/i386-gnu/libuv.so: undefined reference to `uv__hrtime'
/usr/lib/i386-gnu/libuv.so: undefined reference to `uv__platform_invalidate_fd'
/usr/lib/i386-gnu/libuv.so: undefined reference to `uv__io_poll'
/usr/lib/i386-gnu/libuv.so: undefined reference to `uv__platform_loop_init'
/usr/lib/i386-gnu/libuv.so: undefined reference to `uv__fs_event_close'

Could you please take a look?

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

-- 
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#855259: nodejs: FTBFS on alpha architecture

2017-08-29 Thread Aaron M. Ucko 
Source: nodejs
Version: 6.11.2~dfsg-3
Followup-For: Bug #855259

FTR, I'm seeing inappropriate use of the flags -m32, -msse2,
-mfpmath=sse, and -mmmx by the embedded copy of libv8 on alpha, hppa,
and sparc64.  None of these are release architectures, and if
supporting them is infeasible, so be it.  However, in that case, I
would encourage you to restrict nodejs's Architecture field so that
these architectures' autobuilders don't bother trying to build nodejs
or even install its build dependencies.

For that matter, per Policy 4.13, you really ought to use a separately
packaged build of libv8 if at all possible.  However, I see that the
latest packaged version is pretty old -- 3.14.5.8 vs. nodejs's
embedded 5.1.281.

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

-- 
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#873652: nodejs: FTBFS on non-Linux: 'NativeHandle' does not name a type

2017-08-29 Thread Aaron M. Ucko 
Source: nodejs
Version: 6.11.2~dfsg-3
Severity: important
Tags: upstream
Justification: fails to build from source (but built successfully in the past)

Builds of nodejs for kFreeBSD and the Hurd (admittedly not release
architectures) have been failing:

  ../deps/v8/src/base/platform/mutex.h:62:3: error: 'NativeHandle' does not 
name a type
 NativeHandle& native_handle() {

Could you please take a look and ensure that the build system
recognizes both OSes as POSIX-compliant?

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

-- 
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#787751: libuv1: FTBFS - tests fail (mainly pipe_set_non_blocking)

2015-06-04 Thread Aaron M. Ucko 
Source: libuv1
Version: 1.4.2-1
Severity: serious
Justification: fails to build from source

The automated builds of libuv1 all failed with test suite errors.
For some reason, pipe_set_non_blocking failed everywhere:

  `pipe_set_non_blocking` failed: exit code 6
  Output from process `pipe_set_non_blocking`:
  Assertion failed in test/test-pipe-set-non-blocking.c on line 51: n == 0

In addition, loop_configure failed with no explanation on mips and mipsel:

  `loop_configure` failed: exit code 6
  Output from process `loop_configure`: (no output)

Worse yet, most tests failed on arm64, in many cases reporting
timeouts:

https://buildd.debian.org/status/fetch.php?pkg=libuv1&arch=arm64&ver=1.4.2-1&stamp=1433425729

Could you please take a look?

Thanks!

___
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#722284: Bug#722284: libuv: FTBFS on non-Linux: unknown type name 'pthread_rwlock_t'

2013-10-09 Thread Aaron M. Ucko 
Luca BRUNO  writes:

> * hurd port is not done. rust, nodejs and julia (main libuv clients)
>   won't build there, so I've put this at low priority.

That's fair, particularly considering that the Hurd hasn't qualified as
a release architecture.  Thanks for looking into kFreeBSD support, and
for remaining open to patches for Hurd support!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

___
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#722284: libuv: FTBFS on non-Linux: unknown type name 'pthread_rwlock_t'

2013-09-09 Thread Aaron M. Ucko 
Source: libuv
Version: 0.10.8-0~exp2
Severity: important
Justification: fails to build from source

Builds of libuv on kFreeBSD and the Hurd have been failing:

  In file included from /.../libuv-0.10.8/include/uv.h:67:0,
   from src/unix/async.c:25:
  /.../libuv-0.10.8/include/uv-private/uv-unix.h:131:1:
  error: unknown type name 'pthread_rwlock_t'
   typedef pthread_rwlock_t uv_rwlock_t;
   ^

It looks like the immediate problem is that config-unix.mk supplies
-D_GNU_SOURCE only on Linux, but I suspect further changes may be
necessary.  If porting proves infeasible, you can officially declare
Architecture: linux-any so that other architectures' autobuilders know
to leave the package alone.

Could you please take a look?

Thanks!

___
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#722283: libuv: FTBFS with test suite errors

2013-09-09 Thread Aaron M. Ucko 
Source: libuv
Version: 0.10.8-0~exp2
Severity: serious
Justification: fails to build from source

Automated builds of libuv on Linux failed with test suite errors.
(Builds for other platforms didn't even compile; I'll report that
separately.)  To wit:

* test-tty fails because automated builds don't bother allocating
  ttys.  Please try arranging to run the test suite under script(1):

   LD_PRELOAD=$(CURDIR)/libuv.so script -q -c "./run-tests" /dev/null

* Most of the udp tests fail.  I'm not sure why, but suspect a quirk
  of the autobuilders' configuration, which might require disabling
  those tests altogether. :-/

Could you please take a look?  You can find the full logs at
https://buildd.debian.org/status/logs.php?pkg=libuv&ver=0.10.8-0~exp2

Thanks!

___
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#686894: npm: please run under nodejs, not node

2012-09-06 Thread Aaron M. Ucko 
"Aaron M. Ucko"  writes:

> lines in /usr/bin/node and /usr/share/npm/bin/npm-cli.js to

That first should have been /usr/bin/npm, of course.

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

___
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#686901: node-tilelive: please run under nodejs, not node

2012-09-06 Thread Aaron M. Ucko 
Package: node-tilelive
Version: 4.2.1-3
Severity: grave
Justification: renders package unusable (uninstallable)

As you may have heard, nodejs's main executable is now /usr/bin/nodejs
rather than /usr/bin/node to avoid clashing with the unrelated "node"
package.  To accommodate that change, please update the

#!/usr/bin/env node

lines in /usr/bin/tilelive and /usr/bin/tilelive-copy

#!/usr/bin/env nodejs

or better yet

#!/usr/bin/nodejs

and version node-tilelive's dependency on nodejs to (>= 0.6.19~dfsg-1-3~).

Thanks!

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (300, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-3-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

___
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#686900: node-mbtiles: please run under nodejs, not node

2012-09-06 Thread Aaron M. Ucko 
Package: node-mbtiles
Version: 0.2.3-1
Severity: grave
Justification: renders package unusable (uninstallable)

As you may have heard, nodejs's main executable is now /usr/bin/nodejs
rather than /usr/bin/node to avoid clashing with the unrelated "node"
package.  To accommodate that change, please update /usr/bin/mb*'s

#!/usr/bin/env node

lines to

#!/usr/bin/env nodejs

or better yet

#!/usr/bin/nodejs

and version node-mbtiles's dependency on nodejs to (>= 0.6.19~dfsg-1-3~).

Thanks!

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (300, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-3-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

___
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#686899: node-mapnik: please run under nodejs, not node

2012-09-06 Thread Aaron M. Ucko 
Package: node-mapnik
Version: 0.6.7-2
Severity: grave
Justification: renders package unusable (uninstallable)

As you may have heard, nodejs's main executable is now /usr/bin/nodejs
rather than /usr/bin/node to avoid clashing with the unrelated "node"
package.  To accommodate that change, please update the

#!/usr/bin/env node

lines in /usr/bin/mapnik-inspect and /usr/bin/mapnik-render to

#!/usr/bin/env nodejs

or better yet

#!/usr/bin/nodejs

and version node-mapnik's dependency on nodejs to (>= 0.6.19~dfsg-1-3~).

Thanks!

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (300, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-3-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

___
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#686898: node-get: please run node-get-file.js under nodejs, not node

2012-09-06 Thread Aaron M. Ucko 
Package: node-get
Version: 1.1.5+ds1-1
Severity: grave
Justification: renders package unusable (uninstallable)

As you may have heard, nodejs's main executable is now /usr/bin/nodejs
rather than /usr/bin/node to avoid clashing with the unrelated "node"
package.  To accommodate that change, please update the

#!/usr/bin/env node

line in /usr/share/doc/node-get/examples/node-get-file.js to

#!/usr/bin/env nodejs

or better yet

#!/usr/bin/nodejs

and version node-get's dependency on nodejs to (>= 0.6.19~dfsg-1-3~).

Thanks!

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (300, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-3-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

___
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#686897: carto: please run under nodejs, not node

2012-09-06 Thread Aaron M. Ucko 
Package: carto
Version: 0.4.6+ds1-1
Severity: grave
Justification: renders package unusable (uninstallable)

As you may have heard, nodejs's main executable is now /usr/bin/nodejs
rather than /usr/bin/node to avoid clashing with the unrelated "node"
package.  To accommodate that change, please update the

#!/usr/bin/env node

lines in /usr/bin/carto and /usr/bin/mml2json to

#!/usr/bin/env nodejs

or better yet

#!/usr/bin/nodejs

and version carto's dependency on nodejs to (>= 0.6.19~dfsg-1-3~).

Thanks!

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (300, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-3-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

___
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#686896: buddycloud-server: please run under nodejs, not node

2012-09-06 Thread Aaron M. Ucko 
Package: buddycloud-server
Version: 0.3.1-1
Severity: grave
Justification: renders package unusable (uninstallable)

As you may have heard, nodejs's main executable is now /usr/bin/nodejs
rather than /usr/bin/node to avoid clashing with the unrelated "node"
package.  To accommodate that change, please update the

exec env node /usr/share/buddycloud-server/main.js $@

line in /usr/sbin/buddycloud-server to

exec nodejs /usr/share/buddycloud-server/main.js "$@"

(I made two other formal improvements there: env is redundant in this
context, and $@ works properly only when quoted.)

Also, please version buddycloud-server's dependency on nodejs to
(>= 0.6.19~dfsg-1-3~) to ensure that a nodejs executable will exist.

Thanks!

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (300, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-3-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

___
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#686894: npm: please run under nodejs, not node

2012-09-06 Thread Aaron M. Ucko 
Package: npm
Version: 1.1.4~dfsg-1
Severity: grave
Justification: renders package unusable

As you may have heard, nodejs's main executable is now /usr/bin/nodejs
rather than /usr/bin/node to avoid clashing with the unrelated "node"
package.  To accommodate that change, please update the

#!/usr/bin/env node

lines in /usr/bin/node and /usr/share/npm/bin/npm-cli.js to

#!/usr/bin/env nodejs

or better yet

#!/usr/bin/nodejs

and version npm's dependency on nodejs to (>= 0.6.19~dfsg-1-3~).  I'd
suggest additionally updating the .../bin/node references in
/usr/share/npm/doc/cli/folders.md and
/usr/share/doc/npm/doc/folders.html, but that's less critical.

Thanks!

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (300, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-3-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

Versions of packages npm depends on:
ii  node-abbrev   1.0.3-1
ii  node-fstream  0.1.13-1
ii  node-graceful-fs  1.1.8-1
ii  node-ini  1.0.2-1
ii  node-minimatch0.2.0-1
ii  node-mkdirp   0.3.1-2
ii  node-node-uuid1.3.3-1
ii  node-nopt 1.0.10-2
ii  node-request  2.9.153-1
ii  node-rimraf   2.0.1-1
ii  node-semver   1.0.13-1
ii  node-tar  0.1.13-1
ii  node-which1.0.5-1
ii  nodejs0.6.19~dfsg1-2
ii  nodejs-dev0.6.19~dfsg1-2

npm recommends no packages.

npm 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#686893: node-vows: please run under nodejs, not node

2012-09-06 Thread Aaron M. Ucko 
Package: node-vows
Version: 0.6.3-1
Severity: grave
Justification: renders package unusable (uninstallable)

As you may have heard, nodejs's main executable is now /usr/bin/nodejs
rather than /usr/bin/node to avoid clashing with the unrelated "node"
package.  To accommodate that change, please update /usr/bin/vows's

#!/usr/bin/env node

line to

#!/usr/bin/env nodejs

or better yet

#!/usr/bin/nodejs

and version node-vows's dependency on nodejs to (>= 0.6.19~dfsg-1-3~).

Thanks!

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (300, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-3-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

Versions of packages node-vows depends on:
ii  node-eyes  0.1.7-1
ii  nodejs 0.6.19~dfsg1-2

Versions of packages node-vows recommends:
ii  coffeescript  1.3.3-1

node-vows 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#686892: node-optimist: please run examples under nodejs, not node

2012-09-06 Thread Aaron M. Ucko 
Package: node-optimist
Version: 0.3.1-1
Severity: grave
Justification: renders package unusable (uninstallable)

As you may have heard, nodejs's main executable is now /usr/bin/nodejs
rather than /usr/bin/node to avoid clashing with the unrelated "node"
package.  To accommodate that change, please update the

#!/usr/bin/env node

lines in /usr/share/doc/node-optimist/examples/*.js to

#!/usr/bin/env nodejs

or better yet

#!/usr/bin/nodejs

and version node-optimist's dependency on nodejs to (>= 0.6.19~dfsg-1-3~).

Thanks!

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (300, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-3-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

Versions of packages node-optimist depends on:
ii  node-wordwrap  0.0.2-2
ii  nodejs 0.6.19~dfsg1-2

node-optimist recommends no packages.

node-optimist 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#686891: node-jake: please run under nodejs, not node

2012-09-06 Thread Aaron M. Ucko 
Package: node-jake
Version: 0.2.32-1
Severity: grave
Justification: renders package unusable (uninstallable)

As you may have heard, nodejs's main executable is now /usr/bin/nodejs
rather than /usr/bin/node to avoid clashing with the unrelated "node"
package.  To accommodate that change, please update /usr/bin/jake's

#!/usr/bin/env node

line to

#!/usr/bin/env nodejs

or better yet

#!/usr/bin/nodejs

and version node-jake's dependency on nodejs to (>= 0.6.19~dfsg-1-3~).

Thanks!

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (300, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-3-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

Versions of packages node-jake depends on:
ii  nodejs  0.6.19~dfsg1-2

Versions of packages node-jake recommends:
ii  coffeescript  1.3.3-1
ii  node-glob 3.1.9-1

node-jake 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#686890: node-express: please run under nodejs, not node

2012-09-06 Thread Aaron M. Ucko 
Package: node-express
Version: 2.5.9-1
Severity: grave
Justification: renders package unusable (uninstallable)

As you may have heard, nodejs's main executable is now /usr/bin/nodejs
rather than /usr/bin/node to avoid clashing with the unrelated "node"
package.  To accommodate that change, please update /usr/bin/express's

#!/usr/bin/env node

line to

#!/usr/bin/env nodejs

or better yet

#!/usr/bin/nodejs

and version node-express's dependency on nodejs to (>= 0.6.19~dfsg-1-3~).

Thanks!

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (300, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-3-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

Versions of packages node-express depends on:
ii  node-connect  1.7.3-1
ii  node-mime 1.2.5-1
ii  node-mkdirp   0.3.1-2
ii  node-qs   0.4.2-1
ii  nodejs0.6.19~dfsg1-2

node-express recommends no packages.

node-express 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#686889: node-cli: please update examples to run nodejs, not node

2012-09-06 Thread Aaron M. Ucko 
Package: node-cli
Version: 0.4.2~20120411-1
Severity: grave
Justification: renders package unusable (uninstallable)

As you may have heard, nodejs's main executable is now /usr/bin/nodejs
rather than /usr/bin/node to avoid clashing with the unrelated "node"
package.  To accommodate that change, please update the

#!/usr/bin/env node

lines in /usr/share/doc/node-cli/examples/*.js to

#!/usr/bin/env nodejs

or better yet

#!/usr/bin/nodejs

and version node-cli's dependency on nodejs to (>= 0.6.19~dfsg-1-3~).

Thanks!

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (300, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-3-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

Versions of packages node-cli depends on:
ii  nodejs  0.6.19~dfsg1-2

node-cli recommends no packages.

node-cli 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#686883: node-bones: please run nodejs, not node (in simple example)

2012-09-06 Thread Aaron M. Ucko 
Package: node-bones
Version: 2.0.1+ds1-1
Severity: grave
Justification: renders package unusable (uninstallable)

As you may have heard, nodejs's main executable is now /usr/bin/nodejs
rather than /usr/bin/node to avoid clashing with the unrelated "node"
package.  To accommodate that change, please update the

#!/usr/bin/env node

line in /usr/share/doc/node-bones/examples/simple/index.js to

#!/usr/bin/env nodejs

or better yet

#!/usr/bin/nodejs

and version node-bones's dependency on nodejs to (>= 0.6.19~dfsg-1-3~).

Thanks!

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (300, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-3-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

Versions of packages node-bones depends on:
ii  libjs-backbone   0.5.3-2
ii  node-express 2.5.9-1
ii  node-jquery  1.6.3-1
ii  node-mirror  0.3.3-2
ii  node-optimist0.3.1-1
ii  node-underscore  1.3.3-1
ii  nodejs   0.6.19~dfsg1-2

node-bones recommends no packages.

node-bones 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#650552: Bug#650552: Bug#650552: node-expat: FTBFS: EBADF, Bad file descriptor '/usr/lib/package.json'

2012-04-27 Thread Aaron M. Ucko 
Jonas Smedegaard  writes:

> Indeed.  Most likely a different bug, though.

True; I'll file a separate report.

> Both build attempts occured in february. Since then 6 newer releases of 
> Nodejs have been released, some of which (if not all, when considering 
> the underlying changes to libv8) has ARM-specific changes.

AFAICT, the build attempts occurred just a couple of weeks ago, using an
sbuild version from February.

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu



___
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#670678: node-expat: FTBFS on ARM: tests time out

2012-04-27 Thread Aaron M. Ucko 
Source: node-expat
Version: 1.5.0-1
Severity: serious
Justification: fails to build from source

Builds of node-expat on armel and armhf have both been failing with
test suite timeouts:

NODE_PATH=/.../node-expat-1.5.0/debian/node-node-expat//usr/lib/nodejs node 
test.js

timers.js:96
if (!process.listeners('uncaughtException').length) throw e;
  ^
mRuntime within maximum expected timem
at [object Object]. (/.../node-expat-1.5.0/test.js:243:14)
at [object Object]. (events.js:67:17)
at [object Object].emit (/usr/lib/nodejs/vows.js:236:24)
at [object Object].emit (/.../node-expat-1.5.0/lib/node-expat.js:18:12)
at [object Object].resume (/.../node-expat-1.5.0/lib/node-expat.js:41:24)
at Object._onTimeout (/.../node-expat-1.5.0/test.js:226:6)
at Timer.ontimeout (timers.js:94:19)
make: *** [build/node-node-expat] Error 1
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2

Could you please take a look?

Thanks!



___
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#650552: Bug#650552: node-expat: FTBFS: EBADF, Bad file descriptor '/usr/lib/package.json'

2012-04-27 Thread Aaron M. Ucko 
Jonas Smedegaard  writes:

> The package evidently builds fine now.

Yes, this failure mode is gone, thanks.  It looks like the armel and
armhf builds are running into test suite timeouts, though:

https://buildd.debian.org/status/fetch.php?pkg=node-expat&arch=armel&ver=1.5.0-1&stamp=1334337481
https://buildd.debian.org/status/fetch.php?pkg=node-expat&arch=armhf&ver=1.5.0-1&stamp=1334337523

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu



___
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#650552: Bug#650552: Bug#650552: Bug#650552: node-expat: FTBFS: EBADF, Bad file descriptor '/usr/lib/package.json'

2011-12-04 Thread Aaron M. Ucko 
Jonas Smedegaard  writes:

> node: symbol lookup error: 
> /tmp/buildd/node-expat-1.4.1/build/default/node-expat.node: undefined symbol: 
> _ZNK2v86String10WriteAsciiEPciii

FWIW, that demangles to v8::String::WriteAscii(char*, int, int, int) const.
No idea why it would suddenly go missing, though.

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu



___
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#650552: Bug#650552: node-expat: FTBFS: EBADF, Bad file descriptor '/usr/lib/package.json'

2011-12-04 Thread Aaron M. Ucko 
Jonas Smedegaard  writes:

> Not sure if the proper approach is to reasign or file another bug and 
> make one of them affect the other - and since I maintain both packages I 
> will simply spend my time on fixing the issue instead :-)

Commendably practical; thanks for the prompt fix. :-)  It looks like you
may need to nudge the buildd maintainers, though; I'm not one myself,
just a regular DD who keeps tabs on packages showing up on amd64 but not
i386 or vice versa.

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu



___
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#650552: node-expat: FTBFS: EBADF, Bad file descriptor '/usr/lib/package.json'

2011-11-30 Thread Aaron M. Ucko 
Source: node-expat
Version: 1.4.1-1
Severity: serious
Justification: fails to build from source

The automated build of node-expat on i386 (the only platform besides
amd64 for which its build dependencies are available) failed with a
test suite error:

  NODE_PATH=/.../node-expat-1.4.1/debian/node-node-expat//usr/lib/nodejs node 
test.js
  
  node.js:134
  throw e; // process.nextTick error, or 'error' event on first tick
^
  Error: EBADF, Bad file descriptor '/usr/lib/package.json'
  at Object.openSync (fs.js:221:18)
  at Object.readFileSync (fs.js:112:15)
  at Object. (/usr/lib/nodejs/vows.js:254:28)
  at Module._compile (module.js:411:26)
  at Object..js (module.js:417:10)
  at Module.load (module.js:343:31)
  at Function._load (module.js:302:12)
  at require (module.js:355:19)
  at Object. (/.../node-expat-1.4.1/test.js:4:12)
  at Module._compile (module.js:411:26)
  make: *** [build/node-node-expat] Error 1
  dpkg-buildpackage: error: debian/rules build gave error exit status 2

I don't have time to dig too deeply, but see that the npm package
ships a package.json (under /usr/share/npm); a build dependency on
it may be in order.  At any rate, could you please take a look?

Thanks!



___
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#650548: libv8: FTBFS on armel: unrecognized option -m32

2011-11-30 Thread Aaron M. Ucko 
Package: libv8
Version: 3.5.10.24-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Builds of libv8 on armel are now failing because its build system
insists for some reason on passing the unsupported -m32 flag:

  make[2]: Entering directory `/.../libv8-3.5.10.24/out'
g++ '-DENABLE_DEBUGGER_SUPPORT' '-DV8_TARGET_ARCH_ARM' 
'-DCAN_USE_VFP_INSTRUCTIONS' '-DUSE_EABI_HARDFLOAT=0' -I../src -Wall -Werror -W 
-Wno-unused-parameter -Wnon-virtual-dtor -pthread -fno-rtti -fno-exceptions 
-pedantic -m32 -ansi -fvisibility=hidden -fPIC -fdata-sections 
-ffunction-sections -fomit-frame-pointer -O3  -MMD -MF 
/.../libv8-3.5.10.24/out/arm.release/.deps//.../libv8-3.5.10.24/out/arm.release/obj.target/preparser_lib/src/allocation.o.d.raw
 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security 
-Werror=format-security -Wall -Wno-psabi -c -o 
/.../libv8-3.5.10.24/out/arm.release/obj.target/preparser_lib/src/allocation.o 
../src/allocation.cc
  cc1plus: error: unrecognized command line option '-m32'
  make[2]: *** 
[/.../libv8-3.5.10.24/out/arm.release/obj.target/preparser_lib/src/allocation.o]
 Error 1
  make[1]: *** [arm.release] Error 2
  make: *** [debian/stamp-makefile-build] Error 2
  dpkg-buildpackage: error: debian/rules build gave error exit status 2

(Incidentally, the -MF option's argument looks bogus as well; GCC
doesn't appear to care about that at the moment, though.)

Could you please take a look?

Thanks!



___
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#650549: libv8: FTBS on mipsel: no rule to make target mips.release

2011-11-30 Thread Aaron M. Ucko 
Package: libv8
Version: 3.5.10.24-1
Severity: serious
Justification: fails to build from source

Builds of libv8 on mipsel are now failing due to what appears to be a
gap in upstream's build system:

  /usr/bin/make  -C . CFLAGS="-g -O2 -Wformat -Wformat-security 
-Werror=format-security -Wall" CXXFLAGS="-g -O2 -Wformat -Wformat-security 
-Werror=format-security -Wall" CPPFLAGS="" LDFLAGS="" -j2 library=shared 
soname_version=3.5.10.24 OS=linux V=1 mips.release
  make[1]: *** No rule to make target `mips.release'.  Stop.
  make[1]: Entering directory `/.../libv8-3.5.10.24'
  make[1]: Leaving  directory `/.../libv8-3.5.10.24'
  make: *** [debian/stamp-makefile-build] Error 2

Could you please take a look?

Thanks!



___
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#650547: libv8: FTBFS on i386: unused variable in lithium-codegen-ia32.cc

2011-11-30 Thread Aaron M. Ucko 
Source: libv8
Version: 3.5.10.24-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

The latest libv8 upload fails to build on i386:

  ../src/ia32/lithium-codegen-ia32.cc:3178:12: error: variable 'key' set but 
not used [-Werror=unused-but-set-variable]
  cc1plus: all warnings being treated as errors
  
  make[2]: *** 
[/build/buildd-libv8_3.5.10.24-1-i386-CPx3sU/libv8-3.5.10.24/out/ia32.release/obj.target/v8_base/src/ia32/lithium-codegen-ia32.o]
 Error 1

Could you please take a look, and reconsider your use of -Werror in
official uploads (which become fragile as a result)?

Thanks!



___
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel