On Tue, Jan 30, 2007 at 10:38:17PM +0100, Marc Haber wrote:
On Tue, 30 Jan 2007 20:29:33 +0100, Wouter Verhelst
[EMAIL PROTECTED] wrote:
It's not that it's sacred; it's that w-b uses a Berkeley DB with a
database-level lock for every access (including read-only access); so
giving such access
Marc Haber [EMAIL PROTECTED] writes:
On Tue, 30 Jan 2007 20:29:33 +0100, Wouter Verhelst [EMAIL PROTECTED] wrote:
It's not that it's sacred; it's that w-b uses a Berkeley DB with a
database-level lock for every access (including read-only access); so
giving such access to everyone who asks for
On Mon, Jan 29, 2007 at 11:04:12AM +0100, Aurelien Jarno wrote:
You think wrong. Using the public ldap database, you can find the
following details:
This access is only usable for people which have login access to
ftp-master (or where the info currently is located).
Even if I'm included into
Aurelien Jarno [EMAIL PROTECTED] writes:
Goswin von Brederlow a écrit :
Aurelien Jarno [EMAIL PROTECTED] writes:
One first step would be to keep the current build daemons maintainers
(ie the person who signs the upload), and give and access to some
porters to the wanna-build database. This
On Mon, Jan 29, 2007 at 10:35:04AM +0100, Goswin von Brederlow wrote:
Aurelien Jarno [EMAIL PROTECTED] writes:
One first step would be to keep the current build daemons maintainers
(ie the person who signs the upload), and give and access to some
porters to the wanna-build database. This
On Mon, Jan 29, 2007 at 11:04:12AM +0100, Aurelien Jarno wrote:
There is no wb-amd64 nor wb-mipsel. I don't know why.
Because for actual w-b access from buildd hosts, those groups are no
longer used. Instead, there's a buildd_$arch user for every architecture
on buildd.d.o, to which access is
On Mon, Jan 29, 2007 at 11:40:00PM +1100, Hamish Moffatt wrote:
On Mon, Jan 29, 2007 at 11:04:12AM +0100, Aurelien Jarno wrote:
Goswin von Brederlow a écrit :
Aurelien Jarno [EMAIL PROTECTED] writes:
One first step would be to keep the current build daemons maintainers
(ie the
On Tue, 30 Jan 2007 20:29:33 +0100, Wouter Verhelst
[EMAIL PROTECTED] wrote:
It's not that it's sacred; it's that w-b uses a Berkeley DB with a
database-level lock for every access (including read-only access); so
giving such access to everyone who asks for it will interfere with
proper buildd
Aurelien Jarno [EMAIL PROTECTED] writes:
One first step would be to keep the current build daemons maintainers
(ie the person who signs the upload), and give and access to some
porters to the wanna-build database. This way they could reschedule
failed builds, add dep-wait, or do binNMU. If I
Goswin von Brederlow a écrit :
Aurelien Jarno [EMAIL PROTECTED] writes:
One first step would be to keep the current build daemons maintainers
(ie the person who signs the upload), and give and access to some
porters to the wanna-build database. This way they could reschedule
failed builds,
On Mon, Jan 29, 2007 at 11:04:12AM +0100, Aurelien Jarno wrote:
wb-i386: ajt, rmurray, troup, vorlon
wb-mips: ajt, rmurray, vorlon
There is no wb-amd64 nor wb-mipsel. I don't know why.
amd64 is included in wb-i386; mipsel is included in wb-mips.
Cheers,
aj
signature.asc
Description: Digital
On Mon, Jan 29, 2007 at 11:04:12AM +0100, Aurelien Jarno wrote:
Goswin von Brederlow a écrit :
Aurelien Jarno [EMAIL PROTECTED] writes:
One first step would be to keep the current build daemons maintainers
(ie the person who signs the upload), and give and access to some
porters to the
On Thu, Jan 25, 2007 at 01:23:35AM +, James Troup wrote:
unilaterally make the decision that they are or are not OK. If it's
the consensus of the release managers and the architecture porting
team that they want to use emulated buildds and/or cross compiling, I
absolutely will not stop
Wouter Verhelst a écrit :
On Thu, Jan 25, 2007 at 01:23:35AM +, James Troup wrote:
unilaterally make the decision that they are or are not OK. If it's
the consensus of the release managers and the architecture porting
team that they want to use emulated buildds and/or cross compiling, I
14 matches
Mail list logo
