[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [buildd] releasing lenny

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, which means that I should be
a DD soon (I'm mostly done with T&S 1, just need to write a manpage),
likely before we even have TLS in the kernel. Before we even
considered staging on d-ports, I was handling building and lenny
archive administraion on

Now if I don't have upload rights, I'm still willing to help, it just
becomes rather frustating to do so.

Version: GnuPG v1.4.9 (GNU/Linux)
Comment: http://getfiregpg.org


On Thu, Sep 4, 2008 at 4:21 PM, Michael Schmitz
<schmitz@biophys.uni-duesseldorf.de> wrote:
> 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 of debian. I don't see a risk to the
>> archive, so long as his uploads are restricted to lenny.
> What we risk in this manner is arguing that our lenny packages should be
> considered untainted when it comes to re-including m68k in Debian. That's
> only going to be a problem if we succeed in catching up while lenny packages
> are still potentially useful.
> (It's also a problem if we are not barred from re-releasing by other rules
> anyway - think availability of HW, fewer than x buildds, whatever ftpmaster
> comes up with. We've been there.)
> If you see a chance of reapplying during the next release cycle, we would
> need to have all lenny uploads signed by one of us. Can this be handled in a
> similar manner like uploads by people still in the new maintainer process?
> OTOH, I'm complicating things without need here. We'll burn that bridge when
> we get there.
>        Michael
> --
> To UNSUBSCRIBE, email to debian-68k-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmaster@lists.debian.org

Reply to: