Re: Etch release and m68k

[Bill Allombert <Bill.Allombert@math.u-bordeaux1.fr>]

On Fri, Feb 09, 2007 at 03:14:31PM +0100, Wouter Verhelst wrote:
> On Thu, Feb 08, 2007 at 10:30:16PM +0100, Bill Allombert wrote:
> > On Thu, Feb 08, 2007 at 01:33:27PM -0600, Stephen R Marenka wrote:
> > > On Wed, Feb 07, 2007 at 07:11:43PM +0100, Bill Allombert wrote:
> > > > Dear Debian 68k porters,
> > > > 
> > > > Etch now include gcc-4.1 4.1.1-21 for all plateform. 
> > > > As far as I am concerned this was the last blocking bug for releasing
> > > > m68k with Etch (gcc-4.1 4.1.1-17 was too broken to make a release
> > > > worthwhile). Any other known problem to fix before a formal request ?
> > > 
> > > When m68k looks like all the other archs at 
> > > <http://ftp-master.debian.org/testing/testing_probs.html> then it might
> > > be worth a go.
> > 
> >      * amd64:19
> >      * hppa:204
> >      * i386:13
> >      * powerpc:25
> >      * arm:113
> >      * ia64:84
> >      * s390:197
> >      * sparc:145
> >      * mips:185
> >      * mipsel:207
> >      * alpha:193
> >      * m68k:249
> > 
> > Well what can be done about that ?
> > Ask the ftp-master to remove some uninstallable binaries?
> 
> Build missing binaries, I think, and upload to testing-proposed-updates
> 
> Best ask the release team what the best way to fix that issue is.

According to my understanding, this is performed automatically by the
testing-proposed-updates buildd. Maybe some packages need to be
requeued ?

Cheers,
-- 
Bill. <ballombe@debian.org>

Imagine a large blue swirl here.