Skip to contentSkip to conversation

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

PATCH In review Paul Gortmaker 3 participants 3 messages Mar 16, 2017 – Mar 17, 2017

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 file: update SRCREV for 5.30 to fix fetch fail on missing commit

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.

meta/recipes-devtools/file/file_5.30.bb +1 -1
index 0998fcfa8990..112bf105781e 100644
@@ -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
Signature · 1 line
2.11.1
#1 lore raw
Quoted 5 lines · 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.

<explodes>

#2 lore raw
In reply to Paul Gortmaker

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

Quoted 35 lines · 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.

meta/recipes-devtools/file/file_5.30.bb +1 -1
index 0998fcfa8990..112bf105781e 100644
@@ -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
Signature · 7 lines
2.11.1

-- 
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core