All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [RFC PATCH 6/6] ca-certificates: update to 20180409
Date: Wed, 29 Aug 2018 08:38:24 -0700	[thread overview]
Message-ID: <CAMKF1sqNBpbLdnpMOHLG9zf6w2V85_X4L7Hj3OLCr3mmZ+fAvA@mail.gmail.com> (raw)
In-Reply-To: <CANNYZj8hsVXLe0q59PvMeuVb5=7DPJsndi1r6EqE8bC8RMc3sA@mail.gmail.com>

On Wed, Aug 29, 2018 at 7:47 AM Alexander Kanavin
<alex.kanavin@gmail.com> wrote:
>
> 2018-08-29 16:30 GMT+02:00 Khem Raj <raj.khem@gmail.com>:
>
> >> -SRCREV = "34b8e19e541b8af4076616b2e170c7a70cdaded0"
> >> +SRCREV = "dbbd11e56af93bb79f21d0ee6059a901f83f70a5"
> >
> > It fails in do_patch for me.
> > Patch 0002-update-ca-certificates-use-SYSROOT.patch does not apply
> > (enforce with -f)
>
> Works for me though. I just did a cleansstate and build to double
> check. Can you try on plain poky master please?

bitbake ca-certificates -ccleanall && bitbake ca-certificates
worked, seems a wrong fetch sometimes, I wish git fetcher has some
sort of checksumming as well.


  reply	other threads:[~2018-08-29 15:38 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-28 10:23 [RFC PATCH 0/6] openssl 1.1.1 update Alexander Kanavin
2018-08-28 10:23 ` [RFC PATCH 1/6] openssl: rename openssl 1.0.x to openssl10 and make openssl 1.1.x the default version Alexander Kanavin
2018-09-04 19:12   ` Martin Jansa
2018-09-04 20:35     ` Richard Purdie
2018-09-04 20:43       ` Khem Raj
2018-09-04 22:58         ` richard.purdie
2018-09-05  1:49           ` Khem Raj
2018-09-05  4:08             ` Andre McCurdy
2018-09-05  4:54               ` Khem Raj
2018-09-05  7:14                 ` Alexander Kanavin
2018-09-05  8:53                   ` Martin Jansa
2018-09-05 14:45                     ` Richard Purdie
2018-09-05 15:15                       ` Khem Raj
2018-09-05 15:45                         ` Andre McCurdy
2018-09-05 15:55                           ` Martin Jansa
2018-09-10 17:54                             ` Andre McCurdy
2018-09-10 18:09                               ` Khem Raj
2018-09-13  1:43   ` Andre McCurdy
2018-08-28 10:23 ` [RFC PATCH 2/6] cryptodev-tests: port to openssl 1.1 Alexander Kanavin
2018-09-04 20:38   ` Andre McCurdy
2018-09-05 14:15     ` Alexander Kanavin
2018-08-28 10:23 ` [RFC PATCH 3/6] openssl: update to 1.1.1 Alexander Kanavin
2018-09-03 22:53   ` Khem Raj
2018-09-04  3:17     ` Andre McCurdy
2018-09-04  4:26       ` Khem Raj
2018-08-28 10:23 ` [RFC PATCH 4/6] libressl: add a recipe to support openssh Alexander Kanavin
2018-08-28 10:23 ` [RFC PATCH 5/6] openssh: depend on libressl Alexander Kanavin
2018-08-28 10:23 ` [RFC PATCH 6/6] ca-certificates: update to 20180409 Alexander Kanavin
2018-08-29 14:30   ` Khem Raj
2018-08-29 14:47     ` Alexander Kanavin
2018-08-29 15:38       ` Khem Raj [this message]
2018-08-31  6:22 ` [RFC PATCH 0/6] openssl 1.1.1 update Khem Raj
2018-08-31  9:30   ` Alexander Kanavin
2018-08-31  9:38     ` Alexander Kanavin
2018-09-01  8:16       ` Khem Raj
2018-09-01  8:20 ` Khem Raj
2018-09-01  8:20   ` [OE-core] " Khem Raj

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=CAMKF1sqNBpbLdnpMOHLG9zf6w2V85_X4L7Hj3OLCr3mmZ+fAvA@mail.gmail.com \
    --to=raj.khem@gmail.com \
    --cc=alex.kanavin@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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.