Re: [buildd] Access to incoming.d.o?
On Wed, Jan 02, 2008 at 11:27:28AM +0100, Ingo Juergensmann wrote: Hi! It's been a long time since we lost out access to incoming.d.o. Are there any news to this yet? Is there a plan B already? Do we need to escalate this issue finally? With hundreds of packages in needs-build? I don't think this is very urgent. Yes, it needs doing, but we won't die if it doesn't happen. -- Lo-lan-do Home is where you have to wash the dishes. -- #debian-devel, Freenode, 2004-09-22 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [buildd] Access to incoming.d.o?
On Thu, Jan 03, 2008 at 08:35:32PM +0100, Wouter Verhelst wrote: It's been a long time since we lost out access to incoming.d.o. Are there any news to this yet? Is there a plan B already? Do we need to escalate this issue finally? With hundreds of packages in needs-build? I don't think this is very urgent. Yes, it needs doing, but we won't die if it doesn't happen. The sooner, the better. Otherwise we'll be down at some point and still don't have access. -- Ciao...//Fon: 0381-2744150 Ingo \X/ SIP: [EMAIL PROTECTED] gpg pubkey: http://www.juergensmann.de/ij/public_key.asc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
[buildd] Access to incoming.d.o?
Hi! It's been a long time since we lost out access to incoming.d.o. Are there any news to this yet? Is there a plan B already? Do we need to escalate this issue finally? Not that I'm a big fan of escalations, but it seems that nobody cares at the moment about giving us access back. http://lists.debian.org/debian-68k/2007/11/msg00017.html -- Ciao...//Fon: 0381-2744150 Ingo \X/ SIP: [EMAIL PROTECTED] gpg pubkey: http://www.juergensmann.de/ij/public_key.asc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [buildd] Access to incoming.d.o?
Hi, It's been a long time since we lost out access to incoming.d.o. Are there any news to this yet? Is there a plan B already? Do we need to escalate this issue finally? Not that I'm a big fan of escalations, but it seems that nobody cares at the moment about giving us access back. Which machines do currently lack incoming access? Can you please send a new SHA1 password (htpasswd -s IIRC) and the corresponding login for those machines to me? I'l try forwarding them to Joey ... Michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
