Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Fwd: [autobuild.buildroot.net] Your build results for 2019-05-08
Date: Thu, 9 May 2019 21:43:48 +0200	[thread overview]
Message-ID: <20190509214348.1d45d19e@windsurf.home> (raw)
In-Reply-To: <CAMQcK5J5YUv4nYfdFpZhRnO6uy+5i6Rpnxa6nGXcZNQDTA3zGw@mail.gmail.com>

Hello Ryan,

On Thu, 9 May 2019 08:55:43 -0500
Ryan Barnett <ryan.barnett@rockwellcollins.com> wrote:

> [following]
> --2019-05-08 14:47:04--
> https://sourceforge.net/projects/atftp/files/atftp-0.7.2.tar.gz
> Connecting to sourceforge.net (sourceforge.net)|216.105.38.13|:443... connected.
> GnuTLS: A TLS fatal alert has been received.
> Unable to establish SSL connection.
> 
> These were both run on the autobuilder from Thomas so it may be a
> build server configuration issue.

It is a bug in the old version of wget/gnutls that is used in my old
Debian Wheezy chroot. It disappears once the tarball is cached in
sources.buildroot.net.

I should probably update my chroot to Debian Jessie, now that Debian
Wheezy is completely EOLed.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

      reply	other threads:[~2019-05-09 19:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20190509060040.D56B7604B6@crulimr01.rockwellcollins.com>
2019-05-09 13:55 ` [Buildroot] Fwd: [autobuild.buildroot.net] Your build results for 2019-05-08 Ryan Barnett
2019-05-09 19:43   ` Thomas Petazzoni [this message]

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=20190509214348.1d45d19e@windsurf.home \
    --to=thomas.petazzoni@bootlin.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