[Re: [OE-core] [PATCH 1/3] coreutils: don't generate useless dummy stub
manpages] On 11/02/2015 (Wed 09:51) ChenQi wrote:
> Hi Paul,
>
> The fix-for-dummy-man-usage.patch fixes error when generating dummy
> man pages.
> I think we should not delete it.
Sorry - just seeing this now since the mai
As can be seen here:
http://lists.gnu.org/archive/html/coreutils/2014-11/msg1.html
other people have run into the headache of trying to cross compile
coreutils, with the "help2man" problem (assumes host can run the
target binaries with "--help" arg to collect data for manpage.)
And since "cu
We had a couple patches to 1) deal with missing perl and 2) deal
with the perl-less "dummy" help2man fallout, but in the end, they
achieve no purpose whatsoever, since they just populate the doc
RPM with manpages like this one:
NAME
chmod - a GNU coreutils 8.22 program
DESCRIPTION
As part of improving the end user experience for installs where the
end user interacts directly with the generated filesystem (e.g. the
build-appliance) these three commits ensure that we can have real
man pages for coreutils on the target if desired.
This has been problematic for everyone who cro
This was added to try and deal with the cross compile issue of
help2man ; one can not run an ARM binary "./chmod --help" on an
x86-64 host in order to get the help text to create a man page.
This has been primarily an issue with the coreutils package.
However, we have since fixed coreutils to have
If /etc/login.defs is treated as a configuration file, then we would meet
errors at do_rootfs time telling us that useradd/groupadd cannot execute
correctly.
This is because the dpkg handles config file specially, the login.defs
is temporarily renamed as login.defs.dpkg-new.
How ubuntu deals the
We need to use 'purge' instead of 'remove' for debian package backend when
removing packages at rootfs time. This is because that 'remove' command for
'dpkg' and 'apt-get' does not remove configuration files.
Signed-off-by: Chen Qi
---
meta/lib/oe/package_manager.py | 4 ++--
1 file changed, 2 i
Use '-f' ('--force') option so that while removing packages using deb,
we don't fail because of the following error:
update-rc.d: $initd/$bn exists during rc.d purge (use -f to force)
Using '-f' option would make this a warning but continue to execute.
update-rc.d: $initd/$bn exists during
Allow globs in CONFFILES.
This patch changes the way of CONFFILES handling. After this change,
the CONFFILES can take the same form as FILES. That means, we don't
have to list a bunch of files for CONFFILES. It will just be expanded
like the FILES variable.
We don't assume default value for CONF
The following changes since commit d5af8539c0a1718a7254bcdcfa973e3c887dfbd6:
syslinux: support ext2/3/4 device (2015-02-15 08:11:19 +)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib ChenQi/CONFFILES
http://cgit.openembedded.org/cgit.cgi/op
Hi
Am Freitag, den 13.02.2015, 14:51 + schrieb Richard Purdie:
> On Fri, 2015-02-13 at 13:44 +0100, Max Krummenacher wrote:
> > Hi
> >
> > If a recipe builds a package for the default ARCH (I think this is
> > ${TUNE_PKGARCH}) and one for ARCH 'all' then this fails when building
> > in the s
On Wed, Jul 16, 2014 at 07:04:04PM +0200, Martin Jansa wrote:
> * otherwise it triggers following ICE:
> ERROR: Function failed: do_compile (log file is located at
> /OE/build/shr-core/tmp-eglibc/work/arm920tt-oe-linux-gnueabi/icu/53.1-r0/temp/log.do_compile.21570)
> ERROR: Logfile of failure stor
Sometimes you do not want certain packages to be installed when
installing complementary packages, e.g. when using dev-pkgs in
IMAGE_FEATURES you may not want to install all packages from a
particular multilib. This introduces a new PACKAGE_EXCLUDE_COMPLEMENTARY
variable to allow specifying regexes
The following change since commit d5af8539c0a1718a7254bcdcfa973e3c887dfbd6:
syslinux: support ext2/3/4 device (2015-02-15 08:11:19 +)
is available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib
paule/exclude-complementary
http://cgit.openembedded.org/c
On Mon, Feb 16, 2015 at 12:36 PM, Richard Purdie
wrote:
> I have to admit I've lost track of time a bit however the calender says
> Milestone 3 (M3) finishes this week and that marks "feature freeze" for
> the release. Beyond this point we have M4 which which is targeted for
> bug fixing only, no
I have to admit I've lost track of time a bit however the calender says
Milestone 3 (M3) finishes this week and that marks "feature freeze" for
the release. Beyond this point we have M4 which which is targeted for
bug fixing only, no extra features and no package upgrades in general.
I'm therefore
On Mon, 2015-02-16 at 15:07 -0200, Otavio Salvador wrote:
> On Mon, Feb 16, 2015 at 2:24 PM, Richard Purdie
> wrote:
> > Add a check to the SDK so that it only runs on systems with kernel versions
> > it supports.
> >
> > [YOCTO #6856]
> >
> > Signed-off-by: Richard Purdie
> >
> > diff --git a/me
On Mon, Feb 16, 2015 at 2:24 PM, Richard Purdie
wrote:
> Add a check to the SDK so that it only runs on systems with kernel versions
> it supports.
>
> [YOCTO #6856]
>
> Signed-off-by: Richard Purdie
>
> diff --git a/meta/classes/populate_sdk_base.bbclass
> b/meta/classes/populate_sdk_base.bbcla
Add a check to the SDK so that it only runs on systems with kernel versions
it supports.
[YOCTO #6856]
Signed-off-by: Richard Purdie
diff --git a/meta/classes/populate_sdk_base.bbclass
b/meta/classes/populate_sdk_base.bbclass
index 8b7e9ea..e3adacb 100644
--- a/meta/classes/populate_sdk_base.b
Drop patch merged upstream.
Signed-off-by: Richard Purdie
---
.../{libtool-2.4.5.inc => libtool-2.4.6.inc} | 5 +-
...btool-cross_2.4.5.bb => libtool-cross_2.4.6.bb} | 0
...ool-native_2.4.5.bb => libtool-native_2.4.6.bb} | 0
...-t-execute-automake-and-autoconf-on-every.patch | 71
From: "Peter A. Bigot"
Signed-off-by: Peter A. Bigot
---
meta/recipes-connectivity/neard/neard.inc | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-connectivity/neard/neard.inc
b/meta/recipes-connectivity/neard/neard.inc
index 31bc6dd..6b6b1da 100644
--- a/m
From: "Peter A. Bigot"
Signed-off-by: Peter A. Bigot
Signed-off-by: Cristian Iorga
---
meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad.inc| 4 ++--
meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad_git.bb | 1 -
2 files changed, 2 insertions(+), 3 deletions(-)
diff --g
If BlueZ5 is added to a build as a replacement for BlueZ4,
the provider for bluez-hcidump will be bluez5.
Signed-off-by: Cristian Iorga
---
meta/conf/distro/include/default-providers.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/conf/distro/include/default-provider
From: "Peter A. Bigot"
Signed-off-by: Peter A. Bigot
---
meta/recipes-connectivity/libpcap/libpcap.inc | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-connectivity/libpcap/libpcap.inc
b/meta/recipes-connectivity/libpcap/libpcap.inc
index a12eb16..979665c
From: "Peter A. Bigot"
Signed-off-by: Peter A. Bigot
Signed-off-by: Cristian Iorga
---
meta/recipes-connectivity/ofono/ofono.inc | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/meta/recipes-connectivity/ofono/ofono.inc
b/meta/recipes-connectivity/ofono/ofono.inc
inde
From: Richard Purdie
bitbake will currently 'selecting bluez4 to satisfy runtime
libasound-module-bluez due to PREFERRED_PROVIDER_bluez4 = bluez4'
which in the case of bluez5 isn't correct.
This slightly unusual construct avoids this.
Ultimately this is a bitbake issue that needs fixing in
a bett
From: "Peter A. Bigot"
connman currently supports both bluez4 and bluez5 without distinguishing
them at configuration time.
Signed-off-by: Peter A. Bigot
Signed-off-by: Cristian Iorga
---
meta/recipes-connectivity/connman/connman.inc | 8 +---
1 file changed, 5 insertions(+), 3 deletions(
From: "Peter A. Bigot"
Signed-off-by: Peter A. Bigot
---
meta/recipes-core/packagegroups/packagegroup-base.bb | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/meta/recipes-core/packagegroups/packagegroup-base.bb
b/meta/recipes-core/packagegroups/packagegroup-base.bb
index
From: "Peter A. Bigot"
Defines ${BLUEZ} to be the provider of bluez services as specified by
DISTRO_FEATURES.
Example recipe fragment:
inherit bluetooth
PACKAGECONFIG ??= "${@bb.utils.contains('DISTRO_FEATURES', 'bluetooth',
'${BLUEZ}', '', d)}
PACKAGECONFIG[bluez4] = "--enable-bluetooth,
From: "Peter A. Bigot"
Signed-off-by: Peter A. Bigot
---
meta/recipes-qt/qt4/qt-mobility_1.2.0.inc | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-qt/qt4/qt-mobility_1.2.0.inc
b/meta/recipes-qt/qt4/qt-mobility_1.2.0.inc
index ae1769d..b3d23d4 100644
--- a
From: "Peter A. Bigot"
Signed-off-by: Peter A. Bigot
---
meta/recipes-multimedia/pulseaudio/pulseaudio.inc | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-multimedia/pulseaudio/pulseaudio.inc
b/meta/recipes-multimedia/pulseaudio/pulseaudio.inc
index 99cad76
Based on Peter A. Bigot Bluez5 switch patchset.
Full credit given to original authors.
Some changes/adaptations needed, all doneand implemented by Cristian Iorga.
Tested with each Bluetooth stack provider.
The following changes since commit 6ae933b75c1c34a9d39e1aff0a0cb26a7ce4677f:
bitbake: tes
On Mon, Feb 16, 2015 at 02:04:50PM +0100, Stéphane Cerveau wrote:
> The website http://wireless.kernel.org/download does not provide
> crda and binary anymore.
Wrong ML, see README and should go to openembedded-devel ML.
>
> Signed-off-by: Stéphane Cerveau
> ---
> .../recipes-connectivity/crda
On Mon, Feb 16, 2015 at 03:35:32PM +0100, Sven Ebenfeld wrote:
> Am 16.02.2015 um 14:51 schrieb Brendan Le Foll:
> >
> > No real reason, was trying to keep it as simple as possible whilst
> > making it clear it was not a good idea to re-enable it. I can make it
> > a PACKAGECOUNFIG[ssl3] = "--no-s
Am 16.02.2015 um 14:51 schrieb Brendan Le Foll:
>
> No real reason, was trying to keep it as simple as possible whilst
> making it clear it was not a good idea to re-enable it. I can make it
> a PACKAGECOUNFIG[ssl3] = "--no-ssl3" if you think that's best.
Shouldn't it be PACKAGECOUNFIG[nossl3] ?
On Sat, Feb 14, 2015 at 6:48 PM, Holger Hans Peter Freyther
wrote:
> I want to use the multiple defaults route feature of the
> kernel but I want to install some routes that are more
> important than the link managed with dhcp. The only way
> I can think of is to change the "metric=0" to a "metric
On Mon, Feb 16, 2015 at 02:10:03PM +0100, Martin Jansa wrote:
> On Mon, Feb 16, 2015 at 11:18:29AM +, brendan.le.f...@intel.com wrote:
> > From: Brendan Le Foll
> >
> > Because of the SSLv3 POODLE vulnerability, it's preferred to simply disable
> > SSLv3 even if patched with the TLS_FALLBACK_
Dear Martin,
I'm using dora and daisy branch and the build will be failing on this
branch 1.1.3.
Is it planned to backport thee 3.13 patch to dora and daisy ?
I just posted a patch to use the 1.1.3 as before but is there a license
issue, so we cant use this version anymore ?
Best regards.
On Mon, Feb 16, 2015 at 11:18:29AM +, brendan.le.f...@intel.com wrote:
> From: Brendan Le Foll
>
> Because of the SSLv3 POODLE vulnerability, it's preferred to simply disable
> SSLv3 even if patched with the TLS_FALLBACK_SCSV
>
> Signed-off-by: Brendan Le Foll
> ---
> meta/recipes-connecti
On Mon, Feb 16, 2015 at 12:04:49PM +0100, scerveau wrote:
> Dear all,
>
> It seems that crda_1.1.3 recipe is broken according that the link
> http://wireless.kernel.org/download/crda/crda-1.1.3.tar.bz2 is not
> available anymore.
> It can be now downloaded here
> https://www.kernel.org/pub/soft
The website http://wireless.kernel.org/download does not provide
crda and binary anymore.
Signed-off-by: Stéphane Cerveau
---
.../recipes-connectivity/crda/crda_1.1.3.bb| 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/meta-networking/recipes-connectivity/c
From: Brendan Le Foll
SSLv3 should be disabled because of POODLE, this patch disables it completely
Brendan Le Foll (1):
openssl: disable SSLv3 by default
meta/recipes-connectivity/openssl/openssl.inc | 4
1 file changed, 4 insertions(+)
--
2.2.1
--
_
From: Brendan Le Foll
Because of the SSLv3 POODLE vulnerability, it's preferred to simply disable
SSLv3 even if patched with the TLS_FALLBACK_SCSV
Signed-off-by: Brendan Le Foll
---
meta/recipes-connectivity/openssl/openssl.inc | 4
1 file changed, 4 insertions(+)
diff --git a/meta/recip
Dear all,
It seems that crda_1.1.3 recipe is broken according that the link
http://wireless.kernel.org/download/crda/crda-1.1.3.tar.bz2 is not
available anymore.
It can be now downloaded here
https://www.kernel.org/pub/software/network/crda/crda_1.1.3.tar.bz2
But concerning the binary
http:
On Fri, 2015-02-13 at 09:39 +0800, Hongxu Jia wrote:
> On 02/13/2015 12:46 AM, Paul Eggleton wrote:
> >> default_archs) +new_pkg =
> >> >self._search_pkg_name_in_feeds(pkg, default_archs) or \ +
> >> > self._search_pkg_provider_in_smart(pkg, default_archs) if not new_pkg:
> >> >
Hi Ross,
On 02/13/2015 06:53 PM, Burton, Ross wrote:
As nothing else in oe-core needs there right now, I'd suggest that neardal
should be in meta-connectivity and libedit is already in meta-oe
(https://github.com/openembedded/meta-openembedded/blob/master/meta-oe/recipes-devtools/libedit/libed
46 matches
Mail list logo
