Using stable releases from git
It's beginning to sound like we've caught some folks off guard by pushing changes to the edison branch of the poky repository in preparation for an upcoming edison point release.
The named branches are development branches for the release, stable release development will be done in the named branch and we can't guarantee they will be issue free (though we intend them to be where possible).
If you're looking to use a git checkout which matches the release tarballs you should checkout the tags for the releases. i.e. for Poky Edison-6.0/Yocto 1.1:
http://git.yoctoproject.org/cgit/cgit.cgi/poky/tag/?id=edison-6.0
http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/tag/?id=edison-6.0
Having suffered through a couple of stable cycles recently I anticipate that in future the release branches will be updated more frequently. This will make it even more important to use a tag, rather than a branch, to track the releases using git.
Cheers,
Joshua
Signature · 3 lines
Joshua Lock
Yocto Project "Johannes factotum"
Intel Open Source Technology CentreQuoted 9 lines · Joshua Lock
It's beginning to sound like we've caught some folks off guard by pushing changes to the edison branch of the poky repository in preparation for an upcoming edison point release.
The named branches are development branches for the release, stable release development will be done in the named branch and we can't guarantee they will be issue free (though we intend them to be where possible).
If you're looking to use a git checkout which matches the release tarballs you should checkout the tags for the releases. i.e. for Poky Edison-6.0/Yocto 1.1:
http://git.yoctoproject.org/cgit/cgit.cgi/poky/tag/?id=edison-6.0
http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/tag/?id=edison-6.0
So instead of doing:
git checkout -b edison origin/edison
what should I do if I want to stay in sync with the tarball. This may just be a doc problem.
Jim A
Quoted 4 lines
Having suffered through a couple of stable cycles recently I anticipate that in future the release branches will be updated more frequently. This will make it even more important to use a tag, rather than a branch, to track the releases using git.
Cheers,
Joshua
Quoted 17 lines · jfabernathy
On 01/30/2012 05:58 PM, Joshua Lock wrote:
It's beginning to sound like we've caught some folks off guard by pushing changes to the edison branch of the poky repository in preparation for an upcoming edison point release.
The named branches are development branches for the release, stable release development will be done in the named branch and we can't guarantee they will be issue free (though we intend them to be where possible).
If you're looking to use a git checkout which matches the release tarballs you should checkout the tags for the releases. i.e. for Poky Edison-6.0/Yocto 1.1:
http://git.yoctoproject.org/cgit/cgit.cgi/poky/tag/?id=edison-6.0
http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/tag/?id=edison-6.0
Quoted 6 lines
So instead of doing:
git checkout -b edison origin/edison
what should I do if I want to stay in sync with the tarball. This may just be a doc problem.
git checkout -b edison1.1 edison-6.0
(confusing versions... I think that tag should really be poky-6.0)
-M
Quoted 14 lines · jfabernathy
Quoted 13 lines · Joshua Lock
It's beginning to sound like we've caught some folks off guard by pushing changes to the edison branch of the poky repository in preparation for an upcoming edison point release.
The named branches are development branches for the release, stable release development will be done in the named branch and we can't guarantee they will be issue free (though we intend them to be where possible).
If you're looking to use a git checkout which matches the release tarballs you should checkout the tags for the releases. i.e. for Poky Edison-6.0/Yocto 1.1:
Quoted 8 lines
Quoted 3 lines
http://git.yoctoproject.org/cgit/cgit.cgi/poky/tag/?id=edison-6.0
http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/tag/?id=edison-6.0So instead of doing:
git checkout -b edison origin/edison
what should I do if I want to stay in sync with the tarball. This may just be a doc problem.
I'd do:
git fetch --tags
git checkout edison-6.0
Then when a new tarball comes out, you'd repeat with the new tag name.
You can see the tags with:
git tag -l
(be sure to have git fetch --tags first)
i.e. to update through bernard releases
git fetch --tags
git checkout bernard-5.0
<time passes, 5.0.1 released>
git fetch --tags
git checkout bernard-5.0.1
<time passes, 5.0.2 released>
git fetch --tags
git checkout bernard-5.0.2
Cheers,
Joshua
Signature · 3 lines
Joshua Lock
Yocto Project "Johannes factotum"
Intel Open Source Technology CentreQuoted 22 lines · Joshua Lock
Quoted 21 lines · jfabernathy
Quoted 9 lines · Joshua Lock
It's beginning to sound like we've caught some folks off guard by pushing changes to the edison branch of the poky repository in preparation for an upcoming edison point release.
The named branches are development branches for the release, stable release development will be done in the named branch and we can't guarantee they will be issue free (though we intend them to be where possible).
Quoted 7 lines
If you're looking to use a git checkout which matches the release tarballs you should checkout the tags for the releases. i.e. for Poky Edison-6.0/Yocto 1.1:
http://git.yoctoproject.org/cgit/cgit.cgi/poky/tag/?id=edison-6.0
http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/tag/?id=edison-6.0So instead of doing:
git checkout -b edison origin/edison
Quoted 9 lines
Quoted 1 line
what should I do if I want to stay in sync with the tarball. This may just be a doc problem.
I'd do:
git fetch --tags
git checkout edison-6.0Then when a new tarball comes out, you'd repeat with the new tag name.
We I just tried that and it crashed a lot quicker. I'll just stick to the tarballs until this is all sorted out.
Jim A
Quoted 16 lines
You can see the tags with:
git tag -l
(be sure to have git fetch --tags first)i.e. to update through bernard releases
git fetch --tags
git checkout bernard-5.0
<time passes, 5.0.1 released>
git fetch --tags
git checkout bernard-5.0.1
<time passes, 5.0.2 released>
git fetch --tags
git checkout bernard-5.0.2Cheers,
Joshua
Quoted 28 lines · jfabernathy
Quoted 27 lines · Joshua Lock
Quoted 17 lines · jfabernathy
Quoted 9 lines · Joshua Lock
It's beginning to sound like we've caught some folks off guard by pushing changes to the edison branch of the poky repository in preparation for an upcoming edison point release.
The named branches are development branches for the release, stable release development will be done in the named branch and we can't guarantee they will be issue free (though we intend them to be where possible).
Quoted 7 lines
If you're looking to use a git checkout which matches the release tarballs you should checkout the tags for the releases. i.e. for Poky Edison-6.0/Yocto 1.1:
http://git.yoctoproject.org/cgit/cgit.cgi/poky/tag/?id=edison-6.0
http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/tag/?id=edison-6.0Quoted 6 lines
So instead of doing:
git checkout -b edison origin/edison
what should I do if I want to stay in sync with the tarball. This may just be a doc problem.
I'd do:
Quoted 8 lines
Quoted 5 lines
git fetch --tags
git checkout edison-6.0Then when a new tarball comes out, you'd repeat with the new tag name.
We I just tried that and it crashed a lot quicker. I'll just stick to the tarballs until this is all sorted out.
Are you using an appropriate tag (or branch) of meta-intel? The master branch of meta-intel with the bernard tag of poky will fail to parse because some of the recipes being appended to in meta-intel have changed names.
Cheers,
Joshua
Signature · 3 lines
Joshua Lock
Yocto Project "Johannes factotum"
Intel Open Source Technology CentreQuoted 33 lines · Joshua Lock
Quoted 32 lines · jfabernathy
Quoted 31 lines · Joshua Lock
Quoted 18 lines · jfabernathy
Quoted 9 lines · Joshua Lock
It's beginning to sound like we've caught some folks off guard by pushing changes to the edison branch of the poky repository in preparation for an upcoming edison point release.
The named branches are development branches for the release, stable release development will be done in the named branch and we can't guarantee they will be issue free (though we intend them to be where possible).
Quoted 8 lines
If you're looking to use a git checkout which matches the release tarballs you should checkout the tags for the releases. i.e. for Poky Edison-6.0/Yocto 1.1:
http://git.yoctoproject.org/cgit/cgit.cgi/poky/tag/?id=edison-6.0
http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/tag/?id=edison-6.0Quoted 6 lines
So instead of doing:
git checkout -b edison origin/edison
what should I do if I want to stay in sync with the tarball. This may just be a doc problem.
I'd do:
git fetch --tags
git checkout edison-6.0
Quoted 8 lines
Quoted 5 lines
Quoted 2 lines
Then when a new tarball comes out, you'd repeat with the new tag name.
We I just tried that and it crashed a lot quicker. I'll just stick to the tarballs until this is all sorted out.
Are you using an appropriate tag (or branch) of meta-intel? The master branch of meta-intel with the bernard tag of poky will fail to parse because some of the recipes being appended to in meta-intel have changed names.
Can you explain the branch vs. tag as Yocto uses it? most of the help on git checkout refers to branch, where we are talking using a tag name. In Yocto what is the difference?
Quoted 2 lines
Cheers,
Joshua
Quoted 40 lines · jfabernathy
Quoted 39 lines · Joshua Lock
Quoted 37 lines · jfabernathy
Quoted 26 lines · Joshua Lock
Quoted 18 lines · jfabernathy
Quoted 9 lines · Joshua Lock
It's beginning to sound like we've caught some folks off guard by pushing changes to the edison branch of the poky repository in preparation for an upcoming edison point release.
The named branches are development branches for the release, stable release development will be done in the named branch and we can't guarantee they will be issue free (though we intend them to be where possible).
Quoted 8 lines
If you're looking to use a git checkout which matches the release tarballs you should checkout the tags for the releases. i.e. for Poky Edison-6.0/Yocto 1.1:
http://git.yoctoproject.org/cgit/cgit.cgi/poky/tag/?id=edison-6.0
http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/tag/?id=edison-6.0Quoted 6 lines
So instead of doing:
git checkout -b edison origin/edison
what should I do if I want to stay in sync with the tarball. This may just be a doc problem.
Quoted 7 lines
I'd do:
git fetch --tags
git checkout edison-6.0Then when a new tarball comes out, you'd repeat with the new tag name.
We I just tried that and it crashed a lot quicker. I'll just stick to the tarballs until this is all sorted out.
Quoted 8 lines
Quoted 5 lines
Are you using an appropriate tag (or branch) of meta-intel? The master branch of meta-intel with the bernard tag of poky will fail to parse because some of the recipes being appended to in meta-intel have changed names.
Can you explain the branch vs. tag as Yocto uses it? most of the help on git checkout refers to branch, where we are talking using a tag name. In Yocto what is the difference?
A tag is a snapshot, a release or milestone usually, and is static. Releases (and their tarballs) are generated from a tag.
A branch represents some ongoing development of some sort, we branch master when we're close to release and only put bug fixes in the branch. When it comes to release time we tag the release.
We use those same branches for any stable maintenance work, once that's ready for release we'll create another tag.
In short:
* branches are for development and the contents change
* tags are snapshots
Cheers,
Joshua
Signature · 3 lines
Joshua Lock
Yocto Project "Johannes factotum"
Intel Open Source Technology Centre