[Pkg-javascript-devel] Processing of node-nopt_1.0.10-2_i386.changes

2012-05-03 Thread Debian FTP Masters
node-nopt_1.0.10-2_i386.changes uploaded successfully to localhost
along with the files:
  node-nopt_1.0.10-2.dsc
  node-nopt_1.0.10-2.debian.tar.gz
  node-nopt_1.0.10-2_all.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] node-nopt_1.0.10-2_i386.changes ACCEPTED into unstable

2012-05-03 Thread Debian FTP Masters



Accepted:
node-nopt_1.0.10-2.debian.tar.gz
  to main/n/node-nopt/node-nopt_1.0.10-2.debian.tar.gz
node-nopt_1.0.10-2.dsc
  to main/n/node-nopt/node-nopt_1.0.10-2.dsc
node-nopt_1.0.10-2_all.deb
  to main/n/node-nopt/node-nopt_1.0.10-2_all.deb


Changes:
node-nopt (1.0.10-2) unstable; urgency=low
 .
  * Fix Homepage field in debian/control
  * Fix watch file.
  * Add dependency on node-abbrev. (Closes: #671256)


Override entries for your package:
node-nopt_1.0.10-2.dsc - source web
node-nopt_1.0.10-2_all.deb - extra web

Announcing to debian-devel-chan...@lists.debian.org
Closing bugs: 671256 


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


[Pkg-javascript-devel] Bug#671256: marked as done ([node-nopt] this package should depend on the node-abbrev)

2012-05-03 Thread Debian Bug Tracking System
Your message dated Thu, 03 May 2012 06:33:33 +
with message-id e1sppbz-0006lm...@franck.debian.org
and subject line Bug#671256: fixed in node-nopt 1.0.10-2
has caused the Debian Bug report #671256,
regarding [node-nopt] this package should depend on the node-abbrev
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 ow...@bugs.debian.org
immediately.)


-- 
671256: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671256
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: node-nopt
Version: 1.0.10-1
Severity: important

--- Please enter the report below this line. ---
This package should depend on the node-abbrev.
package.json contains appropriate info.
https://github.com/isaacs/nopt/blob/master/package.json#L12

--- System information. ---
Architecture: i386
Kernel:   Linux 3.3.0-trunk-686-pae

Debian Release: wheezy/sid
  500 unstableftp.by.debian.org
1 experimentalftp.by.debian.org

--- Package information. ---
Depends  (Version) | Installed
==-+-===
nodejs | 0.6.16~dfsg1-2


Package's Recommends field is empty.

Package's Suggests field is empty.


---End Message---
---BeginMessage---
Source: node-nopt
Source-Version: 1.0.10-2

We believe that the bug you reported is fixed in the latest version of
node-nopt, which is due to be installed in the Debian FTP archive:

node-nopt_1.0.10-2.debian.tar.gz
  to main/n/node-nopt/node-nopt_1.0.10-2.debian.tar.gz
node-nopt_1.0.10-2.dsc
  to main/n/node-nopt/node-nopt_1.0.10-2.dsc
node-nopt_1.0.10-2_all.deb
  to main/n/node-nopt/node-nopt_1.0.10-2_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 671...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jérémy Lal kapo...@melix.org (supplier of updated node-nopt package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Mon, 19 Mar 2012 15:36:14 +0100
Source: node-nopt
Binary: node-nopt
Architecture: source all
Version: 1.0.10-2
Distribution: unstable
Urgency: low
Maintainer: Debian Javascript Maintainers 
pkg-javascript-devel@lists.alioth.debian.org
Changed-By: Jérémy Lal kapo...@melix.org
Description: 
 node-nopt  - Command-line option parser for Node.js
Closes: 671256
Changes: 
 node-nopt (1.0.10-2) unstable; urgency=low
 .
   * Fix Homepage field in debian/control
   * Fix watch file.
   * Add dependency on node-abbrev. (Closes: #671256)
Checksums-Sha1: 
 2d7fd5d9e41b7f55b57d20740b50ea437859c887 1303 node-nopt_1.0.10-2.dsc
 d5f3f85f3a21ef17eb03805fb3032859b3852b79 2007 node-nopt_1.0.10-2.debian.tar.gz
 4554f410c0507905c45999f5c330afad3e95cbb6 10862 node-nopt_1.0.10-2_all.deb
Checksums-Sha256: 
 44316c71b090e68e60f476f4b8c0f9ab754cc470428c062fe7bdcb421d41e9f4 1303 
node-nopt_1.0.10-2.dsc
 d5d739151eb7b4673ac62910663508700be274a00073d8d5fbcfc8c9985b73e6 2007 
node-nopt_1.0.10-2.debian.tar.gz
 2df90e4826bdaf8f6437752291bd1811739e64afd0eb010ba3bcb59045b3f44e 10862 
node-nopt_1.0.10-2_all.deb
Files: 
 7a24192b52656a009ac401cd69aab63b 1303 web extra node-nopt_1.0.10-2.dsc
 2d0d5ad31c53fbf08eadf54082a28667 2007 web extra 
node-nopt_1.0.10-2.debian.tar.gz
 7240003abee3a4ab4c9b8ffaae0a4096 10862 web extra node-nopt_1.0.10-2_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAk+iJS0ACgkQ5qqQFxOSsXTaugCfaVhxJs8DhZxoIXvCrb+rzlHA
0O0AmgLOXV1BkJd8ULnjwC7y8OQfNMC3
=S+r3
-END PGP SIGNATURE-


---End Message---
___
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] Request for policy interpretation: procedure and possible outcomes for naming conflicts

2012-05-03 Thread Bill Allombert
On Wed, May 02, 2012 at 04:20:47PM -0500, Jonathan Nieder wrote:
 Bill Allombert wrote:
  On Wed, May 02, 2012 at 02:12:22PM -0500, Jonathan Nieder wrote:
 
Policy also states that different packages must not install commands
with different functionality with the same name.
 
  Such packages would have to Conflicts anyway, and gratuituous conflict
  must be avoided. This is not a waivable requiremrent.
 
 As a strawman example, here is what I was thinking of when I asked that:
 
  nodejs package adds a nodejs command which behaves exactly like node
  in Debian (this has already been done) and upstream (working on it).

IMHO, /usr/bin/node is much too generic a name to be in any package.

Cheers,
-- 
Bill. ballo...@debian.org

Imagine a large red swirl here. 

___
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] Request for policy interpretation: procedure and possible outcomes for naming conflicts

2012-05-03 Thread Jérémy Lal
On 03/05/2012 11:51, Bill Allombert wrote:
 On Wed, May 02, 2012 at 04:20:47PM -0500, Jonathan Nieder wrote:
 Bill Allombert wrote:
 On Wed, May 02, 2012 at 02:12:22PM -0500, Jonathan Nieder wrote:

   Policy also states that different packages must not install commands
   with different functionality with the same name.

 Such packages would have to Conflicts anyway, and gratuituous conflict
 must be avoided. This is not a waivable requiremrent.

 As a strawman example, here is what I was thinking of when I asked that:

  nodejs package adds a nodejs command which behaves exactly like node
  in Debian (this has already been done) and upstream (working on it).
 
 IMHO, /usr/bin/node is much too generic a name to be in any package.

Objection: a lot of very generic command names are in /usr/bin.

Jérémy.


___
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] Node.js and it's future in debian

2012-05-03 Thread David Ranch


Hello Gentlemen,

I thought I'd chime in since the linux-hams@vger list was added to the 
thread and give one Packet HAM's perspective.  Specifically, if one 
proposal is to rename the long existing /usr/sbin/node binary to 
/usr/sbin/axnode, why couldn't the new guy node.js binary be renamed 
to something like /usr/sbin/nodejs?  The later seems more of a 
reasonable proposal.


From my experience, many MANY Linux hams have customized scripts that 
startup some very elaborate HAM systems.  For many, these scripts 
weren't written by them and the changing of the node command could be 
very difficult for some.  The other aspect is if this change came into a 
package update that could impact production systems in VERY remote 
sites.  This could cause all kinds ugliness that can be easily avoided.


I can appreciate Debian's goal to keep things moving forward but I'd 
argue that a binary name of /usr/sbin/nodejs would be a lot more 
informative with the two additional characters than just calling it 
node (and disrupting a well known binary name for us Linux packet hams).


--David
KI6ZHD


On 05/02/2012 01:04 PM, Patrick Ouellette wrote:

On Wed, May 02, 2012 at 12:13:49PM -0500, Jonathan Nieder wrote:

Patrick Ouellette wrote:


Likewise I can argue the number of people with installed ham radio systems
is a good reason NOT to change the current situation.

You can, yes.  But how does that move things forward at all?

I never said it did.  Clearly both sides have valid reasons to
not change.  Equally clear to me is one side ignored policy
and created an issue to attempt to force a resolution they hope
will be in their favor rather than solve the issue first.


This is not supposed to be a popularity contest.  I mentioned the
large pile of scripts because _every one of them would have to be
changed_ to have a working system.  By contrast, there are two
configuration files mentioned so far that refer to /usr/sbin/node.

The scripts (on either side) could be changed with a scripted change.

If it is so simple to change the configuration files for the ham radio
users, why has not a Node.js person put forth code to do this and advocated
it on debian-hams and linux-hams? (The patch sent does not address
automatically updating anything)

I've discussed it with other ham radio operators.  They shudder at the
thought of changing the name because of the possible issues that will
come up.


[...]

If it were easy to get an exception, why has this not already happened?

Because you did not ask for one.  Instead you have been wasting time
arguing and defending against an opponent you seem to assume is not
going to care or listen to you.

The Node.js people apparently didn't ask for one either
pot - kettle - black

As for the last line, if I thought the opponent did not care or was
not going to listen I would not waste the time putting forth my
position.  Since it would seem that is where we are, I won't
continue to waste my time.

Here is my proposal:
Node.js people, put forth a reasonable and workable plan to allow
hundreds or thousands of ham radio users to transition from
/usr/sbin/node to /usr/sbin/axnode, including reliable shell scripts
to verify all the files on the system are identified and allowed to
be patched or manually modified.  You created the situation, you
provide the manpower to resolve it in the way you prefer.


Pat - NE4PO
--
To unsubscribe from this list: send the line unsubscribe linux-hams in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.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] Node.js and it's future in debian

2012-05-03 Thread Jonathan Nieder
Hi again,

Patrick Ouellette wrote:

 I completely agree, but apparently Node.js' upstream has changed the name 
 once previously (apparently from a similar problem) and while acknowledging
 the name is generic and a poor choice refuses to consider another change.
 (According to what I can tell from the Debian discussion.  I have not
 talked to Node.js upstream personally.)

The working title of Node.js was server for a few weeks, before
anyone was using it.  When I looked that up in order to understand
what the name node was about (in the spirit of [1]) I mentioned this
factoid without making the context sufficiently clear, and I'm sorry
about that[2].

To avoid banging heads against the wall too quickly: I think there are
two aspects that it would be productive to discuss:

 1. Which package should use the name node in the long term?  What
can we do to ensure that happens eventually?

(My answer is that I hope that neither uses the name node in
the long term.)

 2. What should be the state in Debian's upcoming wheezy release to
provide a smooth upgrade path and not surprise users too much?

(My answer is that configuration needs to be smoothly migrated:

 - ax25d.conf by the ax25-tools package
 - inetd configuration by the node package
 - other configuration by the sysadmin, after they are notified
   through a note in node's NEWS.Debian file (shown by
   apt-listchanges) and the release notes

I also would hope that wheezy can include a /usr/sbin/node file
that prints a message to help people notice they are still using
it and calls /usr/sbin/axnode, but that is still under discussion.

Likewise, the Node.js needs some migration to ensure scripts
installed by Debian packages and from outside use the new name.
I would hope that wheezy can include a /usr/bin/node synonym for
compatibility until usage of it fades away, but that is still
under discussion.)

If you disagree with the long-term goal or have ideas for a smoother
migration, that could be useful.

Hope that helps,
Jonathan

[1] http://wiki.debian.org/WhyTheName
[2] https://lists.debian.org/debian-devel/2011/11/msg00377.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] Node.js and it's future in debian

2012-05-03 Thread Gordon JC Pearc e

On 03/05/12 19:51, Jonathan Nieder wrote:
. Which package should use the name node in the long term?  What
  can we do to ensure that happens eventually?

  (My answer is that I hope that neither uses the name node in
  the long term.)

Exactly.  It's a stupidly common term, probably only slightly better 
than calling it program.


I don't buy into this idea that changing it will break all sorts of 
legacy scripts.  If they are that fragile and undocumented, *get rid of 
them*!  Undocumented fragile code is a liability.  Kill it now, under 
known circumstances, and fix it up properly.


--
Gordonjcp MM0YEQ

___
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] Becoming a Debian Maintainer - call for key signer(s)/advocate(s)

2012-05-03 Thread Emilien Klein
Hi team,

I've come to the point where I'd like to apply for Debian
Maintainership (DM, not [yet] DD).

I've been working with Julien Valroff jul...@debian.org on my first
package nautilus-image-manipulator who has agreed to advocate my
application.

My contributions so far [0]:
- Maintainer of 3 packages (1 of which being co-maintained with the
pkg-javascript team)
  * 7 uploads of nautilus-image-manipulator (1 more currently in progress)
  * 2 uploads of jquery-lazyload
- Done 1 NMU
- A 5th package in the works, currently searching for a mentor.

Miscellaneous stuff (a.k.a. willingness to learn and explore new things):
- Different areas of experimentation: 2 desktop applications (Python
and C), 2 libraries (Python and JavaScript). 1 web application (PHP).
- Use of different tools: own-maintained packages with Bazaar,
co-maintained packages with Git
- Given a Debian Packaging presentation at my local LUG [1], after
which I've motivated one of the participants to start making a
package, i.e. a potential new contributor to Debian. The package [2]
should soon be ready for presentation to potential mentors.

Upon becoming a Debian Maintainer, I plan to work with Julien to add
the DM-Upload-Allowed control field to the nautilus-image-manipulator
package, but I'd prefer to stay a bit longer in 'sponsorship mode
regarding the other packages (i.e. jquery-lazyload as far as you're
concerned). I'll gradually add that control field to the other
packages when some more uploads have been made, or when you and I feel
that the time is right for those packages.

I know I haven't yet done a lot of work inside the JS team, but I hope
some of you would be willing to:
- Sign my key 4096R/0A2368F0 of 2011-11-23, so that I have more than
one DD that has done it [3]. Maybe somebody already has done so when I
uploaded my first JS package (Jose Luis Rivas?)
- Maybe even advocate for my DM application [4]!

Please get in touch with me if you want to help me out with key
signing, or even advocating for me. Thanks!
   +Emilien

P.S.: Hmmm, I'm wondering now whether having met in person is a
prerequisite for key signing... If so, can I just meet with any Debian
developer around me, or how does this process go?

[0] http://qa.debian.org/developer.php?login=emilien%2Bdebian%40klein.st
[1] http://lug.project073.nl/wiki/debian-packaging/
[2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=663517
[3] http://wiki.debian.org/DebianMaintainer#step_1_:_Identification
[4] http://wiki.debian.org/DebianMaintainer#step_3_:_Advocation

___
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] tech-ctte: please help maintainers of packages with a node command to have a reasonable conversation

2012-05-03 Thread Jonathan Nieder
Steve Langasek wrote:

 Clint Byrum has nudged me about this (wearing his Ubuntu Server hat rather
 than his shiny new Debian Developer hat) and I've agreed to approach node.js
 upstream about a possible upstream rename.  I'll report back to the TC what
 I find out.

Best of luck.  You know they've been asked twice before (once for Fedora,
once for Debian), right?

I think an easier sell would be:

 - just adding a command upstream, not renaming.  That way, existing
   users are not heavily impacted.  Perhaps there could be a
   ./configure option to disable the node command for distros like
   Fedora (and Debian?) that want that.  If the reasons for renaming
   are as strong as I think they are, users would migrate to the new
   name without needing upstream to deprecate the old one right away.

 - someone other than Ryan doing the actual work.  There's a patch to 
   start with at http://bugs.debian.org/650343#103.  I imagine the
   proposed Fedora package could also be helpful to someone working
   on this.

Thanks,
Jonathan

___
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] tech-ctte: please help maintainers of packages with a node command to have a reasonable conversation

2012-05-03 Thread Jérémy Lal
On 03/05/2012 23:23, Jonathan Nieder wrote:
 Steve Langasek wrote:
 
 Clint Byrum has nudged me about this (wearing his Ubuntu Server hat rather
 than his shiny new Debian Developer hat) and I've agreed to approach node.js
 upstream about a possible upstream rename.  I'll report back to the TC what
 I find out.
../..
  - someone other than Ryan doing the actual work.  There's a patch to 
start with at http://bugs.debian.org/650343#103.  I imagine the
proposed Fedora package could also be helpful to someone working
on this.
../..

Please note that nowadays Node.js upstream contact is
Isaac Schlueter i...@izs.me
as explained in
https://groups.google.com/forum/?fromgroups#!topic/nodejs/hfajgpvGTLY

Jérémy.


___
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] tech-ctte: please help maintainers of packages with a node command to have a reasonable conversation

2012-05-03 Thread Steve Langasek
On Thu, May 03, 2012 at 04:23:21PM -0500, Jonathan Nieder wrote:
  Clint Byrum has nudged me about this (wearing his Ubuntu Server hat rather
  than his shiny new Debian Developer hat) and I've agreed to approach node.js
  upstream about a possible upstream rename.  I'll report back to the TC what
  I find out.

 Best of luck.  You know they've been asked twice before (once for Fedora,
 once for Debian), right?

No, didn't know that.  Were these requests public, or can you tell me what
the upstream response was?

 I think an easier sell would be:

  - just adding a command upstream, not renaming.

That's exactly what I'm proposing.

  - someone other than Ryan doing the actual work.  There's a patch to 
start with at http://bugs.debian.org/650343#103.  I imagine the
proposed Fedora package could also be helpful to someone working
on this.

Well, changing a filename should be trivial; should be no problem to feed
upstream a patch.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@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 My Dear

2012-05-03 Thread blessing aliyu
Hello My Dear
My name is Miss Blessing i saw your profile today and became intrested in you,i 
will also like to know you the more,and i want you to send an email to my email 
address so i can give you my picture for you to know whom i am.
Here is my email address, (blessingaliy...@yahoo.com)
I believe we can move from here,
i am sorry if i am embarrassing you
your loving girl
Blessing

blessingaliy...@yahoo.com

___
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] Node.js and it's future in debian

2012-05-03 Thread Hans-Peter F. Oeste
I thought I'd also chime in with one aspect that perhaps hasn't been
articulated.  This could have a huge impact in 'Health and Public Safety', a
place where many hams use the tools and the debian distribution as an
appliance.  The node and ax25 package is used worldwide providing
communications infrastructure that may people rely on in times of disaster
and emergency, be it a forwarding of medical information to gain insight to
people health problems to local floods or fires to events like Katrina.
Hams often provide the backbone to the communications for these events.

That they treat the Debian distribution as an appliance says that they trust
the distribution to not break down, and this is something to be proud of.
That they use it as an appliance should not be considered a stupidity,.
Consider how many of us nowadays make changes to the engine in their
vehicles themselves.  Not many, it's done by enthusiasts.  The package node
and its attendant  packages is an engine for many ham operators.  So please,
be very careful in your consideration in making changes. The ramifications
could affect you personally inadvertently.

If you are going to muck with it, please consider a phased in approach that
gives warning of potentially at least year, if not longer, so that warning
is give and propagated to the mentors that these ham operators use, so that
customizations can be 'fixed' and any migrations and mitigation is
flawlessly executed.  This may mean that you yourselves may be asked to help
troubleshoot issues/problems that arise.  Please be patient.

While I am a ham, I am also a mediocre programmer, so I can see both sides
of this argument.  In addition, I've used Linux longer than I've been a ham.

Hans Oeste
VE7OES


___
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] Node.js and it's future in debian

2012-05-03 Thread David Ranch


Me again..

AX.25 in Linux has been around for a long time so I can excuse it's 
overly generic node name purely based upon it's age but..




The working title of Node.js was server for a few weeks, before
anyone was using it.


Wow.. that's horrible!  Obviously we don't want stuff like that to 
happen.  Please also consider that all this ISN'T just a *Debian* 
problem.  Its a Linux distro-wide problem.  It's groups like this that 
form and guide aspects of all Linux distributions consistency and 
considering Debian's wide influence, changes here will surely trickle 
into other distributions over time.


It's also worth touching on that I personally appreciate the work that
Patrick Ouellette has done on maintaining the HAM packages for Debian. 
Like always, there are never enough appreciative people in this world 
but once removed / renamed /etc, I'm SURE a lot of people will come out 
of the woodwork to bitch about it.  A *lot* of people use Debian and 
Debian-related distributions with Packet radio.




  1. Which package should use the name node in the long term?  What
 can we do to ensure that happens eventually?

 (My answer is that I hope that neither uses the name node in
 the long term.)


I personally think that some of it SHOULD be a first come, first served 
thing.  I previously mentioned in the previous email that all of the 
various scripts that people run could/would break.  Probably no big deal 
to many of us on *this* list but trust me, I know a few Linux packet 
people who would be seriously lost because of these changes.


Also consider the tons of documentation, notably the AX.25 HOWTO that 
would be impacted and I highly doubt it would get updated (hasn't been 
since 2001) to reflect these changes.  It's not like things have needed 
to change all that much - http://tldp.org/HOWTO/AX25-HOWTO/




  2. What should be the state in Debian's upcoming wheezy release to
 provide a smooth upgrade path and not surprise users too much?


Is Node.js a new addition to Debian?  Again, I side with first come 
first served.




 I also would hope that wheezy can include a /usr/sbin/node file
 that prints a message to help people notice they are still using
 it and calls /usr/sbin/axnode, but that is still under discussion.

 Likewise, the Node.js needs some migration to ensure scripts
 installed by Debian packages and from outside use the new name.
 I would hope that wheezy can include a /usr/bin/node synonym for
 compatibility until usage of it fades away, but that is still
 under discussion.)


If for some reason Debian feels that longstanding packages and their 
well known binary names can be renamed at any given time (I seriously 
disagree with that mentality btw), I'd say then ALSO force the change of 
the node in Node.JS name to something more sane.  Don't remove one 
poorly named file for a new poorly named one just because it's new and 
shiny.


--David

___
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] Node.js and it's future in debian

2012-05-03 Thread Jonathan Nieder
David Ranch wrote:

 Is Node.js a new addition to Debian?  Again, I side with first come
 first served.

I think one of Debian's most important roles is to help various
dispersed projects to produce code that works well in combination.
Yes, Node.js is a relatively new addition to the world and Debian
(about 3 years old, not part of squeeze).

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