azure-iot-sdk-c: Bump to version 2017-06-30

Signed-off-by: André Hentschel <nerv@dawncrow.de>
---
 package/azure-iot-sdk-c/azure-iot-sdk-c.mk | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Hello,

On Wed,  5 Jul 2017 19:53:21 +0200, André Hentschel wrote:
> Signed-off-by: André Hentschel <nerv@dawncrow.de>
> ---
>  package/azure-iot-sdk-c/azure-iot-sdk-c.mk | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Applied to master, thanks.

Thomas

Hello,

On Wed,  5 Jul 2017 19:53:21 +0200, André Hentschel wrote:
> Signed-off-by: André Hentschel <nerv@dawncrow.de>
> ---
>  package/azure-iot-sdk-c/azure-iot-sdk-c.mk | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

This package is causing a large number of timeouts, apparently due to
the fetch of submodules failing. It only happens on my autobuilder
instance it seems:

  http://autobuild.buildroot.net/?reason=azure-iot-sdk-c-2017-06-30

Is there something that can be done about this?

Thanks,

Thomas

Hello,

On Sat, 15 Jul 2017 12:09:54 +0200, Thomas Petazzoni wrote:

> This package is causing a large number of timeouts, apparently due to
> the fetch of submodules failing. It only happens on my autobuilder
> instance it seems:
> 
>   http://autobuild.buildroot.net/?reason=azure-iot-sdk-c-2017-06-30
> 
> Is there something that can be done about this?

So, the issue is that I am (intentionally) using a very old Linux
distribution for this autobuilder instance, and the distro is so old
that OpenSSL+ca-certificates are no longer compatible with the
requirements of https:// on github.com. But instead of failing with an
error, it just remains stuck forever.

An "openssl s_client -connect" test clearly reveals that it's never
going to connect to github.com from my old distro.

So, I'm wondering what to do. Should I give up testing Buildroot on
Debian Squeeze, and move to Debian Wheezy instead?

I could perhaps backport openssl+ca-certificates, but what's the point
of testing such an old distro, if random packages have anyway to be
upgraded for Buildroot to work correctly?

Arnout, Yann, Peter, what do you think?

I've also Cc'ed Thomas DS, who is known to use Buildroot on really old
Linux distros. Thomas: what are the oldest distro you're still running
Buildroot on? If it's some RHEL distro, what is the closest Debian
version? Do you get openssl/ca-certificates updates on this RHEL, which
allows such machines to continue to connect over HTTPS to modern web
sites?

Best regards,

Thomas

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:

Hi,

 > 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.

Thomas, All,

On 2017-07-15 15:22 +0200, Peter Korsgaard spake thusly:
> >>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
>  > 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.

We can do our best to support older distros, and not break things on
purpose, but when time has come, we should not refrain from requiring a
more uop-to-date system.

If we accidentally break something, interested parties can try to fix it
and send patches if that is fixable. If that is not fixable, then there
is not much we can do.

Except add even more host packages and become a distro... :-/

So, my position is you update your autobuilder.

Regards,
Yann E. MORIN.

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, All,

On 2017-07-16 16:19 +0200, Thomas Petazzoni spake thusly:
> 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.

Thank you Thomas for having run this old distro for the autobuilders for
so long, and most importantly for bringing in patches to fix those
autobuild failures.

Thanks! :-)

So long, Squeeze, and thanks for all the fish! :-)

Regards,
Yann E. MORIN.