From: Denys Dmytriyenko <denis@denix.org>
To: Philip Balister <philip@balister.org>
Cc: openembedded-devel@lists.openembedded.org,
Philip Balister <philip@opensdr.com>
Subject: Re: [meta-oe][rocko][PATCH] protobuf: Fix fetcher failure for rocko.
Date: Wed, 6 Jun 2018 13:43:50 -0400 [thread overview]
Message-ID: <20180606174350.GC19965@denix.org> (raw)
In-Reply-To: <20180604181313.28487-1-philip@balister.org>
On Mon, Jun 04, 2018 at 02:13:13PM -0400, Philip Balister wrote:
> From: Philip Balister <philip@opensdr.com>
Acked-by: Denys Dmytriyenko <denys@ti.com>
Can we get this expedited to rocko, please?
> The 3.4.x branch disappered from the github repo. Remviing the branch
> entry from SRC_URI allows the fetch to succeed. Rocko is the only release
> that has this issue. Sumo and later have 3.5.x.
>
> Signed-off-by: Philip Balister <philip@opensdr.com>
> ---
> meta-oe/recipes-devtools/protobuf/protobuf_3.4.1.bb | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta-oe/recipes-devtools/protobuf/protobuf_3.4.1.bb b/meta-oe/recipes-devtools/protobuf/protobuf_3.4.1.bb
> index fae7c18a1..fe28f475a 100644
> --- a/meta-oe/recipes-devtools/protobuf/protobuf_3.4.1.bb
> +++ b/meta-oe/recipes-devtools/protobuf/protobuf_3.4.1.bb
> @@ -18,7 +18,7 @@ SRCREV = "b04e5cba356212e4e8c66c61bbe0c3a20537c5b9"
>
> PV = "3.4.1+git${SRCPV}"
>
> -SRC_URI = "git://github.com/google/protobuf.git;branch=3.4.x"
> +SRC_URI = "git://github.com/google/protobuf.git"
>
> EXTRA_OECONF += " --with-protoc=echo"
>
> --
> 2.13.6
>
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
prev parent reply other threads:[~2018-06-06 17:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-04 18:13 [meta-oe][rocko][PATCH] protobuf: Fix fetcher failure for rocko Philip Balister
2018-06-06 17:43 ` Denys Dmytriyenko [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=20180606174350.GC19965@denix.org \
--to=denis@denix.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=philip@balister.org \
--cc=philip@opensdr.com \
/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.