Re: m68k release future
On Fri, Oct 27, 2006 at 05:55:13PM +0200, Michael Schmitz wrote:
> On Fri, 27 Oct 2006, Anthony Towns wrote:
> > > Isn't it going to be so that we'd be able to do our own
> > > arch-specific NMUs in both cases? Or is it in both cases going to be a
> > > matter of deciding which package will be part of the distribution and
> > > which not?
> >
> > Well, mostly, I was hoping you'd tell me what you want to do for that...
>
> >From my POV, mainly the former. Plus reordering the build queue based on
> what packages make the most sense to have, both from a dependency and
> build dependency perspective, and from a 'might actually be useful for
> m68k' perspective. In that order of priorities.
>
> > > The point is that if we can actually get something out that is as close
> > > to etch as possible, that we don't have to redo everything the security
> > > team is doing already anymore.
> >
> > > If we do our own snapshots and we do want security support, we would be
> > > pretty much on our own. That's not what I'd like to see.
> >
> > I'd like to see snapshots for testing anyway, and Joey Hess has
> > expressed a similar interest, among others. We haven't managed it yet
> > though, obviously. The unembargoed security team are doing some work
> > at supporting testing again atm too, btw.
>
> Well, seeing that you're at least as busy as everyone else, I'd prefer to
> get as close to released etch as possible, to be able to piggyback on the
> security team's work. Not to mention to prevent bug rot in general.
>
> In summary: I should rather try for testing-m68k, and try to let that not
> fall behind too much. If things look up, get as close to the other archs
> as we can (and I'd appreciate the option to rejoin etch if we can make
> it). Get a snapshot 'etch-m68k' around the time etch is released, if we
> cannot get close enough.
Yes, I would think that's the best way to move forward at this point,
too.
--
<Lo-lan-do> Home is where you have to wash the dishes.
-- #debian-devel, Freenode, 2004-09-22
Reply to: