| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
In all of our recipes, we should be following yoctos lead on formatting,
order, and other things, for consistency in our meta layers.
This commit runs oe-stylize.py on all of our files. The types of
changes being made can be seen in the commit, but amount to:
1. Setting an explicit key ordering
2. Sectioning the files appropriately
3. Applying rules checking to our files
At some point in the near future, we would turn this on as part of
repotest, but some minor changes need to be upstreamed to meta-oe (WIP)
to make that happen.
Looking for input on whether this is something we'd like to do, and
whether the diffs below look reasonable to folks.
Signed-off-by: Ed Tanous <edtanous@google.com>
Change-Id: I489dd21d38a9fe4f3ece89cc7a5e1d0463224abf
|
|
openldap, on purpose or not, now required md4 support to compile. While
this is not ideal that we have this dependency, it's easy enough to
re-enable md4 when ldap is enabled.
Unfortunately, the intent of the obmc-user-mgmt-ldap feature looks like
it was broken at some point, and even with that option disabled,
openldap is still included in image builds, so at the moment, md4 is
universally required for all builds. None of this is ideal, and in the
future, ideally we should:
1. upstream a patch to openldap to not require MD4 support
2. fir the obmc-user-mgmt-ldap feature to meet its intent, and allow
ldap to be optional in the build.
Tested: Code builds further with the subtree updates.
Signed-off-by: Ed Tanous <edtanous@google.com>
Change-Id: I3ebf231b21af01df98ca4c11eb496427ea3f9443
|
|
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I588025b614416c43aa2d053765ab53bacf890cb5
|
|
Upstream recipe moved the disabling of deprecated crypto algorithms into
a new DEPRECATED_CRYPTO_FLAGS variable.
(Klaus: also adjust phosphor's EXTRA_OECONF for this package to not
double-disable already obsolete ciphers)
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I75e2c35ada37c9510a0af347772cdeb2b23d99e9
Signed-off-by: Klaus Heinrich Kiwi <klaus@linux.vnet.ibm.com>
|
|
This script was rewritten into perl at some point and brings in an
unnecessary runtime dependency on perl.
Tested:
Built a romulus openbmc image and verified that c_rehash and perl
were no longer included.
(From meta-phosphor rev: 53b55e6305bc1a801d758d2a11d2f2c402638acd)
Change-Id: I77cc9e3f50cdca47fb71d8c2ceac0fab839b6e9e
Signed-off-by: William A. Kennington III <wak@google.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Reset the following subtrees on thud HEAD:
poky: 87e3a9739d
meta-openembedded: 6094ae18c8
meta-security: 31dc4e7532
meta-raspberrypi: a48743dc36
meta-xilinx: c42016e2e6
Also re-apply backports that didn't make it into thud:
poky:
17726d0 systemd-systemctl-native: handle Install wildcards
meta-openembedded:
4321a5d libtinyxml2: update to 7.0.1
042f0a3 libcereal: Add native and nativesdk classes
e23284f libcereal: Allow empty package
030e8d4 rsyslog: curl-less build with fmhttp PACKAGECONFIG
179a1b9 gtest: update to 1.8.1
Squashed OpenBMC subtree compatibility updates:
meta-aspeed:
Brad Bishop (1):
aspeed: add yocto 2.6 compatibility
meta-ibm:
Brad Bishop (1):
ibm: prepare for yocto 2.6
meta-ingrasys:
Brad Bishop (1):
ingrasys: set layer compatibility to yocto 2.6
meta-openpower:
Brad Bishop (1):
openpower: set layer compatibility to yocto 2.6
meta-phosphor:
Brad Bishop (3):
phosphor: set layer compatibility to thud
phosphor: libgpg-error: drop patches
phosphor: react to fitimage artifact rename
Ed Tanous (4):
Dropbear: upgrade options for latest upgrade
yocto2.6: update openssl options
busybox: remove upstream watchdog patch
systemd: Rebase CONFIG_CGROUP_BPF patch
Change-Id: I7b1fe71cca880d0372a82d94b5fd785323e3a9e7
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
The openssl bbappend does not have any files, so setting FILESEXTRAPATH
is not necessary.
(From meta-phosphor rev: 11c064734d952c30135ee678813ce0a9ea5aaa5f)
Change-Id: I88ee623a0fce5241446e4b7df143aa556e732692
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Because of this commit here:
https://github.com/webpack/webpack/pull/6549/commits
The newest version of webpack chooses to use md4 for compile time
hashing instead of something more useful like md5/sha1/sha256. In the
openbmc openssl.bbappend, we override and disable some of the ciphers we
should not be using on target.
This patchset adjusts the recipe to only disable the insecure hashes on
the target, so openssl-native still compiles and allows them.
This patchset is the first in a series to upgrade phosphor-webui to the
latest versions of the packages we use.
Originally opened as:
https://gerrit.openbmc-project.xyz/#/c/openbmc/openbmc/+/12561/
(From meta-phosphor rev: e5217200adeed14222afde2b3ff6b972173a938f)
Change-Id: Ic68b8cb9f2277cfca78f75aac0640b363640c61d
Signed-off-by: Ed Tanous <ed.tanous@intel.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Adopt a more conventional directory hierarchy. meta-phosphor is still
a _long_ way from suitable for hosting on yoctoproject.org but things
like this don't help.
(From meta-phosphor rev: 471cfcefa74b8c7ceb704cb670e6d915cf27c63b)
Change-Id: I3f106b2f6cdc6cec734be28a6090800546f362eb
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
