All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] glib-networking: depend on target ca-certificates.
Date: Wed, 2 Jan 2019 22:01:58 +0100	[thread overview]
Message-ID: <20190102210158.GM23435@scaer> (raw)
In-Reply-To: <20190102205409.4f9d9ec6@windsurf>

Thomas, All,

On 2019-01-02 20:54 +0100, Thomas Petazzoni spake thusly:
> On Wed, 2 Jan 2019 18:17:04 +0100, Yann E. MORIN wrote:
> > Thomas: maybe we can look at updating it instead of trying to fix it?
> Is there a released/stable, non-development version of glib-networking
> that contains the commit fixing the issue ?

There's 2.58.0 which contains the change that no longer requires the
path to exist at build time.

Adam, are the versions tightly coupled between glib-networking and glib?
I.e, is it possible to use glib-networking-2.58.0 with glib-2.56.3, or
do we have to bump both simultaneously?

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:[~2019-01-02 21:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-02 16:54 [Buildroot] [PATCH 1/1] glib-networking: depend on target ca-certificates aduskett at gmail.com
2019-01-02 17:17 ` Yann E. MORIN
2019-01-02 19:54   ` Thomas Petazzoni
2019-01-02 21:01     ` Yann E. MORIN [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=20190102210158.GM23435@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.