Poky release is 5.0 "Bernard" confusion
Hi,
Can someone please tell me if there is a tag ingit://git.pokylinux.org/poky.git which corresponds to the official release tarball and what it is?
What puzzles me is that if you check out bernard-5.0 from the git repository it does not correspond to
http://www.yoctoproject.org/downloads/poky/poky-bernard-5.0.tar.bz2
OK, it does not seem to be anything seriously different between the two:
# modified: README.hardware # modified: documentation/adt-manual/adt-prepare.xml # modified: documentation/yocto-project-qs/yocto-project-qs.xml # modified: meta/conf/distro/poky.conf
... but you might want to synchronize since some people prefer to work from git and others from the tarball.
As an example the README.hardware found in the tarball suggests to build and update u-boot for the Freescale MPC8315E-RDB, which does not exist in the git repo.
Regards,
Robert
Quoted 17 lines · Robert Berger
Hi,
Can someone please tell me if there is a tag in
git://git.pokylinux.org/poky.gitwhich corresponds to the official release tarball and what it is?What puzzles me is that if you check out bernard-5.0 from the git repository it does not correspond to
http://www.yoctoproject.org/downloads/poky/poky-bernard-5.0.tar.bz2OK, it does not seem to be anything seriously different between the two:
# modified: README.hardware # modified: documentation/adt-manual/adt-prepare.xml # modified: documentation/yocto-project-qs/yocto-project-qs.xml # modified: meta/conf/distro/poky.conf
Quoted 6 lines
... but you might want to synchronize since some people prefer to work from git and others from the tarball.
As an example the README.hardware found in the tarball suggests to build and update u-boot for the Freescale MPC8315E-RDB, which does not exist in the git repo.
This suggests to me that your local git repository isn't up to date. The tag has been moved at least once since it was created, and it sounds like your repository is behind the most recent move of the tag.
Note: if you use git fetch --all, that will fetch new tags but doesn't update old ones that have moved - you need to explicitly run git fetch --tags.
HTH,
Scott
Signature · 3 lines
Scott Garman Embedded Linux Engineer - Yocto Project Intel Open Source Technology Center
Hi Scott,
Quoted 8 lines
This suggests to me that your local git repository isn't up to date. The tag has been moved at least once since it was created, and it sounds like your repository is behind the most recent move of the tag.
Note: if you use git fetch --all, that will fetch new tags but doesn't update old ones that have moved - you need to explicitly run git fetch --tags.
Thanks, you are absolutely right:
git pull
is not enough;)
git fetch --tags
From git://git.pokylinux.org/poky
- [tag update] bernard-5.0 -> bernard-5.0
Quoted 5 lines
HTH,
Scott
Regards,
Robert
..."The scientific name for an animal that doesn't either run from or fight its enemies is lunch." - Michael Friedman
My public pgp key is available at:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x90320BF1
Dear Scott Garman,
Quoted 4 lines · In message <[email protected]> you wrote:
This suggests to me that your local git repository isn't up to date. The tag has been moved at least once since it was created, and it sounds like your repository is behind the most recent move of the tag.
You are ... moving release tags? Grrrgh!!!
Could you please stop doing this? Nobody ever expects such a thing. And while we are at it: It would also be great if you could GPG-sign the tags.
Thanks.
Wolfgang Denk
Signature · 6 lines
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: [email protected] "He only drinks when he gets depressed." "Why does he get depressed?" "Sometimes it's because he hasn't had a drink." - Terry Pratchett, _Men at Arms_
Quoted 9 lines · Wolfgang Denk
Dear Scott Garman,
Quoted 4 lines · In message <[email protected]> you wrote:
This suggests to me that your local git repository isn't up to date. The tag has been moved at least once since it was created, and it sounds like your repository is behind the most recent move of the tag.
You are ... moving release tags? Grrrgh!!!
Oh, that surprises me as well. What is the justification here? Generally speaking, I'd expect the tags to be static.
--
Darren
Quoted 9 lines
Could you please stop doing this? Nobody ever expects such a thing. And while we are at it: It would also be great if you could GPG-sign the tags.
Thanks.
Wolfgang Denk
Signature · 3 lines
Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel
Quoted 5 lines · Darren
Quoted 4 lines · Wolfgang Denk
Dear Scott Garman,
Quoted 1 line · In message<[email protected]> you wrote:
Quoted 8 lines
Quoted 5 lines
Quoted 3 lines
This suggests to me that your local git repository isn't up to date. The tag has been moved at least once since it was created, and it sounds like your repository is behind the most recent move of the tag.
You are ... moving release tags? Grrrgh!!!
Oh, that surprises me as well. What is the justification here? Generally speaking, I'd expect the tags to be static.
I'm cc'ing Beth on this thread, since I was not involved in the tag move.
Scott
Signature · 3 lines
Scott Garman Embedded Linux Engineer - Yocto Project Intel Open Source Technology Center
Quoted 10 lines · Wolfgang Denk
Dear Scott Garman,
Quoted 4 lines · In message<[email protected]> you wrote:
This suggests to me that your local git repository isn't up to date. The tag has been moved at least once since it was created, and it sounds like your repository is behind the most recent move of the tag.
You are ... moving release tags? Grrrgh!!!
Quoted 8 lines
Could you please stop doing this? Nobody ever expects such a thing. And while we are at it: It would also be great if you could GPG-sign the tags.
Thanks.
Wolfgang Denk
Wolfgang,
Yes, there was a problem with what I assumed would be our bernard-5.0 release and the tag needed to be moved, which, while a messy practice, was the only available option at the time. The tag shouldn't have been created until after verification of the RC. I'll make sure that this is captured in our release process. If you want, please feel free to open up a bug in bugzilla and assign it to me. As this was a relatively new process, I knew we'd hit some snags. This was one of them, and I'll make sure this is captured in our process so that we don't hit it again.
Thanks for the feedback.
------------------
Elizabeth Flanagan
Yocto Project
Release Engineer
Dear Elizabeth Flanagan,
Quoted 7 lines · In message <[email protected]> you wrote:
Yes, there was a problem with what I assumed would be our bernard-5.0 release and the tag needed to be moved, which, while a messy practice, was the only available option at the time. The tag shouldn't have been created until after verification of the RC. I'll make sure that this is captured in our release process. If you want, please feel free to open up a bug in bugzilla and assign it to me. As this was a relatively new process, I knew we'd hit some snags. This was one of them, and I'll make sure this is captured in our process so that we don't hit it again.
I know that such things happen, but then it would have been at least a good idea to post some information about this - as mentioned, nobody expects that git tags get moved.
Do you also plan to GPG-sign the tags?
Note that annotated tags would also help a lot for example with commands like "git describe".
Thanks.
Best regards,
Wolfgang Denk
Signature · 4 lines
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: [email protected] Der Dativ ist dem Genitiv sein Tod.
Quoted 11 lines · Wolfgang Denk
Dear Elizabeth Flanagan,
Quoted 7 lines · In message<[email protected]> you wrote:
Yes, there was a problem with what I assumed would be our bernard-5.0 release and the tag needed to be moved, which, while a messy practice, was the only available option at the time. The tag shouldn't have been created until after verification of the RC. I'll make sure that this is captured in our release process. If you want, please feel free to open up a bug in bugzilla and assign it to me. As this was a relatively new process, I knew we'd hit some snags. This was one of them, and I'll make sure this is captured in our process so that we don't hit it again.
Quoted 6 lines
I know that such things happen, but then it would have been at least a good idea to post some information about this - as mentioned, nobody expects that git tags get moved.
Do you also plan to GPG-sign the tags?
We certainly should be doing this. I have some automation of release process tasks coming up, and will make sure that that is part of it. I want to think about how this is going to be done, process wise, and implement an automated process that takes gpg signing and tag annotation into account, instead of doing it one way (manually) and switching midstream to an automated process that may be different. So, short answer, is yes, we should be doing that. Long answer is "Let's do it via the automated release process so we can ensure it's repeatable."
-b
------------------
Elizabeth Flanagan
Yocto Project
Release Engineer