Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] azure-iot-sdk-c: Bump to version 2017-06-30
Date: Sun, 16 Jul 2017 16:19:01 +0200	[thread overview]
Message-ID: <20170716161901.5a88cc27@windsurf> (raw)
In-Reply-To: <87lgnpal7b.fsf@dell.be.48ers.dk>

Hello,

On Sat, 15 Jul 2017 15:22:48 +0200, Peter Korsgaard wrote:

>  > So, I'm wondering what to do. Should I give up testing Buildroot on
>  > Debian Squeeze, and move to Debian Wheezy instead?  
> 
> With stretch out, I indeed think it makes sense to move away from
> squeeze. According to wikipedia squeeze is no longer supported (since
> Feb 2016):
> 
> https://en.wikipedia.org/wiki/Debian_version_history#Release_table
> 
> In general, I don't think it makes sense to test on any distribution no
> longer supported by their upstream.

Following your feedback and Yann's feedback, I've updated my chroot
from Squeeze to Wheezy. I've checked, and now Git clones from
github.com are working, as are wget downloads from cdn.kernel.org. This
should hopefully avoid a lot of bogus download failures.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  parent reply	other threads:[~2017-07-16 14:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-05 17:53 [Buildroot] [PATCH] azure-iot-sdk-c: Bump to version 2017-06-30 André Hentschel
2017-07-06 21:26 ` Thomas Petazzoni
2017-07-15 10:09 ` Thomas Petazzoni
2017-07-15 10:44   ` Thomas Petazzoni
2017-07-15 13:22     ` Peter Korsgaard
2017-07-16  8:15       ` Yann E. MORIN
2017-07-16 14:19       ` Thomas Petazzoni [this message]
2017-07-16 14:59         ` Yann E. MORIN

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=20170716161901.5a88cc27@windsurf \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox