summaryrefslogtreecommitdiff
path: root/meta/recipes-extended
AgeCommit message (Collapse)AuthorFiles
2018-03-11ethtool: refresh patchesRoss Burton1
The patch tool will apply patches by default with "fuzz", which is where if the hunk context isn't present but what is there is close enough, it will force the patch in. Whilst this is useful when there's just whitespace changes, when applied to source it is possible for a patch applied with fuzz to produce broken code which still compiles (see #10450). This is obviously bad. We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For that to be realistic the existing patches with fuzz need to be rebased and reviewed. Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-03-11cups: refresh patchesRoss Burton1
The patch tool will apply patches by default with "fuzz", which is where if the hunk context isn't present but what is there is close enough, it will force the patch in. Whilst this is useful when there's just whitespace changes, when applied to source it is possible for a patch applied with fuzz to produce broken code which still compiles (see #10450). This is obviously bad. We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For that to be realistic the existing patches with fuzz need to be rebased and reviewed. Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-03-09iptables: drop unnecessary patchesAlexander Kanavin3
These were adding definitions for the second time (see bug #10450 for why) or adding an include that isn't anymore necessary for musl builds. Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-03-09tcp-wrappers: refresh patchesRoss Burton1
The patch tool will apply patches by default with "fuzz", which is where if the hunk context isn't present but what is there is close enough, it will force the patch in. Whilst this is useful when there's just whitespace changes, when applied to source it is possible for a patch applied with fuzz to produce broken code which still compiles (see #10450). This is obviously bad. We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For that to be realistic the existing patches with fuzz need to be rebased and reviewed. Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-03-09parted: refresh patchesRoss Burton2
The patch tool will apply patches by default with "fuzz", which is where if the hunk context isn't present but what is there is close enough, it will force the patch in. Whilst this is useful when there's just whitespace changes, when applied to source it is possible for a patch applied with fuzz to produce broken code which still compiles (see #10450). This is obviously bad. We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For that to be realistic the existing patches with fuzz need to be rebased and reviewed. Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-03-09libpam: refresh patchesRoss Burton2
The patch tool will apply patches by default with "fuzz", which is where if the hunk context isn't present but what is there is close enough, it will force the patch in. Whilst this is useful when there's just whitespace changes, when applied to source it is possible for a patch applied with fuzz to produce broken code which still compiles (see #10450). This is obviously bad. We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For that to be realistic the existing patches with fuzz need to be rebased and reviewed. Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-03-09mdadm: refresh patchesRoss Burton2
The patch tool will apply patches by default with "fuzz", which is where if the hunk context isn't present but what is there is close enough, it will force the patch in. Whilst this is useful when there's just whitespace changes, when applied to source it is possible for a patch applied with fuzz to produce broken code which still compiles (see #10450). This is obviously bad. We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For that to be realistic the existing patches with fuzz need to be rebased and reviewed. Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-03-09libidn: refresh patchesRoss Burton1
The patch tool will apply patches by default with "fuzz", which is where if the hunk context isn't present but what is there is close enough, it will force the patch in. Whilst this is useful when there's just whitespace changes, when applied to source it is possible for a patch applied with fuzz to produce broken code which still compiles (see #10450). This is obviously bad. We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For that to be realistic the existing patches with fuzz need to be rebased and reviewed. Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-03-09ghostscript: drop incorrectly applied patchAlexander Kanavin2
The patch was adding a change to the source file that was already there, so the lines of code were repeated twice. This didn't create a bug or a security issue, but it may well have. Long story: https://bugzilla.yoctoproject.org/show_bug.cgi?id=10450 Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-03-09ghostscript: refresh patchesRoss Burton1
The patch tool will apply patches by default with "fuzz", which is where if the hunk context isn't present but what is there is close enough, it will force the patch in. Whilst this is useful when there's just whitespace changes, when applied to source it is possible for a patch applied with fuzz to produce broken code which still compiles (see #10450). This is obviously bad. We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For that to be realistic the existing patches with fuzz need to be rebased and reviewed. Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-03-09ethtool: refresh patchesRoss Burton1
The patch tool will apply patches by default with "fuzz", which is where if the hunk context isn't present but what is there is close enough, it will force the patch in. Whilst this is useful when there's just whitespace changes, when applied to source it is possible for a patch applied with fuzz to produce broken code which still compiles (see #10450). This is obviously bad. We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For that to be realistic the existing patches with fuzz need to be rebased and reviewed. Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-03-09bash: refresh patchesRoss Burton1
The patch tool will apply patches by default with "fuzz", which is where if the hunk context isn't present but what is there is close enough, it will force the patch in. Whilst this is useful when there's just whitespace changes, when applied to source it is possible for a patch applied with fuzz to produce broken code which still compiles (see #10450). This is obviously bad. We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For that to be realistic the existing patches with fuzz need to be rebased and reviewed. Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-03-09at: refresh patchesRoss Burton1
The patch tool will apply patches by default with "fuzz", which is where if the hunk context isn't present but what is there is close enough, it will force the patch in. Whilst this is useful when there's just whitespace changes, when applied to source it is possible for a patch applied with fuzz to produce broken code which still compiles (see #10450). This is obviously bad. We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For that to be realistic the existing patches with fuzz need to be rebased and reviewed. Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-03-08iptables: 1.6.1 -> 1.6.2Huang Qiyu1
Upgrade iptables from 1.6.1 to 1.6.2. Signed-off-by: Huang Qiyu <huangqy.fnst@cn.fujitsu.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-03-08libsolv: update to version 0.6.33Maxin B. John1
0.6.32 -> 0.6.33 * new Selection.clone() method in the bindings * new pool.parserpmrichdep() method in the bindings * fix bad assignment in solution refinement that led to a memory leak * use license tag instead of doc in the spec file [bnc#1082318] Signed-off-by: Maxin B. John <maxin.john@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-03-07libaio: refresh patchesRoss Burton1
The patch tool will apply patches by default with "fuzz", which is where if the hunk context isn't present but what is there is close enough, it will force the patch in. Whilst this is useful when there's just whitespace changes, when applied to source it is possible for a patch applied with fuzz to produce broken code which still compiles (see #10450). This is obviously bad. We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For that to be realistic the existing patches with fuzz need to be rebased and reviewed. Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-03-07lsb: refresh patchesRoss Burton1
The patch tool will apply patches by default with "fuzz", which is where if the hunk context isn't present but what is there is close enough, it will force the patch in. Whilst this is useful when there's just whitespace changes, when applied to source it is possible for a patch applied with fuzz to produce broken code which still compiles (see #10450). This is obviously bad. We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For that to be realistic the existing patches with fuzz need to be rebased and reviewed. Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-03-07screen: refresh patchesRoss Burton1
The patch tool will apply patches by default with "fuzz", which is where if the hunk context isn't present but what is there is close enough, it will force the patch in. Whilst this is useful when there's just whitespace changes, when applied to source it is possible for a patch applied with fuzz to produce broken code which still compiles (see #10450). This is obviously bad. We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For that to be realistic the existing patches with fuzz need to be rebased and reviewed. Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-03-07sysstat: refresh patchesRoss Burton1
The patch tool will apply patches by default with "fuzz", which is where if the hunk context isn't present but what is there is close enough, it will force the patch in. Whilst this is useful when there's just whitespace changes, when applied to source it is possible for a patch applied with fuzz to produce broken code which still compiles (see #10450). This is obviously bad. We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For that to be realistic the existing patches with fuzz need to be rebased and reviewed. Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-03-07unzip: refresh patchesRoss Burton1
The patch tool will apply patches by default with "fuzz", which is where if the hunk context isn't present but what is there is close enough, it will force the patch in. Whilst this is useful when there's just whitespace changes, when applied to source it is possible for a patch applied with fuzz to produce broken code which still compiles (see #10450). This is obviously bad. We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For that to be realistic the existing patches with fuzz need to be rebased and reviewed. Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-03-07watchdog: refresh patchesRoss Burton1
The patch tool will apply patches by default with "fuzz", which is where if the hunk context isn't present but what is there is close enough, it will force the patch in. Whilst this is useful when there's just whitespace changes, when applied to source it is possible for a patch applied with fuzz to produce broken code which still compiles (see #10450). This is obviously bad. We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For that to be realistic the existing patches with fuzz need to be rebased and reviewed. Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-03-07sysklogd: refresh patchesRoss Burton1
The patch tool will apply patches by default with "fuzz", which is where if the hunk context isn't present but what is there is close enough, it will force the patch in. Whilst this is useful when there's just whitespace changes, when applied to source it is possible for a patch applied with fuzz to produce broken code which still compiles (see #10450). This is obviously bad. We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For that to be realistic the existing patches with fuzz need to be rebased and reviewed. Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-03-06libconvert-asn1-perl: inherit ptest-perlTim Orling1
* Enable ptest using new ptest-perl.bbclass Signed-off-by: Tim Orling <timothy.t.orling@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-03-06diffutils: allow native & nativesdk buildsIoan-Adrian Ratiu1
Required by the new dtc rdepends to avoid errors like this: ERROR: Required build target 'ionel-rpi-image' has no buildable providers. Missing or unbuildable dependency chain was: ['ionel-rpi-image', 'nativesdk-packagegroup-sdk-host', 'nativesdk-qemu', 'nativesdk-dtc', 'nativesdk-diffutils'] Signed-off-by: Ioan-Adrian Ratiu <adi@adirat.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-03-06libxml-sax-perl: inherit ptest-perlTim Orling1
* Enable ptest by inheriting new ptest-perl.bbclass * Install testfiles/ into PTEST_PATH Signed-off-by: Tim Orling <timothy.t.orling@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-03-06libxml-sax-base-perl: inherit ptest-perlTim Orling1
* Enable ptest by inheriting new ptest-perl.bbclass Signed-off-by: Tim Orling <timothy.t.orling@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-03-06libtimedate-perl: inherit ptest-perlTim Orling1
* Enable pteset with new ptest-perl.bbclass Signed-off-by: Tim Orling <timothy.t.orling@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-03-03libpam: be more strict about user's sanityMartin Jansa3
* replace do_pam_sanity function with distro_features_check inherit * fixes: WARNING: libpam-1.3.0-r5 do_pam_sanity: Building libpam but 'pam' isn't in DISTRO_FEATURES, PAM won't work correctly in world builds and prevents user to build libpam at all without pam in DISTRO_FEATURES, I don't see any users of this which wouldn't respect pam in DISTRO_FEATURES * only libuser is depending on libpam without respecting DISTRO_FEATURES * there are few recipes in meta-oe layers depending on libpam without respecting DISTRO_FEATURES, I've sent patch for them: samba, openwsman, pam-ssh-agent-auth, sblim-sfcb, passwdqc, python-pam, smbnetfs and omxplayer in meta-raspberrypi, I've sent PR for that one: https://github.com/agherzan/meta-raspberrypi/pull/192 * poky-lsb will need to add pam to DISTRO_FEATURES in order to build packagegroup-core-lsb Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-02-24time: 1.7 -> 1.8Robert Yang3
* Remove debian.patch which is already in the source. * License-Update: The license is changed to GPLv3, and move v2 one to meta-gplv2. * Merge time.inc into time_1.8.bb. Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-02-24libtirpc: refresh patchesRoss Burton3
Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-02-24libtirpc: stop dropping in NIS headersRoss Burton1
libtirpc prior to 1.0.2 assumed that the system provided nis.h but this isn't always true. Until now we've been using a tarball of the missing files from Gentoo, but libtirpc 1.0.2 added a copy of nis.h to the sources so this isn't required anymore. Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-02-24libsolv: upgrade to version 0.6.32Maxin B. John1
0.6.31 -> 0.6.32 Signed-off-by: Maxin B. John <maxin.john@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-02-24sudo: 1.8.21P1 -> 1.8.22Huang Qiyu2
1.Upgrade sudo from 1.8.21P1 to 1.8.22. 2.Update the checksum of LIC_FILES_CHKSUM. The following content is appended to doc/LICENSE, plugins/sudoers/redblack.c. Todd C. Miller <Todd.Miller@courtesan.com> -> Todd C. Miller <Todd.Miller@sudo.ws> Signed-off-by: Huang Qiyu <huangqy.fnst@cn.fujitsu.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-02-24man-db: replace the outdated man implementationAlexander Kanavin34
Until now oe-core has been using a well obsolete implementation of man. Man-db on the other hand is used by all modern Linux distros, is actively maintained, has a standard build system, and does not require 30 patches to build. Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-02-24libpipeline: add a recipeAlexander Kanavin1
This is a hard dependency of man-db, which will be added in the following commit. Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-02-24pax: remove the recipeAlexander Kanavin9
The situation with pax (vs. tar and cpio) is perfectly described here: https://xkcd.com/927/ The only reason pax is still around, kind of, is because both POSIX and LSB mandate it. Outside of those documents, it's not used by anyone. Meanwhile, the upstream URI we've been taking it from went down, and rather than seek an alternative source, I just went ahead and removed the recipe. Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-02-16ltp: fix knob to control numa supportAnders Roxell4
Reported-by: Yi Zhao <yi.zhao@windriver.com> Signed-off-by: Anders Roxell <anders.roxell@linaro.org> Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-02-16ltp: fix fanotify06 testAnders Roxell2
Signed-off-by: Anders Roxell <anders.roxell@linaro.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-02-16packagegroup-core-full-cmdline: remove libraries from the system-services groupRoss Burton1
Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-02-16pakagegroups: don't pull in sysfsutilsRoss Burton1
sysfsutils is unmaintained and generally not needed. Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-02-16iputils: add missing Upstream-Status to patchAlexander Kanavin1
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-02-15pigz: use maintainer-built tarballsRoss Burton1
Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-02-15pigz: pigz is not gzipRoss Burton1
Whilst pigz is effectively a parallel gzip, the command line arguments are not the same so pigz isn't a drop-in replacement for gzip. [ YOCTO #12139 ] [ YOCTO #12410 ] Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-02-14ltp: Improve package strippingRichard Purdie1
Just exclude the specific tests which have an issue with being stripped rather than the whole package. This reduces the disk footprint by around 400MB. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-02-06iputils: update to 20161105Alexander Kanavin8
We've been using obsolete upstream URI for quite a while; meanwhile a lot of development has happened Drop all the patches: they are either changing the code that has been refactored, or are backports. Add a new musl fix patch from gentoo. ping6 and tracepath6 variants have been folded into standard versions. Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-02-06libsolv: upgrade to version 0.6.31Maxin B. John2
Remove upstreamed patch: 0001-repo_rpmdb.c-increase-MAX_HDR_CNT-and-MAX_HDR_DSIZE.patch Signed-off-by: Maxin B. John <maxin.john@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-02-06wget: update to 1.19.4Yi Zhao2
Update LIC_FILES_CHKSUM since replacing HTTP urls with HTTPS in COPYING Signed-off-by: Yi Zhao <yi.zhao@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-02-06pigz: 2.3.4 -> 2.4Hongxu Jia1
License-checksum-change: license is no change, only version bump up. https://github.com/madler/pigz/commit/fe822cb435622c43f491013da77b127e9fe851a9 Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-02-06tar: 1.29 -> 1.30Huang Qiyu3
1.Upgrade tar from 1.29 to 1.30. 2.Modify musl_dirent.patch, since the data has been changed. 3.Delete CVE-2016-6321.patch, since it is integrated upstream. Signed-off-by: Huang Qiyu <huangqy.fnst@cn.fujitsu.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-02-06ltp: remove patches that already have fixes upstreamAnders Roxell6
The following patches has already fixes for the issues they are solving in upstream. - 0001-add-_GNU_SOURCE-to-pec_listener.c.patch - 0011-Rename-sigset-variable-to-sigset1.patch - 0025-mc_gethost-include-sys-types.h.patch - 0027-sysconf01-Use-_SC_2_C_VERSION-conditionally.patch - 0033-shmat1-Cover-GNU-specific-code-under-__USE_GNU.patch Suggested-by: Yi Zhao <yi.zhao@windriver.com> Signed-off-by: Anders Roxell <anders.roxell@linaro.org> Signed-off-by: Ross Burton <ross.burton@intel.com>
generated by cgit v1.2.3 (git 2.25.1) at 2025-03-19 21:40:06 +0000