On Sat, 2016-10-01 at 15:48 +0200, John Paul Adrian Glaubitz wrote:
> On 10/01/2016 02:17 PM, Ben Hutchings wrote:
> >
> > >
> > > This isn't the case for PowerPC32 where upstream development is still very
> > > active because it's part of the PowerPC kernel which is maintained by
> > > IBM.
> >
On Fri, 2016-09-30 at 22:34 +0200, John Paul Adrian Glaubitz wrote:
> On 09/30/2016 09:04 PM, Niels Thykier wrote:
> >
> > As for "porter qualification"
> > =
> >
> > We got burned during the Jessie release, where a person answered the
> > roll call for sparc and we ke
On Sat, 2016-10-01 at 02:28 +0200, Adam Borowski wrote:
> On Fri, Sep 30, 2016 at 11:01:55PM +0200, Mathieu Malaterre wrote:
[...]
> > I have not heard from the ppc64el porters, but I suspect ppc64 will
> > not be a release arch. So you need to take into consideration that for
> > powerpc to remain
On Sat, Oct 1, 2016 at 2:28 AM, Adam Borowski wrote:
> On Fri, Sep 30, 2016 at 11:01:55PM +0200, Mathieu Malaterre wrote:
>> On Fri, Sep 30, 2016 at 10:34 PM, John Paul Adrian Glaubitz
>> wrote:
>> [...]
>> > On the other hand, some packages dropped support for PowerPC32 like Mono
>> > but this i
On Jun 5, 2016, at 1:35 PM, Vagrant Cascadian wrote:
> On 2016-06-05, Gaudenz Steinlin wrote:
>> I have the same problem with my Cubox-i 4x4. Is there any progress on
>> this?
>
> Not the I'm aware of.
>
> Currently, the one-liner I patch just hard-codes a different ram
> configuration. In my
5 matches
Mail list logo
