On 18/08/18 11:01, Roger Shimizu wrote:
On Sat, Aug 18, 2018 at 12:33 PM, Hideki Yamane wrote:
Hi,
So it'll be super great if you (or your boss) can kindly sponsor some
armel/armhf hardwares that support to install 4GB memory.
From DebConf18 seesion "Building a Debian Derivative: Lessons L
On Sat, Aug 18, 2018 at 07:01:39PM +0900, Roger Shimizu wrote:
>...
> Yes. In latest ARM BoF of DebConf18, Steve (93sam) informed us that
> he's trying to rebuild all the armhf archive on arm64 box.
> When that's done, we will get to know how many packages need to fix.
> If the number of those pack
On Sat, Aug 18, 2018 at 12:33 PM, Hideki Yamane wrote:
> Hi,
>
>> So it'll be super great if you (or your boss) can kindly sponsor some
>> armel/armhf hardwares that support to install 4GB memory.
>
> From DebConf18 seesion "Building a Debian Derivative: Lessons Learned
> and Solutions Found" by
Hi,
> So it'll be super great if you (or your boss) can kindly sponsor some
> armel/armhf hardwares that support to install 4GB memory.
From DebConf18 seesion "Building a Debian Derivative: Lessons Learned
and Solutions Found" by Alex Doyle from Cumulus Network, they run
"Jessie on Chromebook"
> On Jul 24, 2018, at 11:20 AM, Steve McIntyre wrote:
>
> [ Dropped cc to debian-ports etc., switched to debian-arm instead ]
>
>> As for the hardware, you should watch out for hardware with ARM Cortex Cores.
>> Alternatively, X-Gene 1. ThunderX, ThunderX2 and Centriq are definitely not
>> su
[ Dropped cc to debian-ports etc., switched to debian-arm instead ]
On Mon, Jul 23, 2018 at 04:11:06PM +0200, John Paul Adrian Glaubitz wrote:
>Hi Roger!
>
>On 07/23/2018 10:42 AM, Roger Shimizu wrote:
>> I talked to a few people about keeping armel in buster, during 1st and
>> 2nd day in debcamp.
Hi Roger!
On 07/23/2018 10:42 AM, Roger Shimizu wrote:
> I talked to a few people about keeping armel in buster, during 1st and
> 2nd day in debcamp.
> Seems the blocker is just the buildd server hardware, and memory size it has.
According to my colleague Alex Graf at SUSE, you can definitely bui
Dear armel/armhf shakeholders,
I talked to a few people about keeping armel in buster, during 1st and
2nd day in debcamp.
Seems the blocker is just the buildd server hardware, and memory size it has.
On Fri, Jun 29, 2018 at 7:04 PM, W. Martin Borgert wrote:
>
> Quoting Uwe Kleine-König :
>>
>> I
> On Jun 29, 2018, at 9:50 AM, Jonathan Wiltshire wrote:
>
>> On Fri, Jun 29, 2018 at 11:04:26PM +0900, Roger Shimizu wrote:
>> I see armel is already not a candidate for buster [0].
>> So it seems we can discuss armhf, but no armel at all.
>> I don't agree with this idea.
>> And I think we sh
On Fri, Jun 29, 2018 at 11:04:26PM +0900, Roger Shimizu wrote:
> I see armel is already not a candidate for buster [0].
> So it seems we can discuss armhf, but no armel at all.
> I don't agree with this idea.
> And I think we should treat armel and armhf equally.
Please review the mail which origi
On Fri, Jun 29, 2018 at 11:00:59AM -0400, Gene Heskett wrote:
> hijacking your thread, my apologies:
Rather than apologising for hijacking a thread in the same breath as doing
so, please simply avoid doing so in the first place. The set of lists
in your CC are *really* not appropriate for such a m
On Fri, Jun 29, 2018 at 3:28 PM, Samuel Thibault wrote:
> Roger Shimizu, le ven. 29 juin 2018 23:04:26 +0900, a ecrit:
>> On Fri, Jun 29, 2018 at 10:04 PM, Uwe Kleine-König
>> wrote:
>> > On 06/29/2018 11:23 AM, Julien Cristau wrote:
>> >> 2G is also way too little memory these days for a new bu
On Friday 29 June 2018 10:28:33 Samuel Thibault wrote:
> Roger Shimizu, le ven. 29 juin 2018 23:04:26 +0900, a ecrit:
> > On Fri, Jun 29, 2018 at 10:04 PM, Uwe Kleine-König
> >
> > wrote:
> > > On 06/29/2018 11:23 AM, Julien Cristau wrote:
> > >> 2G is also way too little memory these days for a
Roger Shimizu, le ven. 29 juin 2018 23:04:26 +0900, a ecrit:
> On Fri, Jun 29, 2018 at 10:04 PM, Uwe Kleine-König
> wrote:
> > On 06/29/2018 11:23 AM, Julien Cristau wrote:
> >> 2G is also way too little memory these days for a new buildd.
> >
> > Then the machine is out, the amount of RAM isn't u
On Fri, Jun 29, 2018 at 10:04 PM, Uwe Kleine-König
wrote:
> Hello Julien,
>
> On 06/29/2018 11:23 AM, Julien Cristau wrote:
>>> If the concerns are mostly about the hardware not being rackable, there
>>> is a rackable NAS by Netgear:
>>>
>>>
>>> https://www.netgear.com/business/products/stor
Hello Julien,
On 06/29/2018 11:23 AM, Julien Cristau wrote:
>> If the concerns are mostly about the hardware not being rackable, there
>> is a rackable NAS by Netgear:
>>
>>
>> https://www.netgear.com/business/products/storage/readynas/RN2120.aspx#tab-techspecs
>>
>> with an armhf cpu. Not s
On Fri, Jun 29, 2018 at 1:12 PM, John Paul Adrian Glaubitz
wrote:
> On 06/29/2018 01:42 PM, Luke Kenneth Casson Leighton wrote:
>>> I think that building on arm64 after fixing the bug in question is the
>>> way to move forward. I'm surprised the bug itself hasn't been fixed yet,
>>> doesn't speak
On 06/29/2018 01:42 PM, Luke Kenneth Casson Leighton wrote:
>> I think that building on arm64 after fixing the bug in question is the
>> way to move forward. I'm surprised the bug itself hasn't been fixed yet,
>> doesn't speak for ARM.
>
> if you mean ARM hardware (OoO), it's too late. systems a
On Fri, Jun 29, 2018 at 12:06 PM, John Paul Adrian Glaubitz
wrote:
> On 06/29/2018 10:41 AM, Luke Kenneth Casson Leighton wrote:
>> On Fri, Jun 29, 2018 at 8:16 AM, Uwe Kleine-König
>> wrote:
>>
In short, the hardware (development boards) we're currently using to
build armel and armhf
On 06/29/2018 10:41 AM, Luke Kenneth Casson Leighton wrote:
> On Fri, Jun 29, 2018 at 8:16 AM, Uwe Kleine-König
> wrote:
>
>>> In short, the hardware (development boards) we're currently using to
>>> build armel and armhf packages aren't up to our standards, and we
>>> really, really want them t
Quoting Uwe Kleine-König :
If the concerns are mostly about the hardware not being rackable, there
is a rackable NAS by Netgear:
https://www.netgear.com/business/products/storage/readynas/RN2120.aspx#tab-techspecs
This seems to be out of stock and discontinued, unfortunately.
Anyway,
[s/debian-ports/debian-arm/]
On 06/29/2018 09:16 AM, Uwe Kleine-König wrote:
> Hello,
>
> On Wed, Jun 27, 2018 at 08:03:00PM +, Niels Thykier wrote:
>> armel/armhf:
>>
>>
>> * Undesirable to keep the hardware running beyond 2020. armhf VM
>>support uncertain. (DSA)
>>-
On Fri, Jun 29, 2018 at 8:16 AM, Uwe Kleine-König
wrote:
> Hello,
>
> On Wed, Jun 27, 2018 at 08:03:00PM +, Niels Thykier wrote:
>> armel/armhf:
>>
>>
>> * Undesirable to keep the hardware running beyond 2020. armhf VM
>>support uncertain. (DSA)
>>- Source: [DSA Sprint
Hello,
On Wed, Jun 27, 2018 at 08:03:00PM +, Niels Thykier wrote:
> armel/armhf:
>
>
> * Undesirable to keep the hardware running beyond 2020. armhf VM
>support uncertain. (DSA)
>- Source: [DSA Sprint report]
>
> [DSA Sprint report]:
> https://lists.debian.org/debian-p
24 matches
Mail list logo
