- Aug 09, 2015
-
-
Richard Purdie authored
"0x200" became "0200" during the upgrade to libpam 1.2.1 in: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=88dd997d9941b63ae9eead6690ecf2b785c0740c and this broke the IMAGE_FEATURES like debug-tweaks. I've converted all the values to octal here to match the original header file convention and make it clearer. [YOCTO #8033] (From OE-Core rev: 588e19058f631a1cc78002e1969a5459cd626afb) Signed-off-by:
Richard Purdie <richard.purdie@linuxfoundation.org>
-
Topi Kuutela authored
If security_flags.inc is 'required' to the image, -pie and -fpie options are added to CFLAGS. These are not compatible with -shared GCC option. The result is several errors of following form and missing Python3 modules in the image: *.o In function `_start': *.S undefined reference to `main' collect2: error: ld returned 1 exit status (From OE-Core rev: 94818c5240b793464700945d0cf057bffb9e1008) Signed-off-by:Topi Kuutela <topi.kuutela@intel.com> Signed-off-by:
-
Ed Bartosh authored
Major changes in 0.2.0: - implemented UUID support - fixed support of GPT partition tables - implemented running bitbake from wic - implemented image compressing - started testing with oe-selftest. implemented 17 test cases - used native tools (parted, mkfs, mtools, etc) - usability and documentation fixes - code clenup (From OE-Core rev: a0f8cb7e0ffa15e101d39463c77707c821250203) Signed-off-by:
Ed Bartosh <ed.bartosh@linux.intel.com> Signed-off-by:
-
Ed Bartosh authored
Fixed pylint warnings. Increased pylint score from 8.02 to 9.40. (From OE-Core rev: 26d8c70fb8a7cc8f6473ad1779b20b00616740c0) Signed-off-by:
-
Ed Bartosh authored
Removed unused global variable wks_vars and 2 unused functions get_wks_var and add_wks_var. (From OE-Core rev: 7d87c821da6a5020e8dde3f1907fb8d6a023b110) Signed-off-by:
-
Ed Bartosh authored
exec_native_cmd was modified to report recipe to build native programs. Pairs executable->recipe are hardcoded as it's not possible to obtain this information automatically. [YOCTO #7631] (From OE-Core rev: 1274379c91ee8e2fb9fbb34a6445cd5767eb4a35) Signed-off-by:
-
Ed Bartosh authored
Included full console output and example of the .wks file into the 'wic help overview' content. Used qemux86-64 machine instead of crownbay to make example working without cloning additional layers. [YOCTO #7940] (From OE-Core rev: 68d391eaf4fe9fc37e3278255d5da170f98b8763) Signed-off-by:
-
Ed Bartosh authored
Made command line specification less confusing. Reformatted usage output. [YOCTO #7938] (From OE-Core rev: c4a44ad4c5aa65657b69b811e793f98418159348) Signed-off-by:
-
Alexander Kanavin authored
COPYING checksum has changed because the previous upstream tarball (taken from Fedora) had GPLv3 in it, but author's tarball has GPLv2. Otherwise the tarballs are identical (From OE-Core rev: 430c7b42ecf93deb41a52b641d4e3a717f3e50ff) Signed-off-by:
Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by:
-
Ed Bartosh authored
create-pull-request -d path creates empty patches if directory is specified as a path, i.e. ./bitbake or ./bitbake/ or full path. It behaves expected way only if script is run with -d bitbake, i.e. relative dir name doesn't contain '\'. Fixed this unwanted behaviour by changing directory and running git format-patch in it with --relative, without specifying relative path as a parameter. (From OE-Core rev: 3042956a86167f89beccc5d05f1fad1844e7c36a) Signed-off-by:
-
Fan Xin authored
wpa-supplicant: backport patch to fix CVE-2015-4141, CVE-2015-4143, CVE-2015-4144, CVE-2015-4145, CVE-2015-4146 Backport patch to fix CVE-2015-4141, CVE-2015-4143, CVE-2015-4144, CVE-2015-4145, CVE-2015-4146. This patch is originally from: For CVE-2015-4141: http://w1.fi/security/2015-2/0001-WPS-Fix-HTTP-chunked-transfer-encoding-parser.patch For CVE-2015-4143: http://w1.fi/security/2015-4/0001-EAP-pwd-peer-Fix-payload-length-validation-for-Commi.patch http://w1.fi/security/2015-4/0002-EAP-pwd-server-Fix-payload-length-validation-for-Com.patch For CVE-2015-4144 and CVE-2015-4145: http://w1.fi/security/2015-4/0003-EAP-pwd-peer-Fix-Total-Length-parsing-for-fragment-r.patch http://w1.fi/security/2015-4/0004-EAP-pwd-server-Fix-Total-Length-parsing-for-fragment.patch For CVE-2015-4146: http://w1.fi/security/2015-4/0005-EAP-pwd-peer-Fix-asymmetric-fragmentation-behavior.patch (From OE-Core rev: ce16e95de05db24e4e4132660d793cc7b1d890b9) Signed-off-by: Fan Xin <fan.xin at jp.fujitsu.com> Signed-off-by:
-
Paul Gortmaker authored
In commit a117fd5e, from OE-Core rev: 88d60e70da0890184922056cef1f20171f716ace "libdrm: Upgrade to 2.4.62" we managed to break X like this: [3602662.736] (--) intel(0): Integrated Graphics Chipset: Intel(R) HD Graphics 4600 [3602662.736] (--) intel(0): CPU: x86-64, sse2, sse3, ssse3, sse4.1, sse4.2, avx, avx2 [3602662.736] (II) intel(0): Creating default Display subsection in Screen section "Default Screen Section" for depth/fbbpp 24/32 [3602662.736] (==) intel(0): Depth 24, (--) framebuffer bpp 32 [3602662.736] (==) intel(0): RGB weight 888 [3602662.736] (==) intel(0): Default visual is TrueColor [3602662.736] (EE) [3602662.736] (EE) Backtrace: [3602662.736] (EE) 0: /usr/bin/X (xorg_backtrace+0x49) [0x56ae09] [3602662.736] (EE) 1: /usr/bin/X (0x400000+0x16ecd9) [0x56ecd9] [3602662.736] (EE) 2: /lib64/libpthread.so.0 (0x3330600000+0x105e0) [0x33306105e0] [3602662.736] (EE) [3602662.736] (EE) Segmentation fault at address 0x0 [3602662.736] (EE) Fatal server error: [3602662.736] (EE) Caught signal 11 (Segmentation fault). Server aborting A mix of a ~1 month old (working) image and the failing image led me to determine /usr/lib64/xorg/modules/drivers/intel_drv.so was bad. However nothing changed the parent package xf86-video-intel in yocto for months. So brute force bisecting yocto leads to the above commit. Inserting libdrm as git and then bisecting the 2.4.59 --> 2.4.62 uprev content leads to libdrm commit 8576527cfacaf42af8316e1030c192193e94225a ("intel: Merge latest i915_drm.h") -- specifically, the part of that commit that adds __u64 flags to drm_i915_gem_mmap lands in our sysroot and is used by the compile of xf86-video-intel. With the specific trigger finally pinpointed, the final leap was to correlate that trigger to the upstream xf86-video-intel commit that accounts for the fallout of this libdrm header change, that we did not yet have here. Fun times. Hopefully this complete description here will ensure nobody else has to retrace these steps again. Cc: Damien Lespiau <damien.lespiau@intel.com> Cc: Neil Roberts <neil@linux.intel.com> Cc: Chris Wilson <chris@chris-wilson.co.uk> Cc: Steffen Pankratz <steffen.pankratz@elektrobit.com> Cc: Ross Burton <ross.burton@intel.com> Cc: Richard Purdie <richard.purdie@linuxfoundation.org> (From OE-Core rev: c1df1da2a71aeb5956952e44c5f4ad669b6e770f) Signed-off-by:
Paul Gortmaker <paul.gortmaker@windriver.com> Signed-off-by:
-
Richard Purdie authored
If runqemu fails, ensure the log output is shown as its invaluable to aid debugging. Its slightly convoluted since we need to ensure we don't block on reading the pipe which may still be executing hence the need for nonblocking IO. (From OE-Core rev: 0e0fa1461863ec586b4f028dfd7d641f091ea928) Signed-off-by: -
Richard Purdie authored
ip list can return devices in the form tapX@NONE. If it does so, ensure we handle that case correctly. Newer distros appear to do this in some cases. [YOCTO #8129] (From OE-Core rev: 6459dde380febce24d2c355d441d9cb3b14409b9) Signed-off-by: -
Richard Purdie authored
In theory the code reduces the tap device number to an integer. This patch adds error checking to ensure that does happen and that the script exits if something unexpected happens. (From OE-Core rev: 4238f3b6e320969aaf539e6afb1cb2bfd61bb28b) Signed-off-by: -
Richard Purdie authored
The current approach used by the Makefile ends up installing weston.desktop twice and can give build failures when using parallel make flags. Change to just have one DATA reference. (From OE-Core rev: 5191ab6962712908e1aa1dca0d4253fb278366c2) Signed-off-by: -
Patrick Ohly authored
When reconfiguring the branch to something not already fetched, action_pull fails with error: pathspec '<new branch name>' did not match any file(s) known to git. It is the "git checkout" which fails like that. To solve this, try the faster "git checkout + git pull" first and only if that fails, fall back to the slow "git fetch + git checkout". In the conf.hard_reset case, do the checkout always after the git fetch. (From OE-Core rev: ad4d3b1da190cf08c6ac5f9a94a2a1c4980a184d) Signed-off-by:
Patrick Ohly <patrick.ohly@intel.com> Signed-off-by:
-
Patrick Ohly authored
The git operations can fail, for example when the branch is unknown or misconfigured. Better move the info message and extend it such that it is printed first and provides the necessary context, because otherwise the CalledProcessError exception gets dumped without mentioning for which component it occurred. (From OE-Core rev: 00d01468a692faf4272894dd328e8c532bcf8b49) Signed-off-by:
-
Alejandro Hernandez authored
Fixes OS hanging infinitely waiting for qemus process to release bitbake.lock (From OE-Core rev: d168bf34c553dbe5de7511e158cd83869d7a88bc) Signed-off-by:
Alejandro Hernandez <alejandro.hernandez@linux.intel.com> Signed-off-by:
-
- Aug 06, 2015
-
-
Michael Wood authored
The new project page is no longer responsible for triggering the build so add a handler for this in layerBtn which is used in the layerdetails and layers pages. This also removes the conflicting and redundant handler for this in the layerdetails. (Bitbake rev: b4c389443bdd121121fd1d1a9006a9f1f63f186f) Signed-off-by:
Michael Wood <michael.g.wood@intel.com> Signed-off-by:
-
Michael Wood authored
Should be & rather than "and" which was returning the truth'd value of the and condition. [YOCTO #8114] (Bitbake rev: 58035667e433f2b77f5cd48240dd051c35476284) Signed-off-by:
-
Michael Wood authored
We were attaching this handler before the elements were fully ready in the dom. Which allowed these links although disabled to take users to the change machine page. (Bitbake rev: 8245a7d679914ca7d4548ab7e83b5047ff8a1ff5) Signed-off-by:
-
Michael Wood authored
Update the url for changing the machine in the project page. [YOCTO #8113] (Bitbake rev: 6e46ad4aa404d80fded27db1fb072d35250cfcfb) Signed-off-by:
-
Michael Wood authored
When using sqlite we sometimes see Database Locked exceptions when we fire off database calls asynchronously from the UI. We need sqlite to wait a bit longer for the lock to be released. n.b In production setup we hopefully wouldn't be using sqlite. docs.djangoproject.com/en/1.6/ref/databases/#database-is-locked-errors (Bitbake rev: 7f3a4e0330f4de3ba8e092bc1c15a53d8c2be073) Signed-off-by:
-
Michael Wood authored
The layerdetails view definition was moved to tables though it isn't a table. We have a mechanism for the JSON response for this page so use this instead of a custom class. (Bitbake rev: b5100bfd4cb32a9b59b0554c6dbc3a4295da7d8e) Signed-off-by:
-
Michael Wood authored
A header id was mistakenly added to the table template which was not also added to the simple version of the toaster template. We don't need this id so remove it. (Bitbake rev: daf902e2a6f736b9c8ef6492143fdbf856451559) Signed-off-by:
-
Michael Wood authored
Add a highlighter for the results in the typeahead, this highlights the part of the results which is currently being matched. This is a modified version of the bootstrap stock function with added escaping and the addition of the details information. (Bitbake rev: 3a6bad55a84d8d374a23f488ce42fed9b927c4f2) Signed-off-by:
-
Michael Wood authored
When we have a slow request we don't want to see the typeahead results changing in the middle of typing the item. To do this we make sure that requests to the typeahead can only happen sequentially and that if results have been retrieved but the input is now empty we don't bother showing the results. (Bitbake rev: 0b508e8b4a9e25c223c6c11ecd6d0e1aab727e8c) Signed-off-by:
-
Michael Wood authored
Fix the currently broken unit test for typeaheads and add some additional fields to check for in layers, projects, recipes and machines typeaheads. (Bitbake rev: 5700cd269e3a4fd517e16a3a19e61a23091df465) Signed-off-by:
-
Michael Wood authored
We need to keep consistent the field names of these objects so that we can use the object response from different calls. e.g. layer dependences or listing layers in the project. (Bitbake rev: 5c7004908f6916c0d279299c47b9dca3237148ec) Signed-off-by:
-
Michael Wood authored
The one thing left being used in this definition was a response which contains the list of layers which would be deleted if you change the project release. This patch moves that to it's own url/endpoint and updates the frontend reference which is using it. (Bitbake rev: 1cc19c84ee97182f39eae0338c712f7a2b40a18d) Signed-off-by:
-
Michael Wood authored
At a minimum for this typeahead to work we need a url parameter to call for a JSON reponse of items to filter on. (Bitbake rev: 80b214d93c5df63a251b807ca93f81f00c6bfeb2) Signed-off-by:
-
Michael Wood authored
Switch the existing typeahead inputs to use the new typeahead widget. This means we have a defined mechanism and end point for typeaheads which meets the design specification. (Bitbake rev: 31a8ae7909347f7b6edde5bbdf02b86dc1b32ed0) Signed-off-by:
-
Michael Wood authored
Implementation of typeahead widgets for layers machines and recipes typeahead. [YOCTO #7152] (Bitbake rev: 913d01758564db2f5fae4451bf0fdca38a1b3d61) Signed-off-by:
-
Michael Wood authored
The typeahead behaviour is significantly different from searching in a table so we need a separate widget to do this. [YOCTO #7152] (Bitbake rev: 195c5407a9de29d97f2525b9ae6c827afb934e37) Signed-off-by:
-
Michael Wood authored
Use the new utils functions on the project object to get the common querysets that we also use in tables. (Bitbake rev: 5e013a9bc3deb03bd6bac357b9ecb81c3c77b255) Signed-off-by:
-
Michael Wood authored
We use these querysets when creating tables of results and also when we want to have a typeahead search. These can also form the basis of future API endpoints. (Bitbake rev: 2a10fecd985343802f0e99c6fff25c28980eee20) Signed-off-by:
-
Michael Wood authored
Save duplicating this call and make a utility function for it on the Layer_Version object. (Bitbake rev: 32d382315bad37cebbe67ca3287085f3d856a9ed) Signed-off-by:
-
Belen Barros Pena authored
It is not very good to just tell people: "this is empty because you haven't done anything". We should politely invite them to do something about it. Thus adding a "Choose a recipe to build" link to the all compatible recipes page whenever the 'most built recipes' section is empty. (Bitbake rev: 8d2ed32cd09cf6cb96521fd42789faae99656fad) Signed-off-by:
Belen Barros Pena <belen.barros.pena@intel.com> Signed-off-by:
-
Belen Barros Pena authored
Adjust the space between the first fieldset and the tabs, and the help text and the first form field. (Bitbake rev: 68086d260842c12e5459c719f383b045fb0b3c2d) Signed-off-by:
-
