Reset poky to before our libpam hacks
Things got a bit out of synch with openbmc-config due to the libpam
issues and the migration from the meta-* layers.
Revert the two previous commits and then put the latest poky in with the
libpam revert and get openbmc-config right again.
Revert "Revert "libpam: update 1.3.1 -> 1.5.1""
This reverts commit 87ddd3eab4df68e624b5350ccaab28b3b97547c0.
Revert "poky: subtree update:796be0593a..10c69538c0"
This reverts commit c723b72979bfac6362509cf1fe086900f6641f28.
Change-Id: I3a1f405193aee6a21fe0cd24be9927c143a23d9a
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
diff --git a/poky/documentation/overview-manual/development-environment.rst b/poky/documentation/overview-manual/development-environment.rst
index 011a479..9a2997d 100644
--- a/poky/documentation/overview-manual/development-environment.rst
+++ b/poky/documentation/overview-manual/development-environment.rst
@@ -40,7 +40,7 @@
Microsoft Corporation.
Wikipedia has a good historical description of the Open Source
-Philosophy `here <https://en.wikipedia.org/wiki/Open_source>`__. You can
+Philosophy `here <http://en.wikipedia.org/wiki/Open_source>`__. You can
also find helpful information on how to participate in the Linux
Community
`here <https://www.kernel.org/doc/html/latest/process/index.html>`__.
@@ -291,7 +291,7 @@
practices or methods that help development run smoothly. The following
list describes some of these practices. For more information about Git
workflows, see the workflow topics in the `Git Community
-Book <https://book.git-scm.com>`__.
+Book <http://book.git-scm.com>`__.
- *Make Small Changes:* It is best to keep the changes you commit small
as compared to bundling many disparate changes into a single commit.
@@ -368,12 +368,12 @@
.. note::
- For more information on Git, see
- https://git-scm.com/documentation.
+ http://git-scm.com/documentation.
- If you need to download Git, it is recommended that you add Git to
your system through your distribution's "software store" (e.g. for
Ubuntu, use the Ubuntu Software feature). For the Git download
- page, see https://git-scm.com/download.
+ page, see http://git-scm.com/download.
- For information beyond the introductory nature in this section,
see the ":ref:`dev-manual/start:locating yocto project source files`"
@@ -507,7 +507,7 @@
you understand the basic philosophy behind Git. You do not have to be an
expert in Git to be functional. A good place to look for instruction on
a minimal set of Git commands is
-`here <https://git-scm.com/documentation>`__.
+`here <http://git-scm.com/documentation>`__.
The following list of Git commands briefly describes some basic Git
operations as a way to get started. As with any set of commands, this
@@ -614,10 +614,10 @@
this history, you can find basic information here:
- `Open source license
- history <https://en.wikipedia.org/wiki/Open-source_license>`__
+ history <http://en.wikipedia.org/wiki/Open-source_license>`__
- `Free software license
- history <https://en.wikipedia.org/wiki/Free_software_license>`__
+ history <http://en.wikipedia.org/wiki/Free_software_license>`__
In general, the Yocto Project is broadly licensed under the
Massachusetts Institute of Technology (MIT) License. MIT licensing
@@ -626,9 +626,9 @@
the GNU General Public License (GPL). Patches to the Yocto Project
follow the upstream licensing scheme. You can find information on the
MIT license
-`here <https://www.opensource.org/licenses/mit-license.php>`__. You can
+`here <http://www.opensource.org/licenses/mit-license.php>`__. You can
find information on the GNU GPL
-`here <https://www.opensource.org/licenses/LGPL-3.0>`__.
+`here <http://www.opensource.org/licenses/LGPL-3.0>`__.
When you build an image using the Yocto Project, the build process uses
a known list of licenses to ensure compliance. You can find this list in
@@ -646,11 +646,11 @@
The base list of licenses used by the build process is a combination of
the Software Package Data Exchange (SPDX) list and the Open Source
-Initiative (OSI) projects. `SPDX Group <https://spdx.org>`__ is a working
+Initiative (OSI) projects. `SPDX Group <http://spdx.org>`__ is a working
group of the Linux Foundation that maintains a specification for a
standard format for communicating the components, licenses, and
copyrights associated with a software package.
-`OSI <https://opensource.org>`__ is a corporation dedicated to the Open
+`OSI <http://opensource.org>`__ is a corporation dedicated to the Open
Source Definition and the effort for reviewing and approving licenses
that conform to the Open Source Definition (OSD).