linux-mips
[Top] [All Lists]

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

To: Ralf Baechle <ralf@linux-mips.org>
Subject: Re: Roll call for porters of architectures in sid and testing (Status update)
From: Florian Lohoff <f@zz.de>
Date: Thu, 19 Sep 2013 17:07:22 +0200
Cc: linux-mips@linux-mips.org
In-reply-to: <20130919145451.GE22468@linux-mips.org>
List-archive: <http://www.linux-mips.org/archives/linux-mips/>
List-help: <mailto:ecartis@linux-mips.org?Subject=help>
List-id: linux-mips <linux-mips.eddie.linux-mips.org>
List-owner: <mailto:ralf@linux-mips.org>
List-post: <mailto:linux-mips@linux-mips.org>
List-software: Ecartis version 1.0.0
List-subscribe: <mailto:ecartis@linux-mips.org?subject=subscribe%20linux-mips>
List-unsubscribe: <mailto:ecartis@linux-mips.org?subject=unsubscribe%20linux-mips>
Organization: rfc822 - pure communication
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <20130919103158.GB7476@pax.zz.de> <20130919135852.GB22468@linux-mips.org> <20130919141006.GB9062@pax.zz.de> <20130919145451.GE22468@linux-mips.org>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.5.20 (2009-06-14)
On Thu, Sep 19, 2013 at 04:54:51PM +0200, Ralf Baechle wrote:
> 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
> fields.
> 
> You also mentioned the availability of hardware.  How's the situation
> there wrt. to MIPS?

Its not about current availability but the possibility to buy new
hardware for whatever reason:

http://lwn.net/Articles/152600/

Flo
-- 
Florian Lohoff                                                 f@zz.de

Attachment: signature.asc
Description: Digital signature

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