azure-iot-sdk-c: Bump to version 2017-06-30
PATCH 1/1 azure-iot-sdk-c: Bump to version 2017-06-30
--- package/azure-iot-sdk-c/azure-iot-sdk-c.mk | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
package/azure-iot-sdk-c/azure-iot-sdk-c.mk +1 -1
@@ -4,7 +4,7 @@ # ################################################################################ -AZURE_IOT_SDK_C_VERSION = 2017-05-05 +AZURE_IOT_SDK_C_VERSION = 2017-06-30 AZURE_IOT_SDK_C_SITE = https://github.com/Azure/azure-iot-sdk-c AZURE_IOT_SDK_C_SITE_METHOD = git AZURE_IOT_SDK_C_GIT_SUBMODULES = YES
Signature · 1 line
2.7.4
Thomas Petazzoni
AppliedPATCH 1/1 azure-iot-sdk-c: Bump to version 2017-06-30
Hello,
Quoted 4 lines · Andr? Hentschel
Signed-off-by Andr? Hentschel <[email protected]>--- package/azure-iot-sdk-c/azure-iot-sdk-c.mk | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Applied to master, thanks.
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com
PATCH 1/1 azure-iot-sdk-c: Bump to version 2017-06-30
In reply to André HentschelHello,
Quoted 4 lines · Andr? Hentschel
Signed-off-by Andr? Hentschel <[email protected]>--- 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
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com
PATCH 1/1 azure-iot-sdk-c: Bump to version 2017-06-30
Hello,
Quoted 7 lines · Thomas Petazzoni
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
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com
PATCH 1/1 azure-iot-sdk-c: Bump to version 2017-06-30
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Thomas" == Thomas Petazzoni <[email protected]> writes:
Hi,
Quoted 2 lines
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.
Signature · 1 line
Bye, Peter Korsgaard
PATCH 1/1 azure-iot-sdk-c: Bump to version 2017-06-30
Thomas, All,
On 2017-07-15 15:22 +0200, Peter Korsgaard spake thusly:
Quoted 4 lines
Quoted 3 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Thomas" == Thomas Petazzoni <[email protected]> writes:
So, I'm wondering what to do. Should I give up testing Buildroot on Debian Squeeze, and move to Debian Wheezy instead?
Quoted 8 lines
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.
Signature · 6 lines
.-----------------.--------------------.------------------.--------------------. | Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: | | +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ | | +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no | | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. | '------------------------------^-------^------------------^--------------------'
PATCH 1/1 azure-iot-sdk-c: Bump to version 2017-06-30
In reply to Peter KorsgaardHello,
Quoted 11 lines · Peter Korsgaard
Quoted 2 lines
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
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com
PATCH 1/1 azure-iot-sdk-c: Bump to version 2017-06-30
Thomas, All,
On 2017-07-16 16:19 +0200, Thomas Petazzoni spake thusly:
Quoted 11 lines · Peter Korsgaard
Quoted 10 lines
Quoted 3 lines
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
Quoted 7 lines
Quoted 2 lines
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.
Signature · 6 lines
.-----------------.--------------------.------------------.--------------------. | Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: | | +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ | | +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no | | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. | '------------------------------^-------^------------------^--------------------'