Re: [buildd] Implications of DSA-1571-1

2008-05-15 Thread Michael Schmitz
Hi, rebuild. Just need to convince buildd to not listen to the nonexisting wanna-build for the uploads. Let me know how you do that. ;) --- /usr/bin/buildd-mail-orig 2008-05-16 06:39:34.0 +0200 +++ /usr/bin/buildd-mail2008-05-16 06:43:16.0 +0200 @@ -971,6 +971,9 @@

Re: [buildd] Implications of DSA-1571-1

2008-05-15 Thread Michael Schmitz
Hi, I'll schedule those of the -fpie failures I can find on hobbes for Did that get fixed? http://lists.debian.org/debian-68k/2008/05/msg4.html ?? (IOW: not officially ...) rebuild. Just need to convince buildd to not listen to the nonexisting wanna-build for the uploads. Let me kno

Re: [buildd] Implications of DSA-1571-1

2008-05-15 Thread Michael Schmitz
Hi, The only downside I see is spam harvesting and frankly I've got a nice procmail filter that keeps spam from making it to my buildds (buildd mail only knows six messages, everything else must be spam). If I was really clever, I could probably drop such messages earlier. H. If we route al

Re: [buildd] Implications of DSA-1571-1

2008-05-15 Thread Michael Schmitz
Hi, I'm willing to be a manual wanna-build to keep us buildding if ya'll like. With 448 needs-build, I hate to not keep things rolling. If you notice a buildd has run dry, either ping me or grab some packages and let me know which ones. I've already got some of the big ones. A list to get us

Re: [buildd] Implications of DSA-1571-1

2008-05-15 Thread Stephen R Marenka
On Fri, May 16, 2008 at 04:10:20AM +0200, Michael Schmitz wrote: > Hi, > >> I'm willing to be a manual wanna-build to keep us buildding if ya'll >> like. With 448 needs-build, I hate to not keep things rolling. >> >> If you notice a buildd has run dry, either ping me or grab some >> packages and le

Re: [buildd] Implications of DSA-1571-1

2008-05-15 Thread Ingo Juergensmann
On Thu, May 15, 2008 at 11:10:11PM +0200, Michael Schmitz wrote: >> The question is, should we maintain this on a wiki where it can be >> updated? We've potentially got 25 buildds if all of them were up and >> running. I can keep that in a spreadsheet, but it'll bit rot as soon as >> something cha

Re: [buildd] Implications of DSA-1571-1

2008-05-15 Thread Michael Schmitz
Hi, Might as well collect an up-to-date listing for all the buildds. I'm hoping we'll have the opportunity to update keys at buildd.d.o. So I'd like to update all the questions we normally get asked. The question is, should we maintain this on a wiki where it can be updated? We've potentially g

Re: [buildd] Implications of DSA-1571-1

2008-05-15 Thread Michael Schmitz
Pretty normal, isn't it? I'm just glad dropping m68k has really sped up Debian releases, no? Do I see a volunteer here for giving a presentation about this topic in the Debian room at next FOSDEM? As long as it's while I'm in Europe anyway ... Duh, while you guys have FOSDEM I usually have Su

Re: [buildd] Implications of DSA-1571-1

2008-05-15 Thread Stephen R Marenka
Might as well collect an up-to-date listing for all the buildds. I'm hoping we'll have the opportunity to update keys at buildd.d.o. So I'd like to update all the questions we normally get asked. The question is, should we maintain this on a wiki where it can be updated? We've potentially got 25 b

Re: [buildd] Implications of DSA-1571-1

2008-05-15 Thread Wouter Verhelst
On Thu, May 15, 2008 at 02:16:25AM +0200, Michael Schmitz wrote: >>> Well, those machines that were installed before etch, should be safe. Can >>> anyone confirm this? >> >> Only if you have an RSA key. DSA (as in, Digital Signature Algorithm) >> keys should be considered compromised, too, since th

Re: [buildd] Implications of DSA-1571-1

2008-05-15 Thread Geert Uytterhoeven
On Thu, 15 May 2008, Michael Schmitz wrote: > > It seems like we've been building some version of gcc for months. I also > > got qt4-x11 built the day the new one was uploaded. Sigh. > > Pretty normal, isn't it? I'm just glad dropping m68k has really sped up Debian > releases, no? Do I see a volu