M W Blunier wrote:
> On 27 Oct 1997, Manoj Srivastava wrote:
>
> >
> > What problems are term limits supposed to solve, exactly?
>
> They prevent the voters from re-electing someone that due to his
> entrenchment in the system, has more power than a freshman would
> have. Greedy and self se
On 27 Oct 1997, Manoj Srivastava wrote:
>
> What problems are term limits supposed to solve, exactly?
They prevent the voters from re-electing someone that due to his
entrenchment in the system, has more power than a freshman would
have. Greedy and self serving voters vote for the incumba
From: Britton <[EMAIL PROTECTED]>
> I just don't see the point in making the process of succession so
> competitive.
It depends if you want the project leader choice to be democratic or not.
If it's going to be democratic, there _has_ to be competition.
Thanks
Bruce
--
Can you g
On Mon, 27 Oct 1997, Syrus Nemat-Nasser wrote:
> On Mon, 27 Oct 1997, Richard G. Roberto wrote:
>
> [snip]
> > PROPOSAL FOR TERM LIMITS
> >
> > I propose that all elected posts in the Debian organization
> > be subject to the following term limits:
I actually like this proposal. I have no pr
Hi,
If this is a thrust for consensus building, then I state that
I like PAM. People very interested in implementing security for
financial institutions have selected PAM; I think we'll benefit from
using it.
manoj
--
Facts are God's arguments, we should be careful never to
Santiago Vila Doncel wrote:
>
> Fabrizio Polacco wrote:
> > Yes, make this symlink (ln -s ../share/doc /usr/doc) on freshly
> > installed systems (where /usr/share/docs will really exist), while
> > make the opposite (ln -s ../../doc /usr/share/doc) on existing
> > systems (where /usr/doc is still
On Thu, 23 Oct 1997, David Engel wrote:
[snip]
> I suggest we modify libtool for Debian to not use -rpath. Comments?
Yes, I think this would be good.
I don't know the `-rpath' option of ld much, so please correct me if I'm
wrong. Is it true that we don't need this option at all? If so, we shou
On Wed, 22 Oct 1997 [EMAIL PROTECTED] wrote:
[snip]
> I suggested PAM support as a goal for 2.0; as such it has gone into Brian C.
> White's "Upcoming Debian Releases" document (
> http://www.debian.org/Lists-Archives/debian-devel-9709/msg00042.html
> is there a permanent web location??).
>
> I l
Richard thinks I'm a putz? I am struck to the heart! Oh, cruel fate! :-)
Term limits are fine, but the biggest problem so far has been finding
serious candidates for the job. I greatly appreciate Ian's running, as
until now there never has been a contested election, and I could not
seriously say t
On Mon, 27 Oct 1997, Richard G. Roberto wrote:
[snip]
> PROPOSAL FOR TERM LIMITS
>
> I propose that all elected posts in the Debian organization
> be subject to the following term limits:
[snip]
So, Richard. Are you ready to commit a lot of your private time to
becoming project leader for a yea
Manoj Srivastava <[EMAIL PROTECTED]> writes:
> >> Changes: section. So Guys script should look for #(\d+) and
> >> close $1 after proceeding (speaking in Perl).
>
> Andreas> lets use "\(close #(\d+)\)", some people might make a note
> Andreas> related to a bug not yet fixed.
>
> Johnie> I prefe
-BEGIN PGP SIGNED MESSAGE-
On Mon, 27 Oct 1997, Joey Hess wrote:
> I don't like overloading the changelog like this (no, I don't use release).
> How about extending the changelog format so we have a field for closed bugs?
> Something like:
>
> foo (1.0-2) unstable; urgency=low closes=100
I think you are right there is not much left to be said. However, it is
comforting to note that this one ugly thread is the only I have seen in
all my time on the Debian lists. Looked at in that light it's sort of
reassuring. If bad threads are so incidental, I can comfortably ignore
them. An
On Mon, Oct 27, 1997 at 05:06:01PM +0100, Giuseppeferdy Miceli wrote:
> From: [EMAIL PROTECTED] (Giuseppe "ferdy" Miceli)
> Date: 27 Oct 1997 17:06:00 +0100
> Message-ID: <[EMAIL PROTECTED]>
> Lines: 12
> X-Mailer: Gnus v5.4.52/XEmacs 20.2
>
>ciao,
>
> i've got 123 mails about dissent and rel
Manoj Srivastava wrote:
> Maybe a slightly stricter syntax for closing bugs, so I may
> mention things like "This is similar to Bug#12345 on package xyz. We
> are still lokking for a solution".
>
> Maybe the check should eb for "This closes Bug#*** BUG#***"
> (concatenatnig the line
Hi,
>>"Johnie" == Johnie Ingram <[EMAIL PROTECTED]> writes:
Johnie> "Andreas" == Andreas Jellinghaus <[EMAIL PROTECTED]> writes:
>> Changes: section. So Guys script should look for #(\d+) and close
>> $1 after proceeding (speaking in Perl).
Andreas> lets use "\(close #(\d+)\)", some people might
From: [EMAIL PROTECTED] (Giuseppe "ferdy" Miceli)
Date: 27 Oct 1997 17:06:00 +0100
Message-ID: <[EMAIL PROTECTED]>
Lines: 12
X-Mailer: Gnus v5.4.52/XEmacs 20.2
ciao,
i've got 123 mails about dissent and related things. i think - my humble
opinion of course - those are far too many for a non-te
"Andreas" == Andreas Jellinghaus <[EMAIL PROTECTED]> writes:
>> Changes: section. So Guys script should look for #(\d+) and close
>> $1 after proceeding (speaking in Perl).
Andreas> lets use "\(close #(\d+)\)", some people might make a note
Andreas> related to a bug not yet fixed.
I prefer the
Hi,
I think term limits may not be the panacea that people think
they are.
1) Unlike general elections, incumbents do not have more money to
spend than challengers
2) Unlike general elections, incumbents do not get more into the
constituents eye (any body can mail on the lists
Sorry to have come into this so late, but I was tuned in to a
different soap opera ;)
This is not the first time someone has requested that Bruce
be "impeached" or removed from his post as project leader,
or president, or whatever it is currently. This is the
first time Dave Cinege has done it.
> Please don't get me wrong: I like the FHS! But we can't implement it for
> Debian 2.0 (hamm) and keep the current dead line.
so decide now : fhs or deadline, we cannot have both.
i think that libc6 will kill the deadline anyway, so i'm a friend of
fhs.
andreas
-BEGIN PGP SIGNED MESSAGE-
Fabrizio Polacco wrote:
> Lalo Martins wrote:
> > Maybe we could come up with a "transition path" - like moving
> > stuff like /usr/doc (less prone to make the system break) and
> > then symlinking "ln -s /usr/share/doc /usr/doc"
>
> Yes, make this symlink (ln -
On Mon, 27 Oct 1997, Ian Jackson wrote:
> Andreas Jellinghaus:
> > please split hamm into two distributions :
> > hamm/unstable and hamm-unstable/fhs-unstable (maybe you have better names).
>
> I'm afraid I think this is a stunningly bad idea.
Exactly.
With the introduction of FHS, we'll increm
On 27 Oct 1997, Kai Henningsen wrote:
> [EMAIL PROTECTED] (Christian Schwarz) wrote on 26.10.97 in <[EMAIL
> PROTECTED]>:
>
> > Here is an incomplete list of changes that would produce lots of work:
> >
> >/usr/doc -> /usr/share/doc(this affects _every_ package!)
> >/usr/man ->
Lalo Martins wrote:
>
> Maybe we could come up with a "transition path" - like moving
> stuff like /usr/doc (less prone to make the system break) and
> then symlinking "ln -s /usr/share/doc /usr/doc"
>
Yes, make this symlink (ln -s ../share/doc /usr/doc) on freshly
installed systems (where /usr/
> with documentation i only have ls /usr/doc/pkg (or dpkg -L pkg |grep
> /usr/doc). with docs splited into several trees this will be more
> difficult.
Maybe we should then try to help Jim get dwww ready and let that handle it.
Also, is it possible to try to get dhelp and dwww talk to each other?
d
> > i will like an automatic method to close bugs.
>
> Let's take a look at the .changes files. Normally all information
> is covered there. Normally closed bugs are mentioned in the
> Changes: section. So Guys script should look for #(\d+) and
> close $1 after proceeding (speaking in Perl).
l
Hi,
>>"Martin" == Martin Schulze <[EMAIL PROTECTED]> writes:
>> i will like an automatic method to close bugs.
Martin> Let's take a look at the .changes files. Normally all
Martin> information is covered there. Normally closed bugs are
Martin> mentioned in the Changes: section. So Guys script
Hi,
I think that this topic has reached the end of it's utility
(much as I like the discourse). I think we are beginning to repeat
ourselves. In concluding my participation on this thread, I have this
to add:
a) The list is not a place where the first amendment to the US
constitut
On Oct 26, Christian Schwarz decided to present us with:
[...]
> I suggest to implement FHS 2.0 with a few exceptions _after_ hamm (2.0)
> is released. Until then, we can discuss the different changes in detail
> and decide which parts of the FHS we'll drop.
I suggest we make FHS 2.0 [with or with
Andreas Jellinghaus:
> please split hamm into two distributions :
> hamm/unstable and hamm-unstable/fhs-unstable (maybe you have better names).
I'm afraid I think this is a stunningly bad idea.
We already have a major incremental upgrade compatibility problem
between 1.3 and 2.0, which we're stil
31 matches
Mail list logo
