t;
The problem with these numbers is the architecture "all."
over 27% of files downloaded don't count since you don't know what
systems they are running on.
--
Patrick Ouellette <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
e the Debian
archives for "temporal release." Not much interest in it overall, and I
ran into time problems setting up the infrastructure to list which
packages would be in the "pre-stable" and "stable" branches (in your
terms).
I might return to that in the next
If you have sensitive skin you may wish to push the delete button now
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Thursday, April 30, 1998 8:27 AM
> To: [EMAIL PROTECTED]; debian-devel@lists.debian.org
> Subject: New Linux distribution
>
>
> Bruce,
Thanks for taking it as intended - and not the flame bait it might
have sounded like. (Rough night last night - but I did put the
delete disclaimer in)
I've been using hamm for some time, and as long as you check to be
sure that application you can't live without exists, it has been
fairly stable
I'll bite:
> From: Ian Keith Setford [mailto:[EMAIL PROTECTED]
> Sent: Thursday, April 30, 1998 3:09 PM
> To: debian-devel@lists.debian.org
> Subject: **Ready your Flame-Throwers**
>
>
>
> Yo-
>
> I am subscribed to devel although I am not a developer and since everyone
> else has had comments on
Sorry for the late reply - catching up.
IMHO speed is always relevant, and so is memory usage. This is the trap
Micro$oft
and Apple have fallen into. Just because the hardware is capable of running
faster
is no excuse for sloppy coding. I'm not saying everything should be written
in assembly
la
I have tossed around the idea of a ham specific configuration that
would fit on a zip disk. Not the fastest way to run the system,
but you could set up a swap and var/temp area on a small local
hard drive, use a ramdisk and have an easy way to upgrade the node.
I haven't thought about what softwa
I had similar problems with Windows NT and large drives on
2940UW controllers. The problem appeared to be the wide bus
mode setting ( I forget the exact wording in the adaptec setup).
If I changed the setting, the machine would not boot from the
drive until I either low level formatted the drive
ve been well
tested, and supportable. Stable no longer is a static concept, but a
slowly evolving thing. If you cannot wrap your mind around to accepting
a stable that evolves, we could snapshot stable at release data and make
a separate archive (really a Packages.gz and related files as long
On Fri, 2005-04-15 at 21:48 -0500, Adam M. wrote:
> Unfortunately this totally changes the purpose of "stable". Stable is
Yes and no. It changes the concept of stable in that stable evolves.
You still have the static release as long as we decide to keep that
version of all the packages in the pa
On Mon, Apr 18, 2005 at 07:37:40PM -0500, Gunnar Wolf wrote:
> Patrick Ouellette dijo [Sat, Apr 16, 2005 at 01:04:59AM -0400]:
> > (...)
> > Another difference is that testing will get new versions of packages and
> > those versions might (but should not) cause break
some - they are much more
> than hundred), and explain at which time of the future you expect
> every single package in the list to fulfill your criteria at the same
> time.
>
I will publish the results on my people.Debian.org page at
http://people.debian.org/~pouelle/temporal_rele
select which branch they use
based upon well know published criteria for the stability of that
particular branch. The user controls the amount of risk they are
willing to have in their system.
Testing, candidate and stable should change progressively slower. That
is the entire point.
Pat
--
Patrick Ouellette
[EMAIL PROTECTED]
[EMAIL PROTECTED]
Amateur Radio: KB8PYM
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
enting a bug free distribution, but about managing
the risks associated with the bugs that may be undetected at the time
the release is released. I believe a second stage between testing and
stable would allow better management of that risk, by providing an
almost frozen area where further
iod from testing to your proposed candidate and then stable would
> do nothing about normals bugs. RC bugs are usually found quite quickly
> by people using unstable.
If RC bugs are found so quickly in unstable, why has there been no
release in the last 3 or so years? Testing is normally quite usable.
That is part of the reason I believe this type of approach to releases
would work.
Pat
--
Patrick Ouellette
[EMAIL PROTECTED]
[EMAIL PROTECTED]
Amateur Radio: KB8PYM
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
;. Initially the ax25 package
name was kept, but later it was changed to "axlisten" and the (created
much later) audio player was allowed to keep the name.
Pat
--
Patrick Ouellette p...@flying-gecko.net
ne4po (at) arrl (dot) net Amateur Radio: NE4PO
What kind of change have you been in the world today?
signature.asc
Description: Digital signature
Actually, from the discussion in debian-hams, nodejs provides a binary
named "node" - otherwise we would not need to have the discussion at all
since there would be no conflict.
--
Patrick Ouellette p...@flying-gecko.net
ne4po (at) arrl (dot) net Amateur Radio: NE
On Tue, Sep 21, 2010 at 05:07:39PM +0200, Mehdi Dogguy wrote:
>
> On 21/09/2010 16:02, Patrick Ouellette wrote:
> > On Tue, Sep 21, 2010 at 03:54:41PM +0200, Mehdi Dogguy wrote:
> >>
> >> Wrong. nodejs still provides the binary nodejs and not _node_. So,
> >
gt; specificity, not about the genericity of the name used for the shipped binary.
Part of the historical discussion on debian-hams and Jéré mentioned
it in this thread today.
Pat
--
Patrick Ouellette p...@flying-gecko.net
ne4po (at) arrl (dot) net Amateur Radio: NE4PO
Anyone use micfo.com? Thoughts?
Thanks,
Pat
--
Patrick Ouellette p...@flying-gecko.net
ne4po (at) arrl (dot) net Amateur Radio: NE4PO
What kind of change have you been in the world today?
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a
project machine could have alerted both the
project's admin team and the owner of the compromised account.
The initial compromise would have been detected sooner, and project
machines protected *without* any additional hardware or money being
spent.
--
Patrick Ouellette
[EMAIL PROTECTED]
ication pair if we can come up with a method of tying the host
key to the hardware.
I would be willing to work on such a task, if others also think it might
have merit.
--
Patrick Ouellette
[EMAIL PROTECTED]
[EMAIL PROTECTED]
Amateur Radio: KB8PYM
--
> Brian May <[EMAIL PROTECTED]>
>
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
>
>
--
Patrick Ouellette
[EMAIL PROTECTED]
Amateur Radio: KB8PYM 50.200, 144.200 EN81fp
ICBM: 41:38:25.476N 83:31:43.417W
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
manually (with debuild) but dies when the build daemon tries with
a 'cannot run configure.sub' error.
Anyone else have this problem? Is it a "feature" or a bug?
Thanks,
Pat
--
Patrick Ouellette
[EMAIL PROTECTED]
Amateur Radio: KB8PYM 50.200, 144.200 EN81fp
ICBM: 41:38:25.476N 83:31:43.417W
Yes, that's the apparent problem.
On Thu, Jan 10, 2002 at 03:38:35PM -0200, Henrique de Moraes Holschuh wrote:
> Date: Thu, 10 Jan 2002 15:38:35 -0200
> From: Henrique de Moraes Holschuh <[EMAIL PROTECTED]>
> To: Patrick Ouellette <[EMAIL PROTECTED]>
> Cc:
t the USA.
Pat
--
Patrick Ouellette p...@flying-gecko.net
ne4po (at) arrl (dot) net Amateur Radio: NE4PO
"Crank the amp to 11, this needs more cowbell - and a llama wouldn't hurt
either"
"Your arguments are an odd mix of overly optimistic on one sid
On Thu, Nov 13, 2014 at 10:04:00AM -0800, Russ Allbery wrote:
>
> In a sense, of course, this is true. However, what I'm trying to point
> out is that we have a fundamental governance question facing us here.
> What are we, as a project, going to do when we face a decision where the
> project is
On Thu, Nov 13, 2014 at 11:24:31AM -0800, Russ Allbery wrote:
> Patrick Ouellette writes:
> > On Thu, Nov 13, 2014 at 10:04:00AM -0800, Russ Allbery wrote:
>
> >> In a sense, of course, this is true. However, what I'm trying to point
> >> out is that we hav
On Thu, Nov 13, 2014 at 01:39:52PM -0800, Russ Allbery wrote:
> Patrick Ouellette writes:
>
> > We do tell users of Debian what to do - that's part of the problem right
> > now. We told the users they will switch init systems, and a large
> > portion (or at least a
On Thu, Nov 13, 2014 at 11:06:08PM +0100, Matthias Klumpp wrote:
>
> > For the record, I really don't care about the init system per-say. I am
> > more annoyed with the systemd insistence on logging to binary files than
> > anything. Log files should be plain text.
> Rsyslog is srill installed b
On Fri, Nov 14, 2014 at 12:05:17AM +, Sam Hartman wrote:
>
> I'm confused. Are you saying that cat isn't working for you
> with systemd on jessie?
> I'm honestly asking for information here.
> As best I can tell on my system everything that gets logged gets logged
> to text log files.
> Some
On Thu, Nov 13, 2014 at 06:07:33PM -0800, Russ Allbery wrote:
> Patrick Ouellette writes:
>
> > I'm saying those things that logged to syslog now log to the journal, so
> > cat /var/log/syslog doesn't work because the output that used to go
> > there is redir
On Thu, Nov 13, 2014 at 06:53:09PM -0800, Russ Allbery wrote:
>
> Maybe some failure to sync status correctly? syslog-ng does ship with a
> service file. What does:
>
> systemctl status syslog-ng
>
> say? Particularly the Loaded and Active fields should have some hint as
> to what's going
On Thu, Nov 13, 2014 at 06:19:32PM -0800, Russ Allbery wrote:
> Patrick Ouellette writes:
>
> > Since /var/log/syslog is empty, clearly there was an issue when my
> > system upgraded. I'll have to look into this to see what is going on.
>
> > (Kind of illustrates
going to move forward with
a binary named "node"
The proposal was made for a transition plan to be made then the nodejs
person quit talking/posting.
Pat
--
,-.
> Patrick Ouellette| Start by doing what's
quot;a life of it's own" in the ham radio
community.
If a binary's name is simply a matter of a popularity contest in Debian,
at some point every name may be made to change.
--
,-.
> Patric
messed up!
Pat
--
,---------.
> Patrick Ouellette | Lord, grant that I might not so much seek <
> pat(at)flying-gecko.net | to be loved as to love. <
> Amateur Radio: NE4P
am changes in node for a long time. The package
builds fine in the auto-builders and does what it was designed to do.
The number of active ham radio maintainers has varied over time, just like
other packages. Right now there are only a few, and most of us are busy
(just like everyone else).
--
,--
On Tue, May 01, 2012 at 03:24:58PM -0700, Russ Allbery wrote:
> Date: Tue, 01 May 2012 15:24:58 -0700
> From: Russ Allbery
> Subject: Re: [Pkg-javascript-devel] Node.js and it's future in debian
> To: debian-devel@lists.debian.org
>
> Patrick Ouellette writes:
> >
ms list.
It usually takes a few days to get any substantive comments on that list.
Pat
--
,-----.
> Patrick Ouellette| It is no use walking anywhere to preach unless <
> pat(at)flying-gecko.net | our
;s where I check.
Pat
--
,-----.
> Patrick Ouellette| No one is to be called an enemy, all are your <
> pat(at)flying-gecko.net | benefactors, and no one does you harm. <
> Amateur Radio: NE4PO | You have no enemy except yourselves. <
>
On Thu, May 03, 2012 at 09:08:23AM -0700, Russ Allbery wrote:
>
> Thomas Goirand writes:
> > On 05/02/2012 06:00 AM, Russ Allbery wrote:
>
> >> and the binary isn't invoked directly by users
>
> > If the binary isn't invoked directly by the users, why do we have a
> > problem? Why can't a patch
On Tue, May 01, 2012 at 03:00:46PM -0700, Russ Allbery wrote:
>
> That community is much smaller, and the binary isn't invoked directly by
> users, which makes the impact fairly minimal in practice.
>
Can you support that assertion with data? I'm not talking installed
instances in Debian, but i
On Thu, May 03, 2012 at 01:10:24PM +0200, Vincent Bernat wrote:
>
> As said many times, node is an interpreter used in shebang. Using a
> different name would just upset its user base. Debian will be seen,
> again, as the one harming a community, like this may happen in the
> Ruby community becaus
On Thu, May 03, 2012 at 02:35:06PM -0300, Fernando Lemos wrote:
>
> So while I don't think decisions shouldn't be taken based solely on
> popcon stats, I think it would be silly to think that ham radio would
> be more popular than node.js. I understand you're reluctant to undergo
> this transition
On Thu, May 03, 2012 at 08:48:07PM +0200, Vincent Bernat wrote:
> OoO Pendant le repas du jeudi 03 mai 2012, vers 19:35, Patrick Ouellette
> disait :
>
> >> As said many times, node is an interpreter used in shebang. Using a
> >> different name would just upset its use
Can someone please explain to be why it is so unpalatable to
have the Node.js package in the README and in an installation/
configuration message include the following (or similar) message:
Node.js in Debian has the executable name /usr/bin/nodejs
This is to solve a conflict with a package that st
On Thu, May 03, 2012 at 09:24:00PM +0200, Raphael Hertzog wrote:
>
> So to avoid disruptions, you rename the binary in the package and in the
> "postinst configure " which is run during upgrade, you add a
> symlink from /usr/sbin/node to ax25-node and you display a prominent
> warning explaining t
On Thu, May 03, 2012 at 10:11:41PM +0200, Raphael Hertzog wrote:
>
> > You also don't address the issue of a user who installs both packages
> > and now gets varying behavior depending on their $PATH - a result not
> > of a local administrator's action, but of the Debian package's actions.
>
> If
On Thu, May 03, 2012 at 09:21:16PM +0100, Colin Tuckley wrote:
> Date: Thu, 03 May 2012 21:21:16 +0100
> From: Colin Tuckley
> Subject: Re: Node.js and it's future in debian
> To: debian-devel@lists.debian.org
>
> On 03/05/12 20:44, Patrick Ouellette wrote:
>
> &g
On Thu, May 03, 2012 at 03:09:42PM -0400, Andrew Starr-Bochicchio wrote:
>
> It has been said many times that the impact on users will be limited
> as node is not meant to be called directly but by inetd. You and other
> members of the ham radio community seem to feel that there would be an
> impa
On Thu, May 03, 2012 at 05:13:09PM -0400, Chris Knadle wrote:
>
> Drat. I forgot about APRS. APRS has become fairly popular among hams, so
> much
> so that it now comes built-in to several radios, and even HTs (Handy-Talkies).
>
> APRS is a system for location reporting. It's also very common
On Thu, May 03, 2012 at 04:46:09PM -0500, Peter Samuelson wrote:
> Date: Thu, 3 May 2012 16:46:09 -0500
> From: Peter Samuelson
> Subject: Re: Node.js and it's future in debian
> To: debian-devel@lists.debian.org, Patrick Ouellette ,
> Andrew Starr-Bochicchio
>
>
On Tue, May 08, 2012 at 12:41:40PM +1000, Ben Finney wrote:
>
> David Weinehall writes:
>
> > Wasn't the main reason (apart from the seniority argument) for
> > preserving the node name for ax25 to prevent remote unmonitored highly
> > important systems from failing?
>
> If such systems are hig
d with this issue, and neither side has shown a
willingness to change, I would say the time has come for both packages to be
renamed.
Pat (one of the unresponsive ham radio maintainers)
--
Patrick Ouellette p...@flying-gecko.net
ne4po (at) arrl (dot) net Amateur Radio: NE4PO
What kind of change have you been in the world today?
signature.asc
Description: Digital signature
On Sun, Nov 06, 2011 at 09:20:31PM -0600, Jonathan Nieder wrote:
>
> Hi Pat,
>
> Patrick Ouellette wrote:
>
> > The binary on the ham radio side is not "LinuxNode" in package "node" it is
> > simply "node" in package "node"
>
Where is the voice of the nodejs maintainers in this? They are
listed as:
Debian Javascript Maintainers
Jérémy Lal
Dave Beckett
Jonas Smedegaard
--
Patrick Ouellette p...@flying-gecko.net
ne4po (at) arrl (dot) net Amateur Radio: NE4PO
What kind of change have you
nyway!
>
The issue is one of following policy. Debian policy doesn't allow such a
"resolution" to this issue. Consensus on which must change, or both must
change are the only allowed outcomes.
73,
Pat
--
Patrick Ouellette p...@flying-gecko.net
ne4po (
On Wed, Nov 09, 2011 at 08:33:38AM +, Philipp Kern wrote:
>
> On 2011-11-08, Patrick Ouellette wrote:
> > I hope to avoid any issues with breaking old boxes with the eventual
> > resolution of the issue.
>
> I don't know what's wrong with Jonathan Ni
he name of *any* binary has the potential for creating
unintended consequences for the end users.
Pat
--
Patrick Ouellette p...@flying-gecko.net
ne4po (at) arrl (dot) net Amateur Radio: NE4PO
What kind of change have you been in the world today?
--
To UNSUBSCRIBE,
archive, install the old syslog as an alternative.
nodejs *only* exists in unstable. A name change in unstable should be
less disruptive because it is, well - unstable.
Pat
--
Patrick Ouellette p...@flying-gecko.net
ne4po (at) arrl (dot) net Amateur Radio: NE4PO
W
s, find a mentor.
Good Luck!
--
Patrick Ouellette p...@flying-gecko.net
ne4po (at) arrl (dot) net Amateur Radio: NE4PO
What kind of change have you been in the world today?
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscri
y of a DVD. All you have to do
is a block copy of the media. That is just one of the reasons the arguments
against decss are/were less than intelligent.
Pat
--
,---------.
> Patrick Ouellette| No one is to be called
On Fri, Mar 16, 2012 at 12:21:14AM +, Ben Hutchings wrote:
>
> On Thu, Mar 15, 2012 at 04:11:00PM -0400, Patrick Ouellette wrote:
> > On Sun, Mar 11, 2012 at 09:48:02AM +0100, Luk Claes wrote:
> > >
> > > Why so? If I make a copy for backup and want to use
On Thu, Mar 15, 2012 at 08:20:22PM -0400, Chris Knadle wrote:
> On Thursday, March 15, 2012 16:11:00, Patrick Ouellette wrote:
> > On Sun, Mar 11, 2012 at 09:48:02AM +0100, Luk Claes wrote:
> > > Why so? If I make a copy for backup and want to use it, how would I do
> > >
On Thu, Oct 25, 2012 at 09:51:16AM +0200, Thibaut Paumard wrote:
>
> So yes, I say long silence from the entire community *including the
> package maintainer(s)* probably means it's safer to orphan the package
> than not. I would probably send a few pings during the one month
> period though. I wo
I think a reasonable policy statement for this would be something like:
All pre-release versions will have debian revision of -0.x
Maintainer release revisions will start at -1 and increment in
whole numbers
Non maintainer releases will add a point version to the left of the
maintainer release
OOPS
left should be right.
One of these days I'll be able to tell my left and right apart!
> -Original Message-
> From: Patrick Ouellette [mailto:[EMAIL PROTECTED]
> Sent: Thursday, June 25, 1998 3:13 PM
> To: debian-policy@lists.debian.org
> Cc: Debian Deve
68 matches
Mail list logo
