@@ -8,7 +8,7 @@ This repository is where manual development occurs. If you plan on contributing
back to the Yocto Project documentation, you should set up a local Git
repository based on this upstream repository as follows:
- git clone git://git.yoctoproject.org/yocto-docs
+ git clone https://git.yoctoproject.org/yocto-docs
Manual Organization
===================
@@ -60,7 +60,7 @@ repository unto itself and clicking on the layer name displays two URLs
from which you can clone the layer's repository to your local system.
Here is an example that clones the Raspberry Pi BSP layer::
- $ git clone git://git.yoctoproject.org/meta-raspberrypi
+ $ git clone https://git.yoctoproject.org/meta-raspberrypi
In addition to BSP layers, the ``meta-yocto-bsp`` layer is part of
:yocto_git:`meta-yocto </meta-yocto>`. The ``meta-yocto-bsp`` layer maintains
@@ -177,7 +177,7 @@ section.
#. *Clone the Layer:* ::
- $ git clone git://git.yoctoproject.org/meta-intel.git
+ $ git clone https://git.yoctoproject.org/meta-intel.git
Cloning into 'meta-intel'...
remote: Counting objects: 15585, done.
remote: Compressing objects: 100% (5056/5056), done.
@@ -210,7 +210,7 @@ section.
your hardware most closely matches the ``meta-raspberrypi``, clone
that layer::
- $ git clone git://git.yoctoproject.org/meta-raspberrypi
+ $ git clone https://git.yoctoproject.org/meta-raspberrypi
Cloning into 'meta-raspberrypi'...
remote: Counting objects: 4743, done.
remote: Compressing objects: 100% (2185/2185), done.
@@ -963,13 +963,13 @@ above:
Setting up source meta-intel, revision 15.0-hardknott-3.3-310-g0a96edae, branch master
Running 'git init -q /srv/work/alex/my-build/meta-intel'
- Running 'git remote remove origin > /dev/null 2>&1; git remote add origin git://git.yoctoproject.org/meta-intel' in /srv/work/alex/my-build/meta-intel
+ Running 'git remote remove origin > /dev/null 2>&1; git remote add origin https://git.yoctoproject.org/meta-intel' in /srv/work/alex/my-build/meta-intel
Running 'git fetch -q origin || true' in /srv/work/alex/my-build/meta-intel
Running 'git checkout -q 0a96edae609a3f48befac36af82cf1eed6786b4a' in /srv/work/alex/my-build/meta-intel
Setting up source poky, revision 4.1_M1-372-g55483d28f2, branch akanavin/setup-layers
Running 'git init -q /srv/work/alex/my-build/poky'
- Running 'git remote remove origin > /dev/null 2>&1; git remote add origin git://git.yoctoproject.org/poky' in /srv/work/alex/my-build/poky
+ Running 'git remote remove origin > /dev/null 2>&1; git remote add origin https://git.yoctoproject.org/poky' in /srv/work/alex/my-build/poky
Running 'git fetch -q origin || true' in /srv/work/alex/my-build/poky
Running 'git remote remove poky-contrib > /dev/null 2>&1; git remote add poky-contrib ssh://git@push.yoctoproject.org/poky-contrib' in /srv/work/alex/my-build/poky
Running 'git fetch -q poky-contrib || true' in /srv/work/alex/my-build/poky
@@ -73,7 +73,7 @@ The following steps describe how to set up the AUH utility:
onto your development host. The following command uses Git to create
a local copy of the repository on your system::
- $ git clone git://git.yoctoproject.org/auto-upgrade-helper
+ $ git clone https://git.yoctoproject.org/auto-upgrade-helper
Cloning into 'auto-upgrade-helper'... remote: Counting objects: 768, done.
remote: Compressing objects: 100% (300/300), done.
remote: Total 768 (delta 499), reused 703 (delta 434)
@@ -741,8 +741,8 @@ Metadata to the build as a "type=kmeta" repository through the
example, consider the following :term:`SRC_URI` statement from the
``linux-yocto_5.15.bb`` kernel recipe::
- SRC_URI = "git://git.yoctoproject.org/linux-yocto.git;name=machine;branch=${KBRANCH};protocol=https \
- git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-5.15;destsuffix=${KMETA};protocol=https"
+ SRC_URI = "https://git.yoctoproject.org/linux-yocto.git;name=machine;branch=${KBRANCH};protocol=https \
+ https://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-5.15;destsuffix=${KMETA};protocol=https"
``${KMETA}``, in this context, is simply used to name the directory into
which the Git fetcher places the Metadata. This behavior is no different
@@ -207,7 +207,7 @@ section:
``linux-yocto-4.12`` kernel and be in the ``standard/base`` branch::
$ cd ~
- $ git clone git://git.yoctoproject.org/linux-yocto-4.12 --branch standard/base
+ $ git clone https://git.yoctoproject.org/linux-yocto-4.12 --branch standard/base
Cloning into 'linux-yocto-4.12'...
remote: Counting objects: 6097195, done.
remote: Compressing objects: 100% (901026/901026), done.
@@ -233,7 +233,7 @@ section:
``yocto-kernel-cache`` and switch to the ``yocto-4.12`` branch::
$ cd ~
- $ git clone git://git.yoctoproject.org/yocto-kernel-cache --branch yocto-4.12
+ $ git clone https://git.yoctoproject.org/yocto-kernel-cache --branch yocto-4.12
Cloning into 'yocto-kernel-cache'...
remote: Counting objects: 22639, done.
remote: Compressing objects: 100% (9761/9761), done.
@@ -30,8 +30,8 @@ example, the following commands clone the Yocto Project baseline Linux
kernel that branches off ``linux.org`` version 4.12 and the
``yocto-kernel-cache``, which contains stores of kernel Metadata::
- $ git clone git://git.yoctoproject.org/linux-yocto-4.12
- $ git clone git://git.yoctoproject.org/linux-kernel-cache
+ $ git clone https://git.yoctoproject.org/linux-yocto-4.12
+ $ git clone https://git.yoctoproject.org/linux-kernel-cache
For more information on
how to set up a local Git repository of the Yocto Project Linux kernel
@@ -403,7 +403,7 @@ development branch in the repository. To help illustrate, consider the
following example Git commands::
$ cd ~
- $ git clone git://git.yoctoproject.org/yocto-docs -b &DISTRO_NAME_NO_CAP;
+ $ git clone https://git.yoctoproject.org/yocto-docs -b &DISTRO_NAME_NO_CAP;
In the previous example
after moving to the home directory, the ``git clone`` command creates a
@@ -442,7 +442,7 @@ The most common use is to check out a working branch that matches a
specific Yocto Project release. Here is an example::
$ cd ~
- $ git clone git://git.yoctoproject.org/yocto-docs
+ $ git clone https://git.yoctoproject.org/yocto-docs
$ cd yocto-docs
$ git fetch --tags
$ git checkout tags/&DISTRO_NAME_NO_CAP;-&DISTRO; -b my_&DISTRO_NAME_NO_CAP;-&DISTRO;
@@ -277,7 +277,7 @@ release selection:
<!-- Bitbake versions which correspond to the metadata release -->
<object model="orm.bitbakeversion" pk="1">
<field type="CharField" name="name">&DISTRO_NAME_NO_CAP;</field>
- <field type="CharField" name="giturl">git://git.yoctoproject.org/poky</field>
+ <field type="CharField" name="giturl">https://git.yoctoproject.org/poky</field>
<field type="CharField" name="branch">&DISTRO_NAME_NO_CAP;</field>
<field type="CharField" name="dirpath">bitbake</field>
</object>
@@ -331,7 +331,7 @@ that includes the layer. In general all releases include the layer.
<object model="orm.layer" pk="1">
<field type="CharField" name="name">openembedded-core</field>
<field type="CharField" name="layer_index_url"></field>
- <field type="CharField" name="vcs_url">git://git.yoctoproject.org/poky</field>
+ <field type="CharField" name="vcs_url">https://git.yoctoproject.org/poky</field>
<field type="CharField" name="vcs_web_url">https://git.yoctoproject.org/cgit/cgit.cgi/poky</field>
<field type="CharField" name="vcs_web_tree_base_url">https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/%path%?h=%branch%</field>
<field type="CharField" name="vcs_web_file_base_url">https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/%path%?h=%branch%</field>
@@ -236,7 +236,7 @@ Perform the following steps to install Toaster:
#. Checkout a copy of ``poky`` into the web server directory. You will
be using ``/var/www/toaster``::
- $ git clone git://git.yoctoproject.org/poky
+ $ git clone https://git.yoctoproject.org/poky
$ git checkout &DISTRO_NAME_NO_CAP;
#. Install Toaster dependencies using the ``--user`` flag which keeps the
Since the git protocol is not supported anymore, change all references to "git.yoctoproject.org" to use https instead. This is a simple textual substitution across the various manuals. Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca> ---