On Fri, Mar 10, 2006 at 10:43:20PM +0100, Martin Schulze wrote: > I must not do that. Being a system administrator is not a green light > for hacking in arbitrary services maintained by another team or > person. This has been a rule for Debian admin for a long time and it > actually grants that those who maintain a service really maintain it > and ar not confronted with arbitrary changes made by others. I don't really think that makes sense here -- the security.d.o stuff is the security team's; if you guys want it not managed by ftpmaster, that's your choice. > Thus, I must not fiddle with the DAK installation on either spohr > or klecker unless ftpmaster give their ok for that. And you already do fiddle with the dak installation on klecker, at least when unwanted uploads build up and no one gets rid of them for you :) > However, hell freezes > when the infrastructure is not working and those responsible for it > don't respond and react. Maybe you remember the disaster that > happened when sarge was released. Sure; I remember it wasn't trivial to get it working for sarge at release time, when we tried getting things to work it took a while before you could test it, then you did that by munging stuff around in ways that we didn't expect which then didn't work, and then you were busy at LinuxTag; and each time anything broke we only found out about it later by reading your blog. That wasn't fun for anyone. This time round the testing-security guys should be putting up with the pain of making sure the stuff works for etch well before the release, and it shouldn't be a problem in the first place. Cheers, aj
Attachment:
signature.asc
Description: Digital signature