[PATCH] file: update SRCREV for 5.30 to fix fetch fail on missing commit

[PATCH] file: update SRCREV for 5.30 to fix fetch fail on missing commit

[Paul Gortmaker]

Machines that cloned a while ago will have the commit, but new
deployments won't because it seems the upstream changed/rebased
and the old commit ID has been garbage-collected away.  Hence
the fetch fails to check out the named commit ID.

Both the old (gone) commit, and the "new" commit show the same
dates and commit log and point at 5.30, so hopefully this is
the right thing to do.  A git diff of the two seems to only show
a blanket uprev of CVS tags and deletion of a couple autogen'd
files, and no real source changes.

Cc: Christos Zoulas <christos@zoulas.com>
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>

diff --git a/meta/recipes-devtools/file/file_5.30.bb b/meta/recipes-devtools/file/file_5.30.bb
index 0998fcfa8990..112bf105781e 100644
--- a/meta/recipes-devtools/file/file_5.30.bb
+++ b/meta/recipes-devtools/file/file_5.30.bb
@@ -19,7 +19,7 @@ SRC_URI = "git://github.com/file/file.git \
         file://0001-Add-P-prompt-into-Usage-info.patch \
         "
 
-SRCREV = "79814950aafb81ecd6a910c2a8a3b8ec12f3e4a6"
+SRCREV = "3050419355566d2a96c5be97fef0ffae097bbb96"
 S = "${WORKDIR}/git"
 
 inherit autotools
-- 
2.11.1

Re: [PATCH] file: update SRCREV for 5.30 to fix fetch fail on missing commit

[Burton, Ross]

[-- Attachment #1: Type: text/plain, Size: 352 bytes --]

On 16 March 2017 at 18:42, Paul Gortmaker <paul.gortmaker@windriver.com>
wrote:

> Machines that cloned a while ago will have the commit, but new
> deployments won't because it seems the upstream changed/rebased
> and the old commit ID has been garbage-collected away.  Hence
> the fetch fails to check out the named commit ID.
>

<explodes>

[-- Attachment #2: Type: text/html, Size: 786 bytes --]

Re: [PATCH] file: update SRCREV for 5.30 to fix fetch fail on missing commit

[Denys Dmytriyenko]

We would need to do the same for past releases - morty/5.28, krogoth/5.25, jethro/5.24...


On Thu, Mar 16, 2017 at 02:42:14PM -0400, Paul Gortmaker wrote:
> Machines that cloned a while ago will have the commit, but new
> deployments won't because it seems the upstream changed/rebased
> and the old commit ID has been garbage-collected away.  Hence
> the fetch fails to check out the named commit ID.
> 
> Both the old (gone) commit, and the "new" commit show the same
> dates and commit log and point at 5.30, so hopefully this is
> the right thing to do.  A git diff of the two seems to only show
> a blanket uprev of CVS tags and deletion of a couple autogen'd
> files, and no real source changes.
> 
> Cc: Christos Zoulas <christos@zoulas.com>
> Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
> 
> diff --git a/meta/recipes-devtools/file/file_5.30.bb b/meta/recipes-devtools/file/file_5.30.bb
> index 0998fcfa8990..112bf105781e 100644
> --- a/meta/recipes-devtools/file/file_5.30.bb
> +++ b/meta/recipes-devtools/file/file_5.30.bb
> @@ -19,7 +19,7 @@ SRC_URI = "git://github.com/file/file.git \
>          file://0001-Add-P-prompt-into-Usage-info.patch \
>          "
>  
> -SRCREV = "79814950aafb81ecd6a910c2a8a3b8ec12f3e4a6"
> +SRCREV = "3050419355566d2a96c5be97fef0ffae097bbb96"
>  S = "${WORKDIR}/git"
>  
>  inherit autotools
> -- 
> 2.11.1
> 
> -- 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core