From: Florian Lohoff <f@zz.de>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: linux-mips@linux-mips.org
Subject: Re: Roll call for porters of architectures in sid and testing (Status update)
Date: Thu, 19 Sep 2013 17:07:22 +0200 [thread overview]
Message-ID: <20130919150722.GC28967@pax.zz.de> (raw)
In-Reply-To: <20130919145451.GE22468@linux-mips.org>
[-- Attachment #1: Type: text/plain, Size: 1886 bytes --]
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 #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2013-09-19 15:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-19 10:31 Fwd: Roll call for porters of architectures in sid and testing (Status update) Florian Lohoff
2013-09-19 13:58 ` Ralf Baechle
2013-09-19 14:10 ` Florian Lohoff
2013-09-19 14:54 ` Ralf Baechle
2013-09-19 15:07 ` Florian Lohoff [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130919150722.GC28967@pax.zz.de \
--to=f@zz.de \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.