[Pkg-javascript-devel] Bug#672388: Bug#672388: npm: completion in Zsh causes error message regarding missing /usr/share/npm/lib/utils/completion.sh
* Jonas Smedegaard [Thu May 10, 2012 at 09:31:22PM +0200]:
On 12-05-10 at 06:27pm, Michael Prokop wrote:
I'm using Zsh:
% zsh --version
zsh 4.3.17 (x86_64-unknown-linux-gnu)
which provides a completion in its package
(/usr/share/zsh/functions/Completion/Unix/_npm), but
there seems to be something fishy in the npm package.
What makes you decide that the fishy part is in npm when zsh provided
that /usr/share/zsh/functions/Completion/Unix/_npm file?
I could easily imagine that zsh had put something together that assumed
npm was installed outside of the system, i.e. below either $home or
/usr/local - which obviously isn't the case for Debian-packaged npm.
Or did I misunderstand something?
Well, Zsh's completion file is as simple as that:
| % cat /usr/share/zsh/functions/Completion/Unix/_npm
| #compdef npm
|
| # Node Package Manager 0.3.15 completion, letting npm do all the completion
work
|
| _npm() {
| compadd -- $(_npm_complete $words)
| }
|
| # We want to show all errors of any substance, but never the npm (not )ok
one.
| # (Also doesn't consider ERR! no match found worth breaking the terminal
for.)
| _npm_complete() {
| local ask_npm
| ask_npm=(npm completion --color false --loglevel error -- $@)
| { _call_program npm $ask_npm 21 3 \
| | egrep -v '^(npm (not |)ok|ERR! no match found)$' 2; \
| } 31
| }
|
| _npm $@
And running the npm completion command even without any further
arguments fails (in Zsh and Bash):
| % npm completion
|
| npm ERR! Error: ENOENT, open '/usr/share/npm/lib/utils/completion.sh'
| npm ERR! You may report this log at:
| npm ERR! http://bugs.debian.org/npm
| npm ERR! or use
| npm ERR! reportbug --attach /home/mika/npm-debug.log npm
| npm ERR!
| npm ERR! System Linux 3.2.0-1-grml-amd64
| npm ERR! command node /usr/bin/npm completion
| npm ERR! cwd /home/mika
| npm ERR! node -v v0.6.17
| npm ERR! npm -v 1.1.4
| npm ERR! path /usr/share/npm/lib/utils/completion.sh
| npm ERR! code ENOENT
| npm ERR! message ENOENT, open '/usr/share/npm/lib/utils/completion.sh'
| npm ERR! errno {}
| npm ERR!
| npm ERR! Additional logging details can be found in:
| npm ERR! /home/mika/npm-debug.log
| npm not ok
So from my POV the completion command of npm is broken in the Debian
package.
regards,
-mika-
signature.asc
Description: Digital signature
___
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#672388: Bug#672388: npm: completion in Zsh causes error message regarding missing /usr/share/npm/lib/utils/completion.sh
On 12-05-11 at 11:47am, Michael Prokop wrote:
* Jonas Smedegaard [Thu May 10, 2012 at 09:31:22PM +0200]:
On 12-05-10 at 06:27pm, Michael Prokop wrote:
I'm using Zsh:
% zsh --version
zsh 4.3.17 (x86_64-unknown-linux-gnu)
which provides a completion in its package
(/usr/share/zsh/functions/Completion/Unix/_npm), but
there seems to be something fishy in the npm package.
What makes you decide that the fishy part is in npm when zsh
provided that /usr/share/zsh/functions/Completion/Unix/_npm file?
I could easily imagine that zsh had put something together that
assumed npm was installed outside of the system, i.e. below either
$home or /usr/local - which obviously isn't the case for
Debian-packaged npm.
Or did I misunderstand something?
Well, Zsh's completion file is as simple as that:
| % cat /usr/share/zsh/functions/Completion/Unix/_npm
| #compdef npm
|
| # Node Package Manager 0.3.15 completion, letting npm do all the completion
work
|
| _npm() {
| compadd -- $(_npm_complete $words)
| }
|
| # We want to show all errors of any substance, but never the npm (not )ok
one.
| # (Also doesn't consider ERR! no match found worth breaking the terminal
for.)
| _npm_complete() {
| local ask_npm
| ask_npm=(npm completion --color false --loglevel error -- $@)
| { _call_program npm $ask_npm 21 3 \
| | egrep -v '^(npm (not |)ok|ERR! no match found)$' 2; \
| } 31
| }
|
| _npm $@
And running the npm completion command even without any further
arguments fails (in Zsh and Bash):
| % npm completion
|
| npm ERR! Error: ENOENT, open '/usr/share/npm/lib/utils/completion.sh'
| npm ERR! You may report this log at:
| npm ERR! http://bugs.debian.org/npm
| npm ERR! or use
| npm ERR! reportbug --attach /home/mika/npm-debug.log npm
| npm ERR!
| npm ERR! System Linux 3.2.0-1-grml-amd64
| npm ERR! command node /usr/bin/npm completion
| npm ERR! cwd /home/mika
| npm ERR! node -v v0.6.17
| npm ERR! npm -v 1.1.4
| npm ERR! path /usr/share/npm/lib/utils/completion.sh
| npm ERR! code ENOENT
| npm ERR! message ENOENT, open '/usr/share/npm/lib/utils/completion.sh'
| npm ERR! errno {}
| npm ERR!
| npm ERR! Additional logging details can be found in:
| npm ERR! /home/mika/npm-debug.log
| npm not ok
So from my POV the completion command of npm is broken in the Debian
package.
Agreed. Thanks for the valuable details!
- Jonas
--
* Jonas Smedegaard - idealist Internet-arkitekt
* Tlf.: +45 40843136 Website: http://dr.jones.dk/
[x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: Digital signature
___
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] Please schedule binNMU for rdepends of libv8
On Sat, May 5, 2012 at 20:25:14 +0200, Tobias Frost wrote: Dear release team, to allow removal of old version of libv8 and allow transition of it to testing, please schedule a binnmu for its rdepends: drizzle osmium Done. What about chromium-browser's FTBFS on arm, and libv8-i18n? Somebody should talk to the v8 folks about ABI stability sometime. Cheers, Julien signature.asc Description: Digital signature ___ Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] Please schedule binNMU for rdepends of libv8
On 11/05/2012 19:10, Julien Cristau wrote: On Sat, May 5, 2012 at 20:25:14 +0200, Tobias Frost wrote: Dear release team, to allow removal of old version of libv8 and allow transition of it to testing, please schedule a binnmu for its rdepends: drizzle osmium Done. Thank you. What about chromium-browser's FTBFS on arm, and libv8-i18n? I'll update libv8-i18n. What's the relation with chromium FTBFS on arm (i guess you mean armel) ? Somebody should talk to the v8 folks about ABI stability sometime. I do... no success yet [1] I would very much like to use libv8-x.y instead of libv8-x.y.z. Some tool like [2] seems to indicate that for example, there is no ABI breakage risk between libv8-3.9.24.1 and libv8-3.9.24.21, as upstream explains it in [1] too. But, as was discussed on debian-devel [3], it's hard to certify without upstream supporting this. Also it takes an experimented c++ programmer to support that. I'm not. Jérémy. [1] https://groups.google.com/d/topic/v8-users/VJRmaQV-M3E/discussion [2] http://www.upstream-tracker.org/versions/v8.html [3] http://lists.debian.org/debian-devel/2012/01/msg00671.html ___ Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] Please schedule binNMU for rdepends of libv8
On Fri, May 11, 2012 at 20:07:35 +0200, Jérémy Lal wrote: What's the relation with chromium FTBFS on arm (i guess you mean armel) ? The current version of chromium-browser on arm$whichever depends on the old libv8. Cheers, Julien signature.asc Description: Digital signature ___ 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] Processing of libv8-i18n_0~0.svn7-2_amd64.changes
libv8-i18n_0~0.svn7-2_amd64.changes uploaded successfully to localhost along with the files: libv8-i18n_0~0.svn7-2.dsc libv8-i18n_0~0.svn7-2.debian.tar.gz libv8-i18n-dev_0~0.svn7-2_amd64.deb libv8-i18n0.0.0_0~0.svn7-2_amd64.deb libv8-i18n0.0.0-dbg_0~0.svn7-2_amd64.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) ___ 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] Hello Dear
How are you doing today, I hope every things is OK with you as it's my pleasure to contact you after viewing your email, although I was searching for life partner but I saw your email Address and I decided to have communication with you, if you will have the desire with me so that we can get to know each other better and see what will happen in future. Kindly write me back for easiest communication and to know all about each other OK, so that I will send you my pictures,as I wish you all the best for your day and I will be waiting to hear from you yours new friend, Alice. ___ 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] Processing of libv8-i18n_0~0.svn7-2_amd64.changes
libv8-i18n_0~0.svn7-2_amd64.changes uploaded successfully to localhost along with the files: libv8-i18n_0~0.svn7-2.dsc libv8-i18n_0~0.svn7-2.debian.tar.gz libv8-i18n-dev_0~0.svn7-2_amd64.deb libv8-i18n0.0.0_0~0.svn7-2_amd64.deb libv8-i18n0.0.0-dbg_0~0.svn7-2_amd64.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) ___ 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] libv8-i18n_0~0.svn7-2_amd64.changes REJECTED
Reject Reasons: md5sum for /srv/ftp-master.debian.org/ftp/pool/main/libv/libv8-i18n/libv8-i18n_0~0.svn7.orig.tar.gz doesn't match libv8-i18n_0~0.svn7-2.dsc. size for /srv/ftp-master.debian.org/ftp/pool/main/libv/libv8-i18n/libv8-i18n_0~0.svn7.orig.tar.gz doesn't match libv8-i18n_0~0.svn7-2.dsc. === Please feel free to respond to this email if you don't understand why your files were rejected, or if you upload new files which address our concerns. ___ 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] Processing of libv8-i18n_0~0.svn7-2_amd64.changes
libv8-i18n_0~0.svn7-2_amd64.changes uploaded successfully to localhost along with the files: libv8-i18n_0~0.svn7-2.dsc libv8-i18n_0~0.svn7-2.debian.tar.gz libv8-i18n-dev_0~0.svn7-2_amd64.deb libv8-i18n0.0.0_0~0.svn7-2_amd64.deb libv8-i18n0.0.0-dbg_0~0.svn7-2_amd64.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) ___ 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] libv8-i18n_0~0.svn7-2_amd64.changes ACCEPTED into unstable
Accepted: libv8-i18n-dev_0~0.svn7-2_amd64.deb to main/libv/libv8-i18n/libv8-i18n-dev_0~0.svn7-2_amd64.deb libv8-i18n0.0.0-dbg_0~0.svn7-2_amd64.deb to main/libv/libv8-i18n/libv8-i18n0.0.0-dbg_0~0.svn7-2_amd64.deb libv8-i18n0.0.0_0~0.svn7-2_amd64.deb to main/libv/libv8-i18n/libv8-i18n0.0.0_0~0.svn7-2_amd64.deb libv8-i18n_0~0.svn7-2.debian.tar.gz to main/libv/libv8-i18n/libv8-i18n_0~0.svn7-2.debian.tar.gz libv8-i18n_0~0.svn7-2.dsc to main/libv/libv8-i18n/libv8-i18n_0~0.svn7-2.dsc Changes: libv8-i18n (0~0.svn7-2) unstable; urgency=low . * Rebuild against libv8-3.8.9.20 * Update symbols file - add external icu symbol. Override entries for your package: libv8-i18n-dev_0~0.svn7-2_amd64.deb - optional libdevel libv8-i18n0.0.0-dbg_0~0.svn7-2_amd64.deb - extra debug libv8-i18n0.0.0_0~0.svn7-2_amd64.deb - optional libs libv8-i18n_0~0.svn7-2.dsc - source libs Announcing to debian-devel-chan...@lists.debian.org Thank you for your contribution to Debian. ___ Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
