Age | Commit message (Collapse) | Author |
|
| ../../git/server/red_parse_qxl.c:367:18: error: 'BITMAP_FMT_IS_RGB'
defined but not used [-Werror=unused-const-variable=]
| static const int BITMAP_FMT_IS_RGB[] = {0, 0, 0, 0, 0, 0, 1, 1, 1, 1, 1};
Signed-off-by: He Zhe <zhe.he@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Upgrade nss-pam-ldapd from 0.9.6 to 0.9.7.
Signed-off-by: Wang Xin <wangxin2015.fnst@cn.fujitsu.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
There is a new QA check warning which has been added which flags
situation where a subpackage includes a license which is not included
in the recipe's LICENSE string. In this case we are seeing:
WARNING: .../meta-cloud-services/recipes-support/spice/spice_git.bb:
LICENSE_lib32-spice-protocol includes licenses (BSD) that are not
listed in LICENSE
Adding the missing license to the LICENSE string.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
spice auto detect Xinerama library to enable the feature,
but it causes error when using sstate between different
builds, e.g. previous build have xinerama but the later
one doesn't, then it fails on the later one with:
"Package 'xinerama', required by 'spice-server', not found"
Add PACKAGECONFIG for xinerama to ensure we have
deterministic builds.
Signed-off-by: Jackie Huang <jackie.huang@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Just add systemd style service file.
Signed-off-by: Liang Li <liang.li@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
To prepare enable nss-pam-ldapd reuseable by other layer/addons.
Signed-off-by: Liang Li <liang.li@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Prior to this commit it is not possible to cross build a ruby gem. In
fact even on the x86 system the object files for the native gem are
generated with the wrong compiler (the host compiler instead of the
cross compiler).
A better way to fix this in the future would be to use only gems that
supported cross compile tool called rake. For now the bbclass can
modify the extconf.rb just before creating the gem and insert some
code into the Makefile so as to honor the cross compile environment.
Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
There are several puppet modules that provide functionality to
interact with vSwitches, such as OpenVSwitch. This one is one of the
more popular and is an officially sanctioned puppet module so using
this one for the time being.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
This module is used by many puppet modules so will be useful to have
to extend our puppet capabilities. Additionally it offers some useful
functionality such as the ability to append to a file.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Only the https protocol is available when cloning from
git.xiph.org currently.
Signed-off-by: Josep Puigdemont <josep.puigdemont@enea.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Create a composite source revision. Failure to do so
can cause parsing errors.
Signed-off-by: Joe Slater <jslater@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
We should uprev puppet at some point but for the sake of stabilizing
first the following set of patches will allow puppet to work with the
newer version of Ruby that we are using.
The first two are upstream commits and the third is a commit which
borrows a fix found in various puppet forks (repos which people host
to stabalize older versions of puppet). With these patches puppet can
now execute commands like 'help' and 'apply' without falling over.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Currently we get the following warning when building puppet:
WARNING: QA Issue: /usr/lib/ruby/gems/2.2.0/gems/puppet-3.7.3/
lib/puppet/vendor/safe@underscore@yaml/run@underscore@specs@
underscore@all@underscore@ruby@underscore@versions.sh_puppet
contained in package puppet requires /bin/bash, but no
providers found in its RDEPENDS [file-rdeps]
Adding 'bash' as an RDEPENDS fixes this.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Puppet can be used by many 'cloud services', it is not openstack
specific, so moving puppet and puppet related recipes to the
meta-cloud-services base layer. This allows either internal sub-layers
found in meta-cloud-services or external layers to include
meta-cloud-services without being burdened by bbappends and configs
found in meta-openstack.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
The patches are taken from Debian.
Signed-off-by: Amy Fong <amy.fong@windriver.com>
|
|
Since oe-core introduced the autotools separated build and source
directory changes, some package builds broke.
With this change, we can build against the latest oe-core master.
It should be noted that this masks the build issues, and the bbappends
should be removed as dependency layers update or "real" fixes are
generated.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Some minor fixes around generated .c and .h files were required to
allow separated src and build dirs. Without these builds will fail
and you would have to build in the src dir.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
We were getting several errors during configure related to
autoreconf. We need to create an empty m4 directory as well
as enable the subdir-objects option to allow configure to
complete successfully. There were indications that this second
issue was fixed upstream but even using the latest git trees
I am seeing this failure.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
spice requires celt051.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
A common requirement for many cloud systems is remote console access. Adding
spice to the common layer allows a rich console environment to be provided.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|