Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH RFC] package/glibc: switch to using the maintenance branch
Date: Sun, 22 Oct 2017 17:25:50 +0200	[thread overview]
Message-ID: <20171022152550.GA2599@scaer> (raw)
In-Reply-To: <59e6c3e0-9492-c433-91e0-db4dda9c76e1@gmail.com>

Romain, All,

On 2017-10-22 17:16 +0200, Romain Naour spake thusly:
> Le 21/10/2017 ? 15:12, Romain Naour a ?crit?:
> > Le 21/10/2017 ? 14:22, Yann E. MORIN a ?crit?:
> >> On 2017-10-21 13:31 +0200, Romain Naour spake thusly:
> >>> Le 21/10/2017 ? 12:22, Yann E. MORIN a ?crit?:
> >>>> The version number is obtained with:
> >>>>     $ git describe --match 'glibc-*' --abbrev=40 origin/release/2.26/master
[--SNIP--]
> >>> I can't clone this repo from here using https:
> >>>
> >>> error: Unable to get pack index
> >>> https://sourceware.org/git/glibc.git/objects/pack/pack-f7640727c0f4d6c3389f46d7d6540bbd74f2c136.idx
> >>> error: Failed to connect to sourceware.org port 443: Connection timed out
> >>> (curl_result = 7, http_code = 0, sha1 = eb4488dc33fedcd7cdb5907a82f18f1d300d533b)
> >>> error: Unable to find a1fd1e8a3e17d0f846df142d93aa2af0bc16ced0 under
> >>> https://sourceware.org/git/glibc.git
[--SNIP--]
> It seems that using https://sourceware.org/git/glibc.git is not a reliable.
> The https connection timeout most of the time.
> A lot of build has been broken in my gitlab when I was testing the
> toolchain-builder infra.
> 
> Since git:// can't be used behind a proxy, we have no choice but use
> http://sourceware.org/git/glibc.git

Using http:// is very unreliable for me, while https:// had only some
occasional failures, indeed...

I don't want we swtich to git:// because of proxies, as you explained,
but at the same time we can't rely on cloning from any of http:// or
https://.

I don't know where to  go from there.

Of course, some autobuilders will end up doing the tarball in the end,
and this would eventually land on sources.buildroot.org, and all will be
happy, but this is not acceptable to _rely_ on s.b.o. in the first place,
especially for a pacakge that is still alive (for dead ones, that is
acceptable).

Regards,
Yann E. MORIN.

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

  reply	other threads:[~2017-10-22 15:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-21 10:22 [Buildroot] [PATCH RFC] package/glibc: switch to using the maintenance branch Yann E. MORIN
2017-10-21 11:31 ` Romain Naour
2017-10-21 12:22   ` Yann E. MORIN
2017-10-21 13:12     ` Romain Naour
2017-10-22 15:16       ` Romain Naour
2017-10-22 15:25         ` Yann E. MORIN [this message]
2017-10-23 19:10     ` Romain Naour

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=20171022152550.GA2599@scaer \
    --to=yann.morin.1998@free.fr \
    --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