Re: [buildd] releasing lenny

Hi, I'll see what I can find in the log archive on buildd.d.o. Not to mention my changes archive :-) I think I've gathered all the ones from the web now. If you will send me (or put somewhere) the ones you listed, that would help. I'll send them ASAP. Michael -- To UNSUBSCRIBE, em

Re: [buildd] releasing lenny

On Sat, Sep 06, 2008 at 06:57:28AM +0200, Michael Schmitz wrote: > Hi, > >>> Regarding archive administration - I suppose Stephen has access to that >>> as well? I would not mind trying my hand at it either if more backup is >>> needed. >> >> At the moment, all I have access to is buildd_m68k. I'll

Re: [buildd] releasing lenny

Hi, We've also got to find changes for the list at . For whatever reason they are keeping us from syncing the archive. Otherwise we'll have to rebuild them. I'm guessing they aren't on merkel, but I haven't looked yet. At least some of them

Re: [buildd] releasing lenny

Hi, Regarding archive administration - I suppose Stephen has access to that as well? I would not mind trying my hand at it either if more backup is needed. At the moment, all I have access to is buildd_m68k. I'll happily share that, send me an ssh key. :) I'll send the keys q650 and hobbes u

Re: [buildd] releasing lenny

On Fri, Sep 05, 2008 at 07:09:20AM +0200, Michael Schmitz wrote: > Hi, > >> No, no binaries from lenny will be going back into unstable to make >> sure. If it becomes an issue, it isn't very difficult to resign the >> changes files after the fact. > > If you say so - no further objections from my p

Re: [buildd] releasing lenny

Hi, No, no binaries from lenny will be going back into unstable to make sure. If it becomes an issue, it isn't very difficult to resign the changes files after the fact. If you say so - no further objections from my part. Regarding archive administration - I suppose Stephen has access to that

Re: [buildd] releasing lenny

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 No, no binaries from lenny will be going back into unstable to make sure. If it becomes an issue, it isn't very difficult to resign the changes files after the fact. Michael -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: http

Re: [buildd] releasing lenny

Hi Michael, It's just a pain getting everything resigned by a DD and I don't use a buildd for most of these builds so there are no build logs ATM anyway. I agree it's a pain - I was wondering whether it's worth the pain myself, that's why I asked the question. Build logs are not the issue - t

Re: [buildd] releasing lenny

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 It's just a pain getting everything resigned by a DD and I don't use a buildd for most of these builds so there are no build logs ATM anyway. I still need to make changes to dports w-b, and these binaries will never be released with Debian. I am a NM,

Re: [buildd] releasing lenny

Hi, On Thu, 4 Sep 2008, Stephen R Marenka wrote: Michael Casadevall believes we can stage lenny on dports. However, he'll need upload rights to make that happen. Per the Kiel meeting, we established that dd's would need to control the archive and machines. Since our lenny will never be part o