aboutsummaryrefslogtreecommitdiffstats
path: root/recipes-devtools
AgeCommit message (Collapse)Author
2021-05-12go-systemd: explicitly specify branchwarriorBruce Ashfield
The upstream project has removed the master branch in favour of 'main'. We were relying on the fetcher default of master previously, and now that master no longer exists, we get a fetch failure. Adding an explicit branch=main gets things working again. Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
2019-03-20notary: uprev to v0.6.1Hongzhi.Song
Signed-off-by: Hongzhi.Song <hongzhi.song@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
2019-03-08python-docker: depend on python-misc for the ntpath moduleDan Callaghan
Signed-off-by: Dan Callaghan <dan.callaghan@opengear.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
2019-02-03python-webob:upgrade to 1.8.5Hong Liu
Upgrade python-webob from 1.8.2 to 1.8.5 Signed-off-by: Hong Liu <hongl.fnst@cn.fujitsu.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
2019-01-16Use SRCPV instead of SRCREV where possiblePaul Barker
This change reduces the length of ${PV} for several recipes and gives us auto-incrementing version numbers. Signed-off-by: Paul Barker <paul@betafive.co.uk> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2018-12-21add the py2 version for python-docker and python-docker-pycreds packagesTing Yu
add the py2 version for python-docker and python-docker-pycreds packages. add python-six and python-backport_ssl (for ph2 only) as python-docker dependencies. verify the connection to docker engine at run time - >>> import docker >>> client = docker.from_env() >>> client.images.list() [<Image: 'hello-world:latest'>] Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2018-09-05python-webob:1.7.3.bb->1.8.2Hong Liu
Upgrade python-webob from 1.7.3 to 1.8.2. Signed-off-by: Hong Liu <hongl.fnst@cn.fujitsu.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2018-09-05python-sphinx:1.7.6:1.7.8Hong Liu
Upgrade python-sphinx from 1.7.6 to 1.7.8. Signed-off-by: Hong Liu <hongl.fnst@cn.fujitsu.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2018-07-23python-sphinx:1.4.1->1.7.6Hong Liu
1.Upgrade python-sphinx from 1.4.1 to 1.7.6. 2.Modify LIC_FILES_CHKSUM,because of delete "PYTHON SOFTWARE FOUNDATION LICENSE VERSION 2" Signed-off-by: Hong Liu <hongl.fnst@cn.fujitsu.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2018-06-22python3-docker: update to 3.4.0Ricardo Salveti
Update python3-docker from 2.5.1 to 3.4.0. Signed-off-by: Ricardo Salveti <ricardo@opensourcefoundries.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2018-06-22python3-docker-pycreds: update to 0.3.0Ricardo Salveti
Update python3-docker-pycreds from 0.2.1 to 0.3.0. Signed-off-by: Ricardo Salveti <ricardo@opensourcefoundries.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2018-04-23refactor for YP Compat for PV changesArmin Kuster
Only include our versions of recipes if virtualiztions is in DISTRO_FEATURE Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2018-03-22go-fsnotify: switch to new repository on githubYunguo Wei
fsnotify is changed to new repository on gihub, so adapt this chanage accordingly to avoid fetch failure. Signed-off-by: Yunguo Wei <yunguo.wei@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2018-03-08gunicorn: replace PN with BPN, to solve fetch failure while building for ↵Jagadeesh Krishnanjanappa
multilib The multilib gunicorn (for example lib32-gunicorn) fetch fails with below error: -- snip -- --2018-03-07 16:52:09-- https://pypi.python.org/packages/source/g/gunicorn/lib32-gunicorn-19.1.1.tar.gz Resolving pypi.python.org... 151.101.0.223, 151.101.64.223, 151.101.128.223, ... Connecting to pypi.python.org|151.101.0.223|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2018-03-07 16:52:09 ERROR 404: Not Found. -- snip -- Signed-off-by: Jagadeesh Krishnanjanappa <jkrishnanjanappa@mvista.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2018-01-18python-twisted: drop recipeMark Asselstine
Per the original commit this was only included as a temporary measure until the recipe was available in meta-openembedded. At this point the meta-openembedded recipe is not only available but has been uprev'd several times making it more suitable than the recipe we are now deleting here. Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
2017-12-28python3-websocket-client: make py2 version availableMark Asselstine
Allow a py2 version of the python-websocket-client package to be built. This is required to support updates in meta-cloud-services. Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2017-11-15python3-dockerpty: fix license-checksum qa issueAbdur Rehman
Fix license path and checksum for python3-dockerpty. Signed-off-by: Abdur Rehman <abdur_rehman@mentor.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2017-11-15python-*: switch remaining pypi recipes to use the pypi classMark Asselstine
Cleanup the various python-* recipes which download from pypi. The biggest change is to "inherit pypi" which should result in us always using current pypi best practices. This will for example ensure we are using https and not http which is apparently going to be disabled soon. Where the default behavior in the pypi class wasn't sufficient we make use of the PYPI_* variables to overwrite the defaults. Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2017-11-07python-webob: uprev to v1.7.3Mark Asselstine
The only user in meta-virtualization is python-bugsnag and there is no version dependency. This new version is however required by the latest openstack. Switched to using the "common" pypi.bbclass while we are at it. Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2017-10-17python3-docker: add missing RDEPENDSRicardo Salveti
Add python3-docker-pycreds, python3-requests and python3-websocket-client to RDEPENDS for a functional python docker module (otherwise even import docker fails). Signed-off-by: Ricardo Salveti <ricardo@opensourcefoundries.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2017-09-15python3-docker-compose: add version 1.16.1 + dependenciesPascal Bach
This requires some packages as well as the pypi.bbclass from meta-python. It uses Python 3 as I don't think it makes sense to use Python 2 anymore. Signed-off-by: Pascal Bach <pascal.bach@siemens.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2017-08-22go-systemd: Fix QA dependency problemJason Wessel
ERROR: go-systemd-4+gitb4a58d95188dd092ae20072bac14cece0e67c388-r0 do_package_qa: QA Issue: /usr/local/go/src/github.com/coreos/go-systemd/test contained in package go-systemd requires /bin/bash, but no providers found in RDEPENDS_go-systemd? [file-rdeps] Resolved with proper dependency to bash. Signed-off-by: Jason Wessel <jason.wessel@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2017-08-14python-itsdangerous: Drop recipeAdrian Dudau
Same version of the recipe is maintained in meta-python, no need to keep a duplicate here. Signed-off-by: Adrian Dudau <adrian.dudau@enea.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2017-08-14python-simplejson: Drop recipeAdrian Dudau
Newer version of the recipe (v3.11.1) is already maintained in meta-python and I couldn't find any hard dependencies on the current version. Signed-off-by: Adrian Dudau <adrian.dudau@enea.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2017-08-03python-six: Drop recipeAdrian Dudau
Same recipe is maintained in oe-core, no need to keep a duplicate here. Signed-off-by: Adrian Dudau <adrian.dudau@enea.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2017-07-10python-requests: Drop recipeAdrian Dudau
There's a newer recipe (v2.13) maintained in meta-python. meta-openstack explicitly prefers that version over this one, so no point in keeping this recipe since nobody else is using this version. Signed-off-by: Adrian Dudau <adrian.dudau@enea.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2017-06-27devtools: remove protobuf*Bruce Ashfield
The protobuf recipes are in meta-oe, and were only here to support higher order virtualization tasks. Dropping the recipes and we'll use the ones directly from meta-oe, since the versions and compatibility should be fine. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2017-06-22python3-twisted: temporarily add recipeMark Asselstine
This will eventually be available in meta-openembedded so will be able to be reverted. This will allow us to use openvswitch with python3 in the interim. Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2017-03-21protobuf-native: Drop PR = 0Khem Raj
Drop PR setting to 0 its default anyway Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2017-03-21protobuf-native: Enable shared libsKhem Raj
protobuf-c needs shared libraries, linking with static libs ends up with undefined symbols Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2017-03-20tools: remove go from meta-virtualizationBruce Ashfield
go is now part of oe-core, so we can drop the meta-virt local recipes. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2017-02-09docker: fixup failing buildMark Asselstine
Docker is failing to build because it is attempting to download missing go dependencies. Add new recipes for missing dependencies and update existing recipes to ensure the version defined in docker's vendor.conf is available. Note that this fixes the build only. At this time many docker functions are working, such as 'docker image', 'docker pull' and more, but 'docker run' is currently failing. Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2017-02-09go-cross: add ${TARGET_ARCH} to PNMark Asselstine
Since we are building a cross tool which produces something which is ARCH specific we should stick to the <toolname>-cross-<arch> naming convention. A variant of this patch has been floating around for a while but with the changes around per recipe sysroots, distributed builds, shared builds... we are best served to adopt this convention now. Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2017-02-09go-native: rename to go-initial-nativeMark Asselstine
With the new per recipe sysroots we were having build issues since the bootstrap version of go (go-native 1.4) was being found and not the go-cross (1.6) we are expecting. This results in errors such as the following when building packages such as containerd: _cgo_.o: decoding dwarf section info at offset 0x4: unsupported version 0 This is caused by the dependency tree built up to prepare the per recipe sysroot. Since recipes like containerd DEPEND on go-cross and go-cross DEPENDS on go-native both are installed but unlike the old global sysroot the dependency parsing order results in go-native being last, overwriting go-cross. You can see this by running a devshell for containerd and running 'go version'. By adding '-initial' in the name we exploit functionality in sstate.bbclass that is already in place to handle gcc-initial and similar. This results in only explicit DEPENDS on go-native being enforced, so in the case of containerd we only get a dependency on go-cross and we therefor get go 1.6 as expected. Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2017-02-01go-cross: depend on virtual/${TARGET_PREFIX}gccMark Asselstine
This fixes the compile time error #runtime/cgo exec: "x86_64-overc-linux-gcc": executable file not found in $PATH Since we set CC_FOR_TARGET to ${TARGET_PREFIX}gcc we need to ensure this is present by adding it to the recipe DEPENDS. Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2017-01-20python-sqlalchemy: uprev to latest in 1.0.x seriesMark Asselstine
According to the changelog at (http://docs.sqlalchemy.org/en/latest/changelog/changelog_10.html) this is mostly bug fixes. We need a version >= 1.0.10 to properly support the python-oslo.db uprev to stable/newton in meta-cloud-services. NOTE the license checksum has changed do to content change, not because the package license has changed, it is still MIT. Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2017-01-20python-sqlalchemy: Add 1.1.5Huang Qiyu
1) Copy the v1.0.9 bb to create python-sqlalchemy v1.1.5. 2) License checksum changed,since the copyright years were updated. Signed-off-by: Huang Qiyu <huangqy.fnst@cn.fujitsu.com> Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2017-01-17python-sqlalchemy: 1.0.8 -> 1.0.9Huang Qiyu
Upgrade python-sqlalchemy from 1.0.8 to 1.0.9. Signed-off-by: Huang Qiyu <huangqy.fnst@cn.fujitsu.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2017-01-14python-sphinx: 1.3.1 -> 1.4.1Huang Qiyu
1) Upgrade python-sphinx from 1.3.1 to 1.4.1 2) License checksum changed,since the copyright years were updated. Signed-off-by: Huang Qiyu <huangqy.fnst@cn.fujitsu.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2017-01-14python-webob 1.4.1 -> 1.6.0Huang Qiyu
Upgrade python-webob from 1.4.1 to 1.6.0. Signed-off-by: Huang Qiyu <huangqy.fnst@cn.fujitsu.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2017-01-14openvswitch: fix build host contaminationMark Asselstine
There is only a single PYTHON variable for configure and yet python is used for the build as well as scripts installed on the target. If we set a path in PYTHON as we had we end up using this same path during the build and since it isn't to the sysroot we end up with host contamination (as demonstrated by python failing to import 'six' on build hosts without python-six installed. The best approach is to set PYTHON to "python" when calling configure, ie. without a path. This will use 'python' from the path during build time and by ensuring all the installed scripts use '/usr/bin/env' we can ensure python will be found on the target when the scripts are run. Since 'six' is used as part of the build we have to ensure it is -native'ly buildable and we set all the required build and runtime dependencies. Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2017-01-03Remove True option to getVar callsPaul Barker
getVar() now defaults to expanding by default. Signed-off-by: Paul Barker <paul@paulbarker.me.uk> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2016-11-22protobuf: uprev 3.1.0 from 3.0.0Wenzong Fan
Signed-off-by: Wenzong Fan <wenzong.fan@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2016-10-21protobuf: ptest: Fix QA file-rdep warningHe Zhe
Add bash to ptest's RDEPENDS "WARNING: QA Issue: /usr/lib64/protobuf/ptest/run-ptest_protobuf-ptest contained in package protobuf-ptest requires /bin/bash, but no providers found in its RDEPENDS [file-rdeps]" Signed-off-by: He Zhe <zhe.he@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2016-10-21protobuf: Fix QA error for GNU_HASHHe Zhe
Add LDFLAGS to examples makefile to pass default ld flags. "ERROR: protobuf-3.0.0-r0 do_package_qa: QA Issue: No GNU_HASH in the elf binary: '.../protobuf/3.0.0-r0/packages-split/protobuf-ptest/usr/ lib/protobuf/ptest/add_person_cpp'" Signed-off-by: He Zhe <zhe.he@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2016-10-19go-cross: Fix failure if building go-cross firstJason Wessel
If go-cross is built as the first package it will fail creating the target libraries used for cross-compilation because it requires libgcc. Signed-off-by: Jason Wessel <jason.wessel@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2016-10-19go-native: Add work around for binutils >= 2.27Jason Wessel
We only use go-native to bootstrap go-cross and according to a post in the go-lang git it is possible to work around by disabling CGO: https://github.com/golang/go/issues/16906 This patch fixes the compile failure with binutils 2.27 which has the message: cannot load DWARF output from $WORK/net/_obj//_cgo_.o: decoding dwarf section info at offset 0x4: unsupported version 0 Signed-off-by: Jason Wessel <jason.wessel@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2016-10-12go-cross: Fix host contamination for x86_64 host to x86_64 targetJason Wessel
The go-cross package is explicitly for compiling target libraries on the host system. When the target architecture matches the host architecture it will actually use the host's linker and compiler however which can result in the generation of the cgo.a library having linker symbols which might not work properly when compiling other packages. A typical error looks like this when building consul-migrate: /opt/build-intel-x86/tmp/sysroots/x86_64-linux/usr/lib/x86_64-linux/go/pkg/tool/linux_amd64/link: running x86_64-yocto-linux-gcc failed: exit status 1 /opt/build-intel-x86/tmp/sysroots/x86_64-linux/usr/libexec/x86_64-yocto-linux/gcc/x86_64-yocto-linux/5.2.0/ld: /opt/build-intel-x86/tmp/work/core2-64-yocto-linux/consul-migrate/git-r0/build-tmp/go-link-956548052/000002.o: unrecognized relocation (0x2a) in section `.text' /opt/build-intel-x86/tmp/sysroots/x86_64-linux/usr/libexec/x86_64-yocto-linux/gcc/x86_64-yocto-linux/5.2.0/ld: final link failed: Bad value collect2: error: ld returned 1 exit status The fix is to use the make.bash --target-only option to properly build the libraries with the target toolchain. The "go" binaries are thrown away but the cross compilation libraries are preserved. The sysroot strip also has to be disabled because it will run the host strip on the target binaries. Signed-off-by: Jason Wessel <jason.wessel@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2016-09-23Revert "go-cross: Fix host contamination for x86_64 host to x86_64 target"Bruce Ashfield
This is breaking the build of go-cross on some machines: Log data follows: | DEBUG: Executing shell function do_compile | NOTE: make -j 20 static | ERROR: oe_runmake failed | /home/bruce/poky/build/tmp/work/core2-64-poky-linux/containerd/0.2.2+git0ac3cd1be170d180b2baed755e8f0da547ceb267-r0/git | cd ctr && go build -ldflags "-w -extldflags -static -X github.com/docker/containerd.GitCommit=0ac3cd1be170d180b2baed755e8f0da547ceb267 " -tags "" -o ../bin/ctr | cd containerd && go build -ldflags "-w -extldflags -static -X github.com/docker/containerd.GitCommit=0ac3cd1be170d180b2baed755e8f0da547ceb267 " -tags "" -o ../bin/containerd | cd containerd-shim && go build -ldflags "-w -extldflags -static -X github.com/docker/containerd.GitCommit=0ac3cd1be170d180b2baed755e8f0da547ceb267 " -tags "" -o ../bin/containerd-shim | # github.com/docker/docker/pkg/term | cannot load DWARF output from $WORK/github.com/docker/docker/pkg/term/_obj//_cgo_.o: decoding dwarf section info at offset 0x4: unsupported version 0 | make: *** [shim-static] Error 2 | make: *** Waiting for unfinished jobs.... | # github.com/docker/docker/pkg/term | cannot load DWARF output from $WORK/github.com/docker/docker/pkg/term/_obj//_cgo_.o: decoding dwarf section info at offset 0x4: unsupported version 0 | # github.com/opencontainers/runc/libcontainer/system | cannot load DWARF output from $WORK/github.com/opencontainers/runc/libcontainer/system/_obj//_cgo_ This reverts commit 7ff08e542d15b8e0104185768debf360044af7d1.
2016-09-22go-cross: Fix host contamination for x86_64 host to x86_64 targetJason Wessel
The go-cross package is explicitly for compiling target libraries on the host system. When the target architecture matches the host architecture it will actually use the host's linker and compiler however which can result in the generation of the cgo.a library having linker symbols which might not work properly when compiling other packages. A typical error looks like this when building consul-migrate: /opt/build-intel-x86/tmp/sysroots/x86_64-linux/usr/lib/x86_64-linux/go/pkg/tool/linux_amd64/link: running x86_64-yocto-linux-gcc failed: exit status 1 /opt/build-intel-x86/tmp/sysroots/x86_64-linux/usr/libexec/x86_64-yocto-linux/gcc/x86_64-yocto-linux/5.2.0/ld: /opt/build-intel-x86/tmp/work/core2-64-yocto-linux/consul-migrate/git-r0/build-tmp/go-link-956548052/000002.o: unrecognized relocation (0x2a) in section `.text' /opt/build-intel-x86/tmp/sysroots/x86_64-linux/usr/libexec/x86_64-yocto-linux/gcc/x86_64-yocto-linux/5.2.0/ld: final link failed: Bad value collect2: error: ld returned 1 exit status The fix is to use the make.bash --target-only option to properly build the libraries with the target toolchain. When the host architecture does not match the target architecture we must also force build the target libraries or they get dynamically populated into the sysroot in an uncontrolled manner by the first package that uses go-cross to compile code. Signed-off-by: Jason Wessel <jason.wessel@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
generated by cgit 1.2.3-korg (git 2.39.0) at 2024-04-28 18:44:59 +0000