On Thu, Feb 22, 2007 at 06:56:01PM -0800, Steve Langasek wrote:
Um, the only archs that don't meet the redundancy requirement today are
i386
and ia64.
http://release.debian.org/etch_arch_qualify.html says alpha, amd64, arm,
hppa, i386, ia64, and m68k don't meet it, fwiw.
Oops.
On Fri, Feb 23, 2007 at 12:13:03PM +1000, Anthony Towns wrote:
On a personal note, in my experience the most effective way of working
with James and Ryan is to trust that they generally know what they're
doing and more or less leave them to get on with making things better on
their own rather
Pierre Habouzit [EMAIL PROTECTED] writes:
I understand they cannot communicate about _everything_. But a
downtime like that _is_ worth communicating. If they don't understand
You did notice that the DSA team is about to install a request tracker
for issues like you described? I would think
On 2007-02-23, Kalle Kivimaa [EMAIL PROTECTED] wrote:
Pierre Habouzit [EMAIL PROTECTED] writes:
I understand they cannot communicate about _everything_. But a
downtime like that _is_ worth communicating. If they don't understand
You did notice that the DSA team is about to install a request
also sprach Kalle Kivimaa [EMAIL PROTECTED] [2007.02.23.1054 +0100]:
You did notice that the DSA team is about to install a request tracker
for issues like you described? I would think that takes care of most
of the current communication related issues.
Does it say anywhere that this will be
On Fri, Feb 23, 2007 at 11:54:40AM +0200, Kalle Kivimaa wrote:
Pierre Habouzit [EMAIL PROTECTED] writes:
I understand they cannot communicate about _everything_. But a
downtime like that _is_ worth communicating. If they don't understand
You did notice that the DSA team is about to
On Fri, Feb 23, 2007 at 11:54:40AM +0200, Kalle Kivimaa wrote:
Pierre Habouzit [EMAIL PROTECTED] writes:
I understand they cannot communicate about _everything_. But a
downtime like that _is_ worth communicating. If they don't understand
You did notice that the DSA team is about to
On pe, 2007-02-23 at 11:41 +0100, Marc Haber wrote:
Our core teams not communicating is a social problem. RT is a
technical solution. There are no technical solutions for social
problems.
This meme is often repeated, but I don't think it is entirely true.
As an example, consider couples who
Anthony Towns [EMAIL PROTECTED] wrote:
incredibly open manner with a pretty impressive level of uptime. None
of that means we can't or shouldn't be doing better, but I think it's
worth recognising that when we say we're not doing a good enough job,
*we* are still the ones setting and raising
Pierre Habouzit a écrit :
On Fri, Feb 23, 2007 at 12:13:03PM +1000, Anthony Towns wrote:
On a personal note, in my experience the most effective way of working
with James and Ryan is to trust that they generally know what they're
doing and more or less leave them to get on with making things
On Fri, Feb 23, 2007 at 11:41:06AM +0100, Marc Haber wrote:
Our core teams not communicating is a social problem. RT is a
technical solution. There are no technical solutions for social
problems.
That's not always true. Let's suppose (ad absurdum) that the questioned
teams have their own .txt
On Fri, Feb 23, 2007 at 10:44:55AM +0100, Pierre Habouzit wrote:
So sorry, but I don't buy a single word of your argumentation here.
It wasn't an argument; it was just a statement of things are, as I see
them. In so far as how things are isn't well communicated in those
areas, I don't see any
Hi!
* Lars Wirzenius [EMAIL PROTECTED] [070223 11:50]:
There are no technical solutions for social problems.
This meme is often repeated, but I don't think it is entirely true.
As an example, consider couples who sleep in the same bed, under the
same blanket. They often complain about a
On 2007-02-23, Alexander Schmehl [EMAIL PROTECTED] wrote:
the other party steals the blanket during the night and leaves the other
^
one shivering.
I know we are on the way to an off topic thread, but I'm curious: Why
is that a social problem?
because of the
Package: project
Severity: serious
The Debian project lacks an alpha developer-available machine for about
8 months. This makes some bugs impossible to fix.
The severity is set to serious because alpha is a release architecture
for Etch, but without a developer-available machine it is not sure
On Fri, Feb 23, 2007 at 08:45:27PM +1000, Anthony Towns wrote:
On Fri, Feb 23, 2007 at 10:44:55AM +0100, Pierre Habouzit wrote:
So sorry, but I don't buy a single word of your argumentation here.
It wasn't an argument; it was just a statement of things are, as I see
them. In so far as how
Anthony Towns aj@azure.humbug.org.au wrote:
We're far beyond trying to help them, at least for me, [...]
Your opinions are only ever going to be considered in so far as you're
willing to help make them a reality. If you're not willing to help,
find something else to worry about.
So you
Lars Wirzenius [EMAIL PROTECTED] wrote:
[...] They often complain about a social problem, namely that
the other party steals the blanket during the night and leaves the other
one shivering.
The technical solution this social problem is to have two blankets.
That doesn't solve it: the other
On Fri, Feb 23, 2007 at 12:13:03PM +1000, Anthony Towns wrote:
The primary reason why there's only one keyring-maint is the binary
blob problem: [...]
[...]
This issue has been mentioned briefly in the past a few times, but to
the best of my knowledge, no one's taken up the challenge so far.
On 2/23/07, martin f krafft [EMAIL PROTECTED] wrote:
also sprach Kalle Kivimaa [EMAIL PROTECTED] [2007.02.23.1054 +0100]:
You did notice that the DSA team is about to install a request tracker
for issues like you described? I would think that takes care of most
of the current communication
On Fri, Feb 23, 2007 at 12:14:34PM +0100, Stefano Zacchiroli wrote:
I personally do *not* think an RT would change anything. Still I don't
see a valid reason for *not* trying.
One reason would be that we could do something more valuable with the
same effort. I see parallels with what Bruce
On Fri, Feb 23, 2007 at 12:57:01PM +0100, Frank K?ster wrote:
Anthony Towns aj@azure.humbug.org.au wrote:
We're far beyond trying to help them, at least for me, [...]
Your opinions are only ever going to be considered in so far as you're
willing to help make them a reality. If you're not
On Fri, Feb 23, 2007 at 10:06:47AM -0300, Gustavo Franco wrote:
softwares) and anyone is free to open bugs with debsecan output and
stuff like that. Don't tell me that hey, what's the alpha machine
status? and keyring-maint requests will leak information.
Off the top of my head Please send
Anthony Towns aj@azure.humbug.org.au wrote:
On Fri, Feb 23, 2007 at 12:57:01PM +0100, Frank K?ster wrote:
Anthony Towns aj@azure.humbug.org.au wrote:
We're far beyond trying to help them, at least for me, [...]
Your opinions are only ever going to be considered in so far as you're
Anthony Towns aj@azure.humbug.org.au wrote:
On Fri, Feb 23, 2007 at 12:57:01PM +0100, Frank K?ster wrote:
All we are
allowed to consider with respect to these teams is to help *them*, not
to achieve help?
You can reasonably expect them to do what they've said they will, or
what the role
On 2/23/07, Mark Brown [EMAIL PROTECTED] wrote:
On Fri, Feb 23, 2007 at 10:06:47AM -0300, Gustavo Franco wrote:
softwares) and anyone is free to open bugs with debsecan output and
stuff like that. Don't tell me that hey, what's the alpha machine
status? and keyring-maint requests will leak
also sprach martin f krafft [EMAIL PROTECTED] [2007.02.23.1101 +0100]:
You did notice that the DSA team is about to install a request
tracker for issues like you described? I would think that takes
care of most of the current communication related issues.
Does it say anywhere that this
Thanks, Anthony, for the update. I have some small comments inline
below:
As a consequence, if you have two people working on the keyring,
and one hands the other a new version claiming that the only
change is to include a new key for foo, it's very hard for the
other maintainer to verify
Anthony Towns aj@azure.humbug.org.au wrote:
If they don't do it, and it's important, someone else will. Cf the
security team versus testing security support, backports or [...]
That's fine if they don't do it. I think the problem is when
they're doing it and make a mistake which they won't
On Fri, Feb 23, 2007 at 12:13:03PM +1000, Anthony Towns wrote:
[...lots of interesting info snipped...]
* Wanna-build access
- Ryan Murray, Steve Langasek, James Troup, Anthony Towns, others
- schedule give-backs, binNMUs, etc
- listed as group wb-$arch on DSA
Anthony Towns wrote:
I've been delaying this mail for a while now
Is it purely coincidental that it was sent the same day as your
nomination for the DPL elections?
--
.''`.
: :' : We are debian.org. Lower your prices, surrender your code.
`. `' We will add your hardware and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Folks,
I'm currently in discussion with a tartan designer to come up with a design
for a Debian Tartan in time for kilts to be made for people that would like
them for Debconf7
The timing is going to be tight, in that we need to get the beginning
On Fri, Feb 23, 2007 at 08:05:33PM +0100, Josselin Mouette wrote:
Anthony Towns wrote:
I've been delaying this mail for a while now
Is it purely coincidental that it was sent the same day as your
nomination for the DPL elections?
Not remotely; I was delaying the nomination until I'd finished
Anthony Towns wrote:
On Fri, Feb 23, 2007 at 11:15:00PM -0500, Joey Hess wrote:
Changed-By: Joey Hess [EMAIL PROTECTED]
Comment: Removing an old email address.
I'm not sure that's plausible -- afaik the keyring gets synced to the
real keyservers for new signatures and uids, so removing
On Sat, Feb 24, 2007 at 12:54:41AM -0500, Joey Hess wrote:
That means you can't reorder changesets easily. I wonder if it'd be
better say del uid [EMAIL PROTECTED] and have the tool work out
which uid (if any) that is.
I don't feel that reordering changesets is a good thing in general,
Anthony Towns wrote:
I was more meaning it as an optimisation so you could ignore key
add 0x7172daed if there was a key delete 0x7172daed changeset
later. Likewise a uid add followed by a uid del or whatever.
Ah, sure, as an optimisation it could be useful. However, I think that
letting the
36 matches
Mail list logo
