[Top] [All Lists]

Re: Roll call for porters of architectures in sid and testing (Status up

To: Florian Lohoff <>
Subject: Re: Roll call for porters of architectures in sid and testing (Status update)
From: Ralf Baechle <>
Date: Thu, 19 Sep 2013 16:54:51 +0200
In-reply-to: <>
List-archive: <>
List-help: <>
List-id: linux-mips <>
List-owner: <>
List-post: <>
List-software: Ecartis version 1.0.0
List-subscribe: <>
List-unsubscribe: <>
Original-recipient: rfc822;
References: <> <> <>
User-agent: Mutt/1.5.21 (2010-09-15)
On Thu, Sep 19, 2013 at 04:10:06PM +0200, Florian Lohoff wrote:

> On Thu, Sep 19, 2013 at 03:58:52PM +0200, Ralf Baechle wrote:
> > On Thu, Sep 19, 2013 at 12:31:58PM +0200, Florian Lohoff wrote:
> > 
> > > just a heads up that Mips and Mipsel are 2 architectures in danger
> > > of beeing dropped by Debian if no one steps up as a porter beeing
> > > reachable for addressing architecture specific bugs. 
> > 
> > What components and packages are we talking about?  Are we talking about
> > a fulltime job for a small army of geeks or?
> Its about dealing with architecture specific problems. Looking after
> ICEs, userspace asm stuff for debian packages where they break etc.
> A typical Debian Developer wont know about the mips specifics and 
> needs someone to adress stuff to if the build breaks for architecture
> specific problems.
> Debian has formalizes the release criterias for their architectures
> concerning build architecture, availabibility of hardware and 
> manpower to fix those problems. This is why there needs to be some
> names on the list.
> All the Debian architectures are depending on one another. So if a
> gcc build fails for parisc the new gcc cant propagate to stable/testing.
> So the release managers are keen on quickly fixing those bugs to not
> hold up all architectures progressing.

Sounds like this is really a job for a number of specialists in various

You also mentioned the availability of hardware.  How's the situation
there wrt. to MIPS?


<Prev in Thread] Current Thread [Next in Thread>