On Wed, 23 Nov 2005 23:01:25 -0800, Thomas Bushnell BSG
[EMAIL PROTECTED] wrote:
Marc Haber [EMAIL PROTECTED] writes:
According to the reports of another member of the ftp-master team, the
situation was cleared up, but Mr. Troup re-enabled the check that
breaks dpkg-sig on purpose after not
On Tue, 22 Nov 2005 21:41:21 +0100, Andreas Schuldei
[EMAIL PROTECTED] wrote:
* Marc Haber [EMAIL PROTECTED] [2005-11-21 23:33:48]:
If the DPL team is actually addressing that issue, it is not doing so
transparently.
That was on purpose. we thought that there was something to be
learned from
* Marc Haber [EMAIL PROTECTED] [2005:11:23 11:07 +0100]:
What are you trying to do instead? If you might have noticed, we have
_just_ _another_ ftpmaster situation _right_ _now_, and from handling
of #339686 by a member of the DPL team I don't get the impression that
the DPL team actually
On Wed, 23 Nov 2005 11:32:19 -0500, Erinn Clark
[EMAIL PROTECTED] wrote:
* Marc Haber [EMAIL PROTECTED] [2005:11:23 11:07 +0100]:
What are you trying to do instead? If you might have noticed, we have
_just_ _another_ ftpmaster situation _right_ _now_, and from handling
of #339686 by a member
On Wed, 23 Nov 2005, Marc Haber wrote:
Sorry. #340306.
Hmm... wasn't the situation around this bug cleared up in another d-devel
thread no more than two or three days ago, and a fix already commited to
CVS?
--
One disk to rule them all, One disk to find them. One disk to bring
them all and
[Henrique de Moraes Holschuh]
Hmm... wasn't the situation around this bug cleared up in another
d-devel thread no more than two or three days ago, and a fix already
commited to CVS?
That's what I thought. But the bug is still open. And jvw's reasoning
that it is OK for ftp.debian.org to
Marc Haber [EMAIL PROTECTED] wrote:
What are you trying to do instead? If you might have noticed, we have
_just_ _another_ ftpmaster situation _right_ _now_, and from handling
of #339686 by a member of the DPL team I don't get the impression that
the DPL team actually cares.
(#340306)
In
On Wed, 23 Nov 2005 16:14:47 -0200, Henrique de Moraes Holschuh
[EMAIL PROTECTED] wrote:
On Wed, 23 Nov 2005, Marc Haber wrote:
Sorry. #340306.
Hmm... wasn't the situation around this bug cleared up in another d-devel
thread no more than two or three days ago, and a fix already commited to
CVS?
* Marc Haber [Wed, 23 Nov 2005 18:38:15 +0100]:
I confused these bugs because in the discussion, somebody used #339686
to show that I am doing a job as bad as Mr. Troup.
10:18 dato Zugschlus: so. how'd you'd feel if I said that #339686 was
a deliberate attempt on your part to
Marc Haber [EMAIL PROTECTED] writes:
What are you trying to do instead? If you might have noticed, we have
_just_ _another_ ftpmaster situation _right_ _now_, and from handling
of #339686 by a member of the DPL team I don't get the impression that
the DPL team actually cares.
I can't
Marc Haber [EMAIL PROTECTED] writes:
According to the reports of another member of the ftp-master team, the
situation was cleared up, but Mr. Troup re-enabled the check that
breaks dpkg-sig on purpose after not being amused about HE's rant on
here.
If this is accurate, it is not reasonable.
On Mon, 21 Nov 2005, Thomas Bushnell BSG wrote:
Andreas Schuldei [EMAIL PROTECTED] writes:
i have not given up that hope yet and i invest a considerable
amount of time working on this issue as part of my work on the
DPL-Team. others there do so, too.
I hope this is true. I really do.
* Jaakko Niemi [EMAIL PROTECTED] [2005-11-22 17:12:00]:
On Mon, 21 Nov 2005, Thomas Bushnell BSG wrote:
Andreas Schuldei [EMAIL PROTECTED] writes:
i have not given up that hope yet and i invest a considerable
amount of time working on this issue as part of my work on the
DPL-Team.
Scripsit Anand Kumria [EMAIL PROTECTED]
On Mon, Nov 21, 2005 at 02:18:02AM +0100, Henning Makholm wrote:
If somebody designs and implements (after a suitable architectural
review) some software to support distributed keyring maintenance in a
secure, auditable way, it is likely that calls for
On Tue, 22 Nov 2005, Andreas Schuldei wrote:
Get to next debconf and see him actually work with people.
No need for words.
did i beat someone up when i was watched? did it get caught on
film, even? (c:
... where did the evidence go? :)
--j
--
To UNSUBSCRIBE, email
* Florian Weimer [EMAIL PROTECTED] [2005-11-22 08:52:25]:
* Andreas Schuldei:
i have not given up that hope yet and i invest a considerable
amount of time working on this issue as part of my work on the
DPL-Team. others there do so, too.
Is this the delegation to teams item on
* Marc Haber [EMAIL PROTECTED] [2005-11-21 23:33:48]:
If the DPL team is actually addressing that issue, it is not doing so
transparently.
That was on purpose. we thought that there was something to be
learned from threads on public mailinglists that lead nowhere and
wanted to try private mail
* Marc Haber [EMAIL PROTECTED] [2005-11-21 08:55:52]:
On Sun, 20 Nov 2005 11:29:19 +0100, Petter Reinholdtsen
[EMAIL PROTECTED] wrote:
I seriously hope the non-elected people blocking and slowing down
several important processes in Debian soon realize that there is a
problem and that it
2005/11/21, Henning Makholm [EMAIL PROTECTED]:
It can be considered bad from a technical viewpoint - as far as I
understand the master copy of the keyring is currently on a medium
that is under the keyring maintainer's direct physical control.
The obvious way of switching to team maintenance
On Mon, 21 Nov 2005, Martijn van Oosterhout wrote:
Anyway, surely the acceptance onto the keyring is designated by a
signiture on that key, not just by it's presense in a particular file?
Yes, it *is* the presense in a particular file.
--
One disk to rule them all, One disk to find them.
Scripsit Martijn van Oosterhout [EMAIL PROTECTED]
My first thought would be to simply create multiple keyrings, one for
each keyring maintainer, which are merged on a regular basis. Teaching
the archive scripts to look at more than one keyring wouldn't be too
hard.
That would not solve the
On Mon, 21 Nov 2005 09:05:02 +0100, Andreas Schuldei
[EMAIL PROTECTED] wrote:
* Marc Haber [EMAIL PROTECTED] [2005-11-21 08:55:52]:
On Sun, 20 Nov 2005 11:29:19 +0100, Petter Reinholdtsen
[EMAIL PROTECTED] wrote:
I seriously hope the non-elected people blocking and slowing down
several
Hi Henning,
On Mon, Nov 21, 2005 at 02:18:02AM +0100, Henning Makholm wrote:
Scripsit Martijn van Oosterhout [EMAIL PROTECTED]
push aside? There's no rule that says there can be only one. Yes,
replacing someone could become ugly, but providing additional hands
can't be considered bad,
[Anand Kumria]
- require the developer to generate a new key
- require the developer to have _at least_ N
number of other, existing developers sign
their key
- once the developer
Andreas Schuldei [EMAIL PROTECTED] writes:
i have not given up that hope yet and i invest a considerable
amount of time working on this issue as part of my work on the
DPL-Team. others there do so, too.
I hope this is true. I really do. However, I have no particular
evidence that it is
* Andreas Schuldei:
i have not given up that hope yet and i invest a considerable
amount of time working on this issue as part of my work on the
DPL-Team. others there do so, too.
Is this the delegation to teams item on
http://wiki.debian.org/DPLTeamCurrentIssues? A rather cryptic
reference,
[Nathanael Nerode]
It's a pity the DPL hasn't anointed a less-busy person with
authority to alter the keyring.
I suspect and hope the DPL try to reason with the people in question
first, before the DPL wields his authority and push the current holder
of privileged positions aside, as a power
2005/11/20, Petter Reinholdtsen [EMAIL PROTECTED]:
I suspect and hope the DPL try to reason with the people in question
first, before the DPL wields his authority and push the current holder
of privileged positions aside, as a power struggle with the overworked
people in these privileged key
Chip Salzenberg [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
Who does a developer have to fuck around here to get his key deleted?
I'm not sure your resignation was valid. Most important debian mechanisms
require a signature from a key in the keyring.
It is hard for anybody to
Chip Salzenberg [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
Who does a developer have to fuck around here to get his key deleted?
--
Chip Salzenberg [EMAIL PROTECTED]
Wait. Ignore my previous post. I had forgotten that the resignation post was
indeed signed. It might however be
Chip == Chip Salzenberg [EMAIL PROTECTED] writes:
Chip Who does a developer have to fuck around here to get his key
Chip deleted? -- Chip Salzenberg [EMAIL PROTECTED]
Chip -- To UNSUBSC
Hi. As you are no doubt aware by now, getting your key removed is a
great mystery and deep
Scripsit Martijn van Oosterhout [EMAIL PROTECTED]
push aside? There's no rule that says there can be only one. Yes,
replacing someone could become ugly, but providing additional hands
can't be considered bad, can it?
It can be considered bad from a technical viewpoint - as far as I
understand
Henning Makholm [EMAIL PROTECTED] writes:
If somebody designs and implements (after a suitable architectural
review) some software to support distributed keyring maintenance in a
secure, auditable way, it is likely that calls for adding more people
to the task would be considered more
On Sun, 20 Nov 2005 11:29:19 +0100, Petter Reinholdtsen
[EMAIL PROTECTED] wrote:
I seriously hope the non-elected people blocking and slowing down
several important processes in Debian soon realize that there is a
problem and that it might be best for them to solve it by stepping
aside or allowing
On 15:34 Fri 18 Nov 2005, Chip Salzenberg wrote:
Who does a developer have to fuck around here to get his key deleted?
That's the way it is.
--
David Moreno Garza [EMAIL PROTECTED] | http://www.damog.net/
[EMAIL PROTECTED] | GPG: C671257D
Cuando yo nací, la
Chip Salzenberg wrote:
Who does a developer have to fuck around here to get his key deleted?
Same one he has to fuck to get a new key added, presumably.
It's a pity the DPL hasn't anointed a less-busy person with authority to
alter the keyring.
--
ksig --random|
--
To UNSUBSCRIBE, email to
Who does a developer have to fuck around here to get his key deleted?
--
Chip Salzenberg [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
37 matches
Mail list logo