summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* bitbake: server/xmlrpc: stop server on client exitAlexandru DAMIAN2013-09-011-0/+5
| | | | | | | | | | | | If the server only expects a single client to connect (i.e. no bind parameter set, so there is no way for the clients to get the server port), stop the server after the first client exits. (Bitbake rev: eb6bae56f62082bf147045311154cbae4bca0f4c) Signed-off-by: Alexandru DAMIAN <alexandru.damian@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: prserv/serv: Settle on two threads for optimal performanceRichard Purdie2013-09-011-14/+34
| | | | | | | | | | | | Using the threading mixin class resulted in large amounts of memory being used by the PR server for no good reason. Using a receiver thread and a thread to do the actual database operations on a single connection gives the same performance with a much saner memory overhead so switch to this. (Bitbake rev: e08455d5f3b8e96765942b9c3b9767c30650557d) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: build: Fix profile file namesRichard Purdie2013-09-011-1/+1
| | | | | | | | | | | | | Using the basename of the .bb file is not unique, for example xxx-native and xxx can overwrite each other. If this happens whilst running, you can get odd backtraces as one file is parsed as another tries to write out new data. Avoid issues by using PN for the output filename instead. (Bitbake rev: c9534f8e59d44b885334607ed90a3be2e492ec69) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: serv/db: Don't use BEGIN/COMMITRichard Purdie2013-09-011-13/+3
| | | | | | | | | | Since we don't support using multiple servers on the same database file, don't use the BEGIN/COMMIT syntax and allow writes to the database to work ~100 times faster with no transaction locking. (Bitbake rev: 42144a54979658f93fbbb43f7e271c1fff4d88ff) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: serv/db: Take an excluside lock on the databaseRichard Purdie2013-09-011-1/+1
| | | | | | | | | We only support one server using the database at a time so take an exclusive lock and avoid later lock overhead. (Bitbake rev: e3e39be6f2d063858c92971ce8ccd89c95d4f26d) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: serv/db: Fix looping upon database locked issuesRichard Purdie2013-09-011-3/+4
| | | | | | | | | | | | | If the database is locked we will get an immediate error indicating so, there is no retry timeout. The looping code is therefore useless, the loop count is near instantly exceeded. Using a time based retry means we can wait a sensible time, then gracefully exit. (Bitbake rev: 9f9e6d87007ea87e62495705464f4232c996a165) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: server/process, server/xmlrpc, runqueue: Use select.select() on ↵Richard Purdie2013-09-013-21/+28
| | | | | | | | | | | | | | | | | | | | | | fds, not time.sleep() The existing backend server implementations were inefficient since they were sleeping for the full length of the timeouts rather than being woken when there was data ready for them. It was assumed they would wake and perhaps did when we forked processes directory but that is no longer the case. This updates both the process and xmlrpc backends to wait using select(). This does mean we need to pass the file descriptors to wait on from the internals who know which these file descriptors are but this is a logical improvement. Tests of a pathaolgical load on the process server of ~420 rapid tasks executed on a server with BB_NUMBER_THREAD=48 went from a wall clock measurement of the overall command execution time of 75s to a much more reasonable 24s. (Bitbake rev: 9bee497960889d9baa0a4284d79a384b18a8e826) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Edits to figuresScott Rifenbark2013-08-3010-0/+0
| | | | | | | | | | I updated several figures to implement some of Dave Stewart's review feedback for the expanded section on the build process. (From yocto-docs rev: abd78cd6eaad8173ef8f9b3376c323875e5c4542) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Minor edit.Scott Rifenbark2013-08-301-3/+1
| | | | | | | | | | Removed the bit about the bold text representing a layer. I changed the figure so I am not following that convention. (From yocto-docs rev: 119b64be029e15e5c588a5e6c8dd9e0ac1a79c8c) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual, mega-manual: Edits for expanded packaging descriptionScott Rifenbark2013-08-303-21/+33
| | | | | | | | | | | | | | | Fixes [YOCTO #2808] Applied review comments to the package splitting section in the section that digs deeper into the build process. This involved updating the figure that resides in both "figures" directories of the ref-manual and the mega-manual. Also updated supporting text throughout the section per Paul's comments. (From yocto-docs rev: 34e3610d0c6912530f678e9f1fa4587aaaf9fc70) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: New variables descriptions for PKGDATA_DIR and PKGDESTWORKScott Rifenbark2013-08-301-0/+36
| | | | | | | (From yocto-docs rev: a5c3663f6fa6e8f98a7626b99b5ad9ca2058670b) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lib/oeqa/runtime: ping: fix ping false failStefan Stanacar2013-08-301-3/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We run the ping test as soon as we reach the login prompt. But sometimes (seen in sato systemd) we end up with link down/link up stuff like: qemux86-64 login: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready The logic behind ping -w 30 -c 1 was to wait at most 30 seconds for at least one reply, but there is a catch: reply doesn't seems to be echo reply but any reply (non-reply means loss not network error) ping's man page: -w deadline Specify a timeout, in seconds, before ping exits regardless of how many packets have been sent or received. In this case ping does not stop after count packet are sent, it waits either for deadline expire or until count probes are answered or for some error notification from network. Just when the link up/link down happens ping returns: From 192.168.7.1 icmp_seq=1 Destination Host Unreachable --- 192.168.7.2 ping statistics --- 1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms and exits sooner than the 30 seconds timeout. This patch should do what was originally intended (wait at most 30 seconds for at least one reply). (From OE-Core rev: 56d144fd22d37189e49cdf3032afb00f0be469c6) Signed-off-by: Stefan Stanacar <stefanx.stanacar@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python: Backport 2 CVE from upstreamSaul Wold2013-08-303-0/+288
| | | | | | | | | | | These are back ports of 2 patches from upstream to address CVE-2011-4944 CVE-2013-4238 (From OE-Core rev: 4606eab53e8eff57d6369ea20a5ea63916ea3ea7) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* perl: Backport 2 CVE PatchesSaul Wold2013-08-303-0/+267
| | | | | | | | | | | | | These patches are backported from upstream since it might be risky to update right now They address the following CVEs CVE-2012-6329 CVE-2013-1667 (From OE-Core rev: b6c286c447e50fe499f03b64c6be80ac18504265) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* btrfs-tools: Add dependency on lzo acl e2fsprogsRoy.Li2013-08-301-1/+1
| | | | | | | | | | | | | | | | | | Add dependency on lzo acl e2fsprogs to fix the below building failure 1. commit b268a417259b9[add lzo compression support to restore] needs lzo cmds-restore.c:30:25: fatal error: lzo/lzoconf.h: No such file or directory 2. btrfs-tools includes <sys/acl.h> which is provided by acl btrfs-convert.c:32:21: fatal error: sys/acl.h: No such file or directory 3. btrfs-tools always needs e2fsprogs btrfs-convert.c:44:28: fatal error: ext2fs/ext2_fs.h: No such file or directory (From OE-Core rev: 51bb56a19f03e341a0b46199dddbbc3e9b209904) Signed-off-by: Roy.Li <rongqing.li@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* systemd: use /bin/mkdir instead of host mkdir pathJonathan Liu2013-08-302-0/+32
| | | | | | | | (From OE-Core rev: 9ee883f2f9f36f6d5cca56ac5f179468dfa5b686) Signed-off-by: Jonathan Liu <net147@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-4.8: fix ICE of cross-compile for PowerPC e500v2 targetsChunrong Guo2013-08-302-0/+22
| | | | | | | | | | | | | | | * http://gcc.gnu.org/bugzilla//show_bug.cgi?id=57717#c7 * fix the segfault issue of dd on e500v2 targets Since double-float is disabled for e500v2 targets build due to ICE of gcc-4.8.1, accordingly %Ld format of sprintf is disabled. Address Bug 4910 - [p1022ds]urandom: segmentation fault (From OE-Core rev: a4fefac26d91bc56d5d28e1c9973a189d2509d45) Signed-off-by: Chunrong Guo <B40290@freescale.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libsamplerate0: add PACKAGECONFIG for fftwRoy.Li2013-08-301-0/+2
| | | | | | | | | | fftw is autodetected from sysroot, add PACKAGECONFIG to make it deterministic (From OE-Core rev: 5e00319ea942764ed2e7d6bc8c74e5d48166231b) Signed-off-by: Roy.Li <rongqing.li@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mesa: add missing elfutils dependency for r600 PACKAGECONFIGJonathan Liu2013-08-301-2/+4
| | | | | | | | | | | Fixes the following configure error: configure:23490: error: radeonsi and r600g require libelf when using LLVM (From OE-Core rev: 43e7f168c84128b5d48bbfde9d6c07f2fb656b00) Signed-off-by: Jonathan Liu <net147@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bluez4: fix network Connect parameter validationPeter A. Bigot2013-08-302-0/+31
| | | | | | | | | | | The incorrect validation prevents connection to the NAP service on another device. (From OE-Core rev: 895a0840e82ddfd05c4441b7f8f358e27e6cb38a) Signed-off-by: Peter A. Bigot <pab@pabigot.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* multilib.bbclass: Expand the WHITELISTs with multilib prefixJackie Huang2013-08-301-0/+7
| | | | | | | | | | | | fix the following failures: ERROR: Nothing PROVIDES 'virtual/lib32-i586-pokymllib32-linux-compilerlibs' ERROR: Nothing RPROVIDES 'lib32-update-alternatives-cworth' (From OE-Core rev: a27d5b08d438861309827aecb731c29218679730) Signed-off-by: Jackie Huang <jackie.huang@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oe-setup-rpmrepo: add native sysroot so nativepython can be found by envPeter A. Bigot2013-08-301-0/+1
| | | | | | | | | | | | | | This avoids the following new behavior resulting from the create_wrapper fixes: llc[11]$ ../poky/scripts/oe-setup-rpmrepo /usr/bin/env: nativepython: No such file or directory (From OE-Core rev: ce37ef05c14ba28773823d1f14f629c37c76d827) Signed-off-by: Peter A. Bigot <pab@pabigot.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* recipes: Ensure that we only apply poky changes when poky is selectedRichard Purdie2013-08-302-2/+2
| | | | | | (From meta-yocto rev: 5bd26f2d294f10d9119c6b81d0b368198ee96ed9) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: prserv: Allow 'table is locked' matching for retry loopRichard Purdie2013-08-301-1/+1
| | | | | | | | | Try and avoid errors like "ERROR: database table is locked: PRMAIN_nohist" by retrying if we see the string "is locked". (Bitbake rev: 1a175b51f80d13f747b653d29e9c0d2201b5109c) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: server/xmlrpc: Increase timeout to 60sRichard Purdie2013-08-301-1/+1
| | | | | | | | | | | | This is a better value that the earlier infinite timeout yet still allows for servers with high loads. It does mean the bitbake process can hang at exit for the timeout period but that should never happen and only happened for me in some test cases which wouldn't happen in normal use. (Bitbake rev: ab8d926b9bc27c58011e7db9327e031ac76ba34b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: cookerdata: Allow bblayers.conf to be found using BBPATHRichard Purdie2013-08-301-8/+15
| | | | | | | | | | | | | | | It should be possible to run a build anywhere on the filesystem and have bitbake find the correct build directory if its set somehow. The BBPATH variable makes perfect sense for this usage. Therefore use any available value of BBPATH to search for conf/bblayers.conf before walking the parent directory structure. This restores the option of being able to run bitbake from anywhere if the user has set things up to operate in that environment. (Bitbake rev: e86336b3fe245bc97fe74c9b9d6a21d38a536fb7) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: cookerdata: Set TOPDIR when using bblayers.confRichard Purdie2013-08-301-0/+3
| | | | | | | | | | | | | By definition, bblayers.conf is at the top of the build tree. We'd like to support running bitbake anywhere within that build tree but TOPDIR gets set to wherever cwd is. Change the code to reset TOPDIR to the top of the build directory. This shouldn't break anything but does make the system more usable. (Bitbake rev: b266db27de0bba19a418e4d42e870649136b116b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* web-webkit: Drop, we have midori nowRichard Purdie2013-08-303-31/+1
| | | | | | | | | | | This was never a particularly useful browser and is a dead codebase, retire it and suggest midori instead. [YOCTO #2318] (From OE-Core rev: 3883d2cb03fb79fa39a7d85505c79784a996f178) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* runqemu-ifdown: clean up the remaining iptables rulesChen Qi2013-08-301-0/+14
| | | | | | | | | | | | | | | | The iptables rules for the tap interface are added by runqemu-ifup everytime we use runqemu to start a qemu target. But it's not cleaned up when runqemu exits. This patch cleans up the remaining iptables rules for the tap interface in runqemu-ifdown. [YOCTO #5047] (From OE-Core rev: ef38a0aed35357d035ca587162158cd2f55b958f) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* runqemu-internal: provide more info if a preconfigured tap is usedChen Qi2013-08-301-0/+1
| | | | | | | | | | | | | | | | We should provide the user more information if a preconfigured tap is used. This is because the user might have manually set up the tap interface to be used by other qemu binaries. So at a minimum, we should let the user know how to make runqemu skip that tap interface. [YOCTO #5047] (From OE-Core rev: ec08d92641cc51c567cc3745937b1839d3faa095) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* runqemu-internal: don't bring down preconfigured tap interfaceChen Qi2013-08-301-1/+3
| | | | | | | | | | | runqemu-ifup and runqemu-ifdown should be pairs. If we're using a preconfigured tap interface, the runqemu-ifdown should not be invoked to bring it down. (From OE-Core rev: f60f215f74b5fe5a43943c9d3ccdbe0fa06b7828) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lib/oeqa/runtime: syslog: fix test for logger in case of systemdStefan Stanacar2013-08-301-1/+1
| | | | | | | | | | | Recently syslog behaviour changed for systemd images (log it's in a buffer not in /var/log/messages), account for the new stuff. (From OE-Core rev: 32576c4cc1621fa3013eac66c7caaa1e1fd14995) Signed-off-by: Stefan Stanacar <stefanx.stanacar@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* list-packageconfig-flags.py: fix searching bitbake module failedHongxu Jia2013-08-301-7/+25
| | | | | | | | | | | | | | | | | | | | | | | | Run list-packageconfig-flags.py on wrlinux's platform in which the oe-core layer and bitbake layer in different directories: ---- ../layers/oe-core/scripts/contrib/list-packageconfig-flags.py Traceback (most recent call last): File "../layers/oe-core/scripts/contrib/list-packageconfig-flags.py", line 28, in <module> import bb.cache ImportError: No module named bb.cache ---- The script import bb module from bitbake lib dir, the previous lib dir was hardcode and only worked on poky but not for others. In this situation, look for bitbake/bin dir in PATH could fix this issue. [YOCTO #5060] (From OE-Core rev: 9e749c430f97b1a30cdf0c13dacd2a985ef7b433) Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gtk+3: pull forward the gtk+2 hardcoded libtool patchChristopher Larson2013-08-302-0/+36
| | | | | | | | | | | | | | | Without this, it tries to run ./libtool, not the sys-prefixed libtool, which fails, resulting in dynamic modules being disabled, which in turn results in compiling the immodules directly into the gtk+3 library. I tried switching it to using $LIBTOOL rather than hardcoding the path, as LT_INIT sets LIBTOOL, but it didn't work, I didn't have time to dig further, and this gets the job done for now. (From OE-Core rev: f74e456772fc80c2333fbdf57c629a18412375e8) Signed-off-by: Christopher Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gtk+3: only set GTKIMMODULES_PACKAGES if we have immodulesChristopher Larson2013-08-301-1/+4
| | | | | | | (From OE-Core rev: 9191c8b08ea25641d228acc83f2d4ad6a14333fe) Signed-off-by: Christopher Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lib/oeqa/utils: qemurunner: fix when runqemu errors outStefan Stanacar2013-08-301-2/+2
| | | | | | | | | | | | | When qemu doesn't start or runqemu errors out (some wrong option passed or sudo needs a password for setting tap) we want to display the output but oe-core commit 9de7fe11967576f4a8b24e653c6b9a02e5f6d85b/ poky commit 51588936d4a8cde3c9bb05800240c0a0f5dedf8d changed the kill method and broke this code, so let's fix it. (From OE-Core rev: 923d4bd548911caa0b419c10905895af1e8e7026) Signed-off-by: Stefan Stanacar <stefanx.stanacar@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lttng-ust: Update to version 2.2.1Tom Zanussi2013-08-303-62/+2
| | | | | | | | | | | | | Update lttng-ust to version 2.2.1 to correspond to the LTTng 2.2 "Cuda" - Tracer toolchain stable release. This also removes all the local lttng-ust patches, which are now upstream. (From OE-Core rev: 3f856556972617560b24cc86bfab027bed83bd49) Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lttng-tools: Update to version 2.2.3Tom Zanussi2013-08-301-2/+2
| | | | | | | | | | Update lttng-tools to version 2.2.3 to correspond to the LTTng 2.2 "Cuda" - Tracer toolchain stable release. (From OE-Core rev: 303abf7f2d8e79e8d14ce5b9aff287347aae43be) Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* util-linux: package mkfs.cramfs and fsck.cramfsAndrea Adami2013-08-301-0/+5
| | | | | | | | | The recipe builds the two utils which are unpackaged. (From OE-Core rev: a8212a5170940b9ba9ca7a594b65939b06aac86c) Signed-off-by: Andrea Adami <andrea.adami@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* image_types.bbclass: use mkfs.cramfs instead of makecramfsAndrea Adami2013-08-301-2/+2
| | | | | | | | | | | | The former is provided by util-linux and the latter is now to be removed for meta-filesystems. This allows to generate cramfs images whithout extra layers. (From OE-Core rev: 451546a9d2f675ac331f72f4e66317685d931aba) Signed-off-by: Andrea Adami <andrea.adami@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* busybox: configure system user id to range from 100 to 999Chen Qi2013-08-301-2/+2
| | | | | | | | | | | | | | | Previously, the range was 0 to 0. This made it impossible to use busybox's adduser utility to add a system user. The following error would appear. adduser: no uids left This patch fixes this problem by giving it a reasonable range. (From OE-Core rev: c4555007d04ccacbc192827b70a97f9a48500a22) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* packagegroup-self-hosted: Add missing python codeSaul Wold2013-08-301-0/+6
| | | | | | | | | | | These are in the Toolchain list, so they should also be installed on the build appliance [YOCTO #5061] (From OE-Core rev: 82374feece5c576f9950bad6861b1e00c6b30d84) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: upgrade to commit ↵Cristian Iorga2013-08-301-1/+1
| | | | | | | | | | | | | | | 5745e45b18e5099e94b4d5a73bc97dc6d4cdc91f Improvements to poky gets in this way reflected in Build Appliance. Notable improvements/fixes to bitbake. New hardware targets. (From OE-Core rev: ced23e66ad3c255fdccfba24301c99cb60832cff) Signed-off-by: Cristian Iorga <cristian.iorga@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* remove the unnecessary protocol parametersJackie Huang2013-08-3098-100/+100
| | | | | | | | | | | It's not necessary to specify the protocol parameter when it's the default protocol for the fetcher, e.g. the default protocol for git fetcher it git, "protocol=git" isn't needed. (From OE-Core rev: a2bab241c64428d5109c3c5ac5de4463fbad70c5) Signed-off-by: Jackie Huang <jackie.huang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* builder: register html links and files with MidoriMihai Prica2013-08-301-1/+7
| | | | | | | | | | | HTML files and links will open in a tab in Midori. [YOCTO #3506] (From OE-Core rev: 1177aee9a6761a6a46a6213f7c4d35827ea54022) Signed-off-by: Mihai Prica <mihai.prica@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* packagegroup-self-hosted: integrate midoriMihai Prica2013-08-301-0/+1
| | | | | | | | | | | | Integrate the Midori web browser in Build Appliance. This will allow the users to get help and file a bug from Hob in Build Appliance. [YOCTO #3506] (From OE-Core rev: 18109cf0c71cbd3b77bcf133996774abe4bbccae) Signed-off-by: Mihai Prica <mihai.prica@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lib/oeqa: move skeletoninit.py where it belongsStefan Stanacar2013-08-301-0/+0
| | | | | | | | | | | | | OE-core commit fcc59cbcdb1550489d372edf9f465efa7165245f / poky commit 748ddc39e56623f4e48987f0467f4722f6e162f2 added a new test, but in the wrong location. I took the patch from Alex's branch but renamed it from meta/lib/oeqa/runtime/skeleton.py to meta/lib/oeqa/skeletoninit.py before sending. This was unintentional, it should have been under meta/lib/oeqa/runtime. (From OE-Core rev: f12c346ef48cb44be2e356e4cf4f28d015c3f507) Signed-off-by: Stefan Stanacar <stefanx.stanacar@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libnfsidmap: Add and modify idmapd.confZhang Xiao2013-08-302-0/+25
| | | | | | | | | | | | add configuration file to make rpc.idmapd to not report below error: rpc.idmapd: Skipping configuration file "/etc/idmapd.conf": No such file or directory rpc.idmapd: Could not find group "nobody" (From OE-Core rev: 6ecd6fb730f473fb90cefd7d0b431d5b8d2c05f7) Signed-off-by: Zhang Xiao <xiao.zhang@windriver.com> Signed-off-by: Roy.Li <rongqing.li@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* busybox: set default log buffer size to 64 at compile timePaul Eggleton2013-08-301-1/+1
| | | | | | | | | | | | | | This provides a more reasonable log buffer size to avoid losing earlier events, and 64K is not a problem for modern systems. When the buffer is used on sysvinit-based systems, which it isn't by default, 64K is already the runtime default size unless /etc/syslog-startup.conf is modified or deleted, so this only really affects systems using systemd. This completely removes the need for the busybox bbappend in meta-oe. (From OE-Core rev: 6d6a3f805b0fad6f904afb52dc12bfb543e3eec5) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildtools-tarball: Add python-pkgutil1.5_M4.rc2Richard Purdie2013-08-291-0/+1
| | | | | | | | | This is needed by some recently added automated QA tests so we should add it to the buildtools tarball. (From OE-Core rev: 7d93288117e7054472d8a01dde0b38bc0ff98c27) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-11-17 02:53:56 +0000