[yocto] [dora] Compiling Qt 5.7 without meta-qt5
I'm trying to create/integrate a recipe that builds Qt5.7 on a Architech Hachiko (ARM) board. This board is uniquely compatible with Poky DORA (for technical reasons, I don't have the choice). Using meta-qt5 is excluded. Actually? I succeeded to build qt5.7 with the Poky SDK and I would like to create a recipe that will call the "configure" and the "make / make install". The command line looks like: ./configure -v -prefix /usr/local/qt5 -extprefix /opt/qt5-hachiko -device linux-arm-hachiko-g++ -device-option CROSS_COMPILE=/opt/poky/hachiko64/1.5.4/sysroots/x86_64-pokysdk-linux/usr/bin/arm-poky-linux-gnueabi/arm-poky-linux-gnueabi- -sysroot /opt/poky/hachiko64/1.5.4/sysroots/cortexa9hf-vfp-neon-poky-linux-gnueabi -release -shared -no-opengl -no-gstreamer -no-sql-sqlite -no-sql-sqlite2 -qt-zlib -no-gif -no-accessibility -qt-libpng -qt-libjpeg -qt-xcb -device-option QMAKE_LFLAGS=-O1 -opensource -confirm-license -nomake examples -nomake tests -skip qt3d -skip qtwebengine -skip qtcanvas3d -no-icu -skip qtvirtualkeyboard But in a Yocto recipe, which variable should I use for the following options: CROSS_COMPILE=/opt/poky/hachiko64/1.5.4/sysroots/x86_64-pokysdk-linux/usr/bin/arm-poky-linux-gnueabi/arm-poky-linux-gnueabi- -sysroot /opt/poky/hachiko64/1.5.4/sysroots/cortexa9hf-vfp-neon-poky-linux-gnueabi Currently, the values points to the Poky SDK generated by Yocto. Thanks. Z. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [yocto-kernel-tools][PATCH 0/1] Rework merge of feature branches
On vendredi 3 février 2017 13:51:34 CET Bruce Ashfield wrote: > > I was able to merge branches with this patch applied to Morty. > > Cheers, > > Bruce > I've just successfully tested it on Morty myself. Works for me too, branches are merged just like they were before ! Thank you David -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [dora] Compiling Qt 5.7 without meta-qt5
On 7 February 2017 at 11:05, Karim ATIKI wrote: > Using meta-qt5 is excluded. > > But why not port meta-qt5 to dora? Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [dora] Compiling Qt 5.7 without meta-qt5
Hi Burt, I tried. But many errors raise that impact the "meta-hachiko" layer which is not compatible at all with versions > Dora. De : Burton, Ross Envoyé : mardi 7 février 2017 12:44 À : Karim ATIKI Cc : yocto Objet : Re: [yocto] [dora] Compiling Qt 5.7 without meta-qt5 On 7 February 2017 at 11:05, Karim ATIKI mailto:karim_at...@hotmail.com>> wrote: Using meta-qt5 is excluded. But why not port meta-qt5 to dora? Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [yocto-kernel-tools][PATCH 0/1] Rework merge of feature branches
On 2017-02-07 06:21 AM, David Vincent wrote: On vendredi 3 février 2017 13:51:34 CET Bruce Ashfield wrote: I was able to merge branches with this patch applied to Morty. Cheers, Bruce I've just successfully tested it on Morty myself. Works for me too, branches are merged just like they were before ! Good news! I'll send the patch to the morty maintainer so it can be merged. Cheers, Bruce Thank you David -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] is there a list somewhere of OE/YP-supported system perf/monitoring tools?
colleague asked me for a list of OE/YP recipes for monitoring system performance/resource utilization/profiling, i'm unaware of any single list that tracks that sort of thing so i'll just ask what people are aware of. just off the top of my head: * sysstat * atop * collectd * netdata * rrdtool * dstat i'm going to stop there since that's just a sample list. what other recipes should be added to that list that people find spectacularly useful? thanks. rday -- Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH] git-pw: include bundle sub-command
From: Leonardo Sandoval
This new command allows to fetch bundles (set of selected patches by the user)
and print them into the stdout. For the moment, bundles must be public
(otherwise
these wont be found)
Command line example:
openembedded-core$ git pw bundle newbundle --username lsandov1
Signed-off-by: Leonardo Sandoval
---
git-pw/git-pw | 52
1 file changed, 48 insertions(+), 4 deletions(-)
diff --git a/git-pw/git-pw b/git-pw/git-pw
index f5fbdcb..554dfae 100755
--- a/git-pw/git-pw
+++ b/git-pw/git-pw
@@ -126,6 +126,11 @@ class Command(object):
'need_project' : False,
'need_auth': False,
},
+'bundle': {
+'need_git_repo': True,
+'need_project' : False,
+'need_auth': False,
+},
'list': {
'need_git_repo': True,
'need_project' : True,
@@ -295,13 +300,25 @@ class Patch(RestObject):
def url(self, url='/'):
return '/patches/' + str(self.id) + url
+class Bundle(RestObject):
+
+def __init__(self, patchwork, bundle_name, user):
+super(Bundle, self).__init__(patchwork)
+self.bundle_name = str(bundle_name)
+self.user = str(user)
+
+def url(self, url='/'):
+return '/bundle/' + self.user + '/' + self.bundle_name + url
+
class Patchwork(object):
+api_version= 'api/1.0'
+
def __init__(self, web_root, project_linkname, user):
if not web_root.endswith('/'):
web_root += '/'
-self.api_base = web_root + 'api/1.0'
+self.api_base = web_root + self.api_version
self.web_root = web_root
self.project = Project(self, project_linkname)
self.user = user
@@ -372,6 +389,9 @@ class Patchwork(object):
def get_patch(self, patch_id):
return Patch(self, patch_id)
+def get_bundle(self, bundle_name, name):
+return Bundle(self, bundle_name, name)
+
class Terminal(object):
DEFAULT_WIDTH = 80
@@ -578,15 +598,13 @@ class GitPatchwork(object):
# auth mechanism. In any case, using HTTPS is a must.
username = None
password = None
-user = None
try:
username = config.get(section, 'user')
password = config.get(section, 'password')
-user = User(username, password)
except:
pass
-if not user and self.cmd.need_auth:
+if not password and self.cmd.need_auth:
die('No authentication configured.\n\n'
"Please set up credentials, e.g.:\n\n"
" git config patchwork.%(config)s.user myusername\n"
@@ -594,6 +612,8 @@ class GitPatchwork(object):
'config': self.cmd.config,
})
+user = User(username, password)
+
self.pw = Patchwork(web_root, project, user)
self.pw.setup()
@@ -679,6 +699,20 @@ class GitPatchwork(object):
raise
die('No patch with id %d.' % self.cmd.patch_id)
+def do_bundle(self):
+user = self.cmd.username or self.pw.user.username
+if not user:
+die('Either define a patchwork user at .git/config or set it
through --username')
+
+bundle = self.pw.get_bundle(self.cmd.bundle_name, user)
+
+try:
+return
self._print_mbox(bundle.absolute_url('/mbox/').replace(self.pw.api_version,''))
+except HttpError as e:
+if e.status_code != 404:
+raise
+die('No user %s bundle with name %s.' % (self.cmd.user,
self.cmd.bundle_name))
+
def do_list(self):
project = self.pw.get_project()
params = {
@@ -973,6 +1007,16 @@ if __name__ == '__main__':
parser_add_mbox_options(mbox_patch_parser)
+# bundle
+bundle_parser = subparsers.add_parser('bundle',
+help='retrieve a mbox file of a bundle and print it on stdout')
+bundle_parser.add_argument('--username', '-u', metavar='username',
+type=str, help='the patchwork\'s user that created the bundle, use
git\'s configured if omitted')
+bundle_parser.add_argument('bundle_name', metavar='bundle_name',
+type=str, help='the bundle to retrieve')
+
+parser_add_mbox_options(bundle_parser)
+
# poll-events
poll_events_parser = subparsers.add_parser('poll-events',
help='list events since the last invocation')
--
2.1.4
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [patchwork][PATCH] git-pw: include bundle sub-command
From: Leonardo Sandoval
This new command allows to fetch bundles (set of selected patches by the user)
and print them into the stdout. For the moment, bundles must be public
(otherwise
these wont be found)
Command line example:
openembedded-core$ git pw bundle newbundle --username lsandov1
Signed-off-by: Leonardo Sandoval
---
git-pw/git-pw | 52
1 file changed, 48 insertions(+), 4 deletions(-)
diff --git a/git-pw/git-pw b/git-pw/git-pw
index f5fbdcb..554dfae 100755
--- a/git-pw/git-pw
+++ b/git-pw/git-pw
@@ -126,6 +126,11 @@ class Command(object):
'need_project' : False,
'need_auth': False,
},
+'bundle': {
+'need_git_repo': True,
+'need_project' : False,
+'need_auth': False,
+},
'list': {
'need_git_repo': True,
'need_project' : True,
@@ -295,13 +300,25 @@ class Patch(RestObject):
def url(self, url='/'):
return '/patches/' + str(self.id) + url
+class Bundle(RestObject):
+
+def __init__(self, patchwork, bundle_name, user):
+super(Bundle, self).__init__(patchwork)
+self.bundle_name = str(bundle_name)
+self.user = str(user)
+
+def url(self, url='/'):
+return '/bundle/' + self.user + '/' + self.bundle_name + url
+
class Patchwork(object):
+api_version= 'api/1.0'
+
def __init__(self, web_root, project_linkname, user):
if not web_root.endswith('/'):
web_root += '/'
-self.api_base = web_root + 'api/1.0'
+self.api_base = web_root + self.api_version
self.web_root = web_root
self.project = Project(self, project_linkname)
self.user = user
@@ -372,6 +389,9 @@ class Patchwork(object):
def get_patch(self, patch_id):
return Patch(self, patch_id)
+def get_bundle(self, bundle_name, name):
+return Bundle(self, bundle_name, name)
+
class Terminal(object):
DEFAULT_WIDTH = 80
@@ -578,15 +598,13 @@ class GitPatchwork(object):
# auth mechanism. In any case, using HTTPS is a must.
username = None
password = None
-user = None
try:
username = config.get(section, 'user')
password = config.get(section, 'password')
-user = User(username, password)
except:
pass
-if not user and self.cmd.need_auth:
+if not password and self.cmd.need_auth:
die('No authentication configured.\n\n'
"Please set up credentials, e.g.:\n\n"
" git config patchwork.%(config)s.user myusername\n"
@@ -594,6 +612,8 @@ class GitPatchwork(object):
'config': self.cmd.config,
})
+user = User(username, password)
+
self.pw = Patchwork(web_root, project, user)
self.pw.setup()
@@ -679,6 +699,20 @@ class GitPatchwork(object):
raise
die('No patch with id %d.' % self.cmd.patch_id)
+def do_bundle(self):
+user = self.cmd.username or self.pw.user.username
+if not user:
+die('Either define a patchwork user at .git/config or set it
through --username')
+
+bundle = self.pw.get_bundle(self.cmd.bundle_name, user)
+
+try:
+return
self._print_mbox(bundle.absolute_url('/mbox/').replace(self.pw.api_version,''))
+except HttpError as e:
+if e.status_code != 404:
+raise
+die('No user %s bundle with name %s.' % (self.cmd.user,
self.cmd.bundle_name))
+
def do_list(self):
project = self.pw.get_project()
params = {
@@ -973,6 +1007,16 @@ if __name__ == '__main__':
parser_add_mbox_options(mbox_patch_parser)
+# bundle
+bundle_parser = subparsers.add_parser('bundle',
+help='retrieve a mbox file of a bundle and print it on stdout')
+bundle_parser.add_argument('--username', '-u', metavar='username',
+type=str, help='the patchwork\'s user that created the bundle, use
git\'s configured if omitted')
+bundle_parser.add_argument('bundle_name', metavar='bundle_name',
+type=str, help='the bundle to retrieve')
+
+parser_add_mbox_options(bundle_parser)
+
# poll-events
poll_events_parser = subparsers.add_parser('poll-events',
help='list events since the last invocation')
--
2.1.4
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Minutes: Yocto Project Technical Team Meeting - Tuesday, Feb 7, 2017 8:00 AM US Pacific Time
Attendees: Stephen, Armin, Stephano Sona, Ross, Joshua, Jussi, Saul, Sveinse, Richard, Agenda: * Opens collection - 5 min (Stephen) * Yocto Project status - 5 min (Stephen/team) YP 2.3 M2 rc3 is in QA. YP 2.3 M3 target cut off is Feb. 27th. YP 2.2.1 should go into QA after YP 2.3 M2 is out. https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.3_Status https://wiki.yoctoproject.org/wiki/Yocto_2.3_Schedule https://wiki.yoctoproject.org/wiki/Yocto_2.3_Features * Opens - 10 min * Team Sharing - 10 min Sona - CVE Check tool doesn't currently build on master. Jussi discussed that patches to fix it should be sent this week. We has some issues with the tool and discussed if we can get this into QA. We need an automated test script to add testing the tool to QA. Richard - How are recipe specific sysroots doing? No issues not filed in bugzilla yet. Thanks, Stephen K. Jolley Yocto Project Program Manager INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124 * Work Telephone:(503) 712-0534 *Cell: (208) 244-4460 * Email:stephen.k.jol...@intel.com -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Installing iperf3 causes strange image corruption
On 1 February 2017 at 20:28, Wilde, DonaldX wrote: > Unfortunately, what happens is that somewhere along the line after the > initial patch and compilation, something in our image gets radically > corrupted. With IMAGE_INCLUDE += “iperf3” set, the image is corrupted. > Horrible results occur including that much of our NVRAM content becomes > invisible and we get dumped into some kind of emergency debugging shell > after about 6.3 seconds. > ... > starting pid 1363, tty '': '/etc/init.d/rcS' > > can't run '/etc/init.d/rcS': No such file or directory > IMAGE_INCLUDE isn't a standard variable, so either you typo'd that or it's a variable that your images use. Either way, your error is basically "the rootfs is bust" so it's quite possible that by assigning to IMAGE_INCLUDE from your local.conf may be overriding the default value (set by ?=). For example, if you meant IMAGE_INSTALL then image.bbclass uses IMAGE_INSTALL ?= so by doing +=iperf3, you're building an image that *just* contains iperf3. Try using IMAGE_INSTALL_append = " iperf3". Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Installing iperf3 causes strange image corruption
On 7 February 2017 at 17:42, Wilde, DonaldX wrote: > My bad, Ross. I meant IMAGE_INSTALL. Must have been lexdysic the other > day. J > > In that case my guess was right: don't += it from your local.conf as you'll wipe the default value away. Use _append (and remember the leading whitespace as append doesn't add it for you). Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Minutes: Yocto Project Technical Team Meeting - Tuesday, Feb 7, 2017 8:00 AM US Pacific Time
Hi Jolley, Cve-check tool fails on master and latest morty, I have created following bug (Jussi is working on this): Bug 11026 - cve-check: Error in executing cve-check-update Some background info about this tool: = cve-check tool has been supported since the Morty release. This tool is not perfect (we get many false positives and false negatives) but it is better than nothing. This tool is using the nvd database which reads CVE data from Mitre. Sometimes Mitre doesn't have the correct/updated info about CVEs. EX: CVE-2016-2147 is listed : https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2147 ** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem. When the candidate has been publicized, the details for this candidate will be provided. So this CVE will not be in the nvd database and will not be detected by cve-check tool. There are other similar problems with nvd database but some of these can be fixed /improved eventually. My suggestion is to run this tool on master e.g. weekly when a release is approaching. It is easier to upgrade a package version to address CVEs on master rather than on maintenance/release branches. People caring about security could voluntarily check the result (cve.log) or we can have responsible maintainer, rotating on a weekly/bi-weekly basis. Related issues, hopefully someone will have time to work on these :) Bug 10771 - cve-check tool does not detect and report all relevant CVEs Bug 10772 - Automatic generation of CVE-reports Let me know if you have further question. Thanks for paying attention to this issue. //Sona From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On Behalf Of Jolley, Stephen K Sent: den 7 februari 2017 17:27 To: yocto@yoctoproject.org Subject: [yocto] Minutes: Yocto Project Technical Team Meeting - Tuesday, Feb 7, 2017 8:00 AM US Pacific Time Attendees: Stephen, Armin, Stephano Sona, Ross, Joshua, Jussi, Saul, Sveinse, Richard, Agenda: * Opens collection - 5 min (Stephen) * Yocto Project status - 5 min (Stephen/team) YP 2.3 M2 rc3 is in QA. YP 2.3 M3 target cut off is Feb. 27th. YP 2.2.1 should go into QA after YP 2.3 M2 is out. https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.3_Status https://wiki.yoctoproject.org/wiki/Yocto_2.3_Schedule https://wiki.yoctoproject.org/wiki/Yocto_2.3_Features * Opens - 10 min * Team Sharing - 10 min Sona - CVE Check tool doesn't currently build on master. Jussi discussed that patches to fix it should be sent this week. We has some issues with the tool and discussed if we can get this into QA. We need an automated test script to add testing the tool to QA. Richard - How are recipe specific sysroots doing? No issues not filed in bugzilla yet. Thanks, Stephen K. Jolley Yocto Project Program Manager INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124 I Work Telephone: (503) 712-0534 ( Cell: (208) 244-4460 ((Email: stephen.k.jol...@intel.com -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Removing/Disabling /etc/version
Hi, Easy question! I would like to disable the /etc/version file from being installed to the rootfs. How do I proceed? It looks hard-coded at first glance...? Regards, Marc -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Installing iperf3 causes strange image corruption
My bad, Ross. I meant IMAGE_INSTALL. Must have been lexdysic the other day. ☺ From: Burton, Ross [mailto:ross.bur...@intel.com] Sent: Tuesday, February 7, 2017 10:34 AM To: Wilde, DonaldX Cc: yocto@yoctoproject.org Subject: Re: [yocto] Installing iperf3 causes strange image corruption On 1 February 2017 at 20:28, Wilde, DonaldX mailto:donaldx.wi...@intel.com>> wrote: Unfortunately, what happens is that somewhere along the line after the initial patch and compilation, something in our image gets radically corrupted. With IMAGE_INCLUDE += “iperf3” set, the image is corrupted. Horrible results occur including that much of our NVRAM content becomes invisible and we get dumped into some kind of emergency debugging shell after about 6.3 seconds. ... starting pid 1363, tty '': '/etc/init.d/rcS' can't run '/etc/init.d/rcS': No such file or directory IMAGE_INCLUDE isn't a standard variable, so either you typo'd that or it's a variable that your images use. Either way, your error is basically "the rootfs is bust" so it's quite possible that by assigning to IMAGE_INCLUDE from your local.conf may be overriding the default value (set by ?=). For example, if you meant IMAGE_INSTALL then image.bbclass uses IMAGE_INSTALL ?= so by doing +=iperf3, you're building an image that *just* contains iperf3. Try using IMAGE_INSTALL_append = " iperf3". Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Installing iperf3 causes strange image corruption
As it happens, I learned to generate a statically linked binary that I could load into NVRAM on our board so I could move forward and accomplish my work, but I will take your advice and I believe you’ve told me enough that I can learn to do what you say to do for the future work that I do. Once it works I’ll spread the knowledge in CHD. From: Burton, Ross [mailto:ross.bur...@intel.com] Sent: Tuesday, February 7, 2017 10:44 AM To: Wilde, DonaldX Cc: yocto@yoctoproject.org Subject: Re: [yocto] Installing iperf3 causes strange image corruption On 7 February 2017 at 17:42, Wilde, DonaldX mailto:donaldx.wi...@intel.com>> wrote: My bad, Ross. I meant IMAGE_INSTALL. Must have been lexdysic the other day. ☺ In that case my guess was right: don't += it from your local.conf as you'll wipe the default value away. Use _append (and remember the leading whitespace as append doesn't add it for you). Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [patchwork][PATCH v2 1/2] series.js: Get patch id and pass it to POST request
Patch forms in series view do not pass selected patch id
as request element during a POST call, so no status/bundle
updates can be performed from such view.
This change includes the selected patch id as a request
element and pass it to POST call through a hidden input field.
[YOCTO #10973]
Signed-off-by: Jose Lamego
---
htdocs/js/series.js | 25 +++--
1 file changed, 23 insertions(+), 2 deletions(-)
diff --git a/htdocs/js/series.js b/htdocs/js/series.js
index 4f4f477..bd75790 100644
--- a/htdocs/js/series.js
+++ b/htdocs/js/series.js
@@ -1,5 +1,5 @@
$(document).ready(function(){
-$('[data-toggle="tooltip"]').tooltip();
+$('[data-toggle="tooltip"]').tooltip()
revTab=document.getElementById('revs-list')
coverView=document.getElementById('cover-letter-view'),
patchView=document.getElementById('patch-view'),
@@ -34,10 +34,31 @@ $(document).ready(function(){
})
$('.patch-link').on('click', function(){
+var pa=this.getAttribute("data-url")
+var curr_rev=document.getElementById('revs-list').value
+pa=pa.match(/\d+/)[0]
coverView.style.display='none'
patchView.style.display='block'
patchView.innerHTML=
'Loading patch...'
-$("#patch-view").load(this.getAttribute("data-url") + " #patch-body")
+$("#patch-view").load(
+this.getAttribute("data-url") + " #patch-body", function() {
+forms=document.forms
+for (i=0; ihttps://lists.yoctoproject.org/listinfo/yocto
[yocto] [patchwork][PATCH v2 2/2] series.py: Add POST call
Current series view is missing a POST call, avoiding users to update
or edit patch status or bundles.
This change adds POST call to series view, including the target
patch id, which is taken from request context.
[YOCTO #10973]
Signed-off-by: Jose Lamego
---
patchwork/views/series.py | 83 +--
1 file changed, 81 insertions(+), 2 deletions(-)
diff --git a/patchwork/views/series.py b/patchwork/views/series.py
index 1c14074..5fe8a74 100644
--- a/patchwork/views/series.py
+++ b/patchwork/views/series.py
@@ -18,9 +18,13 @@
# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
from django.conf import settings
-from django.shortcuts import render, get_object_or_404, get_list_or_404
+from django.shortcuts import render, render_to_response
+from django.shortcuts import get_object_or_404, get_list_or_404
from django.views.generic import View
-from patchwork.models import Project, Series, SeriesRevision, TestResult
+from patchwork.models import Patch, Project, Bundle,
+from patchwork.models import Series, SeriesRevision, TestResult
+from patchwork.requestcontext import PatchworkRequestContext
+from patchwork.forms import PatchForm, CreateBundleForm
class SeriesListView(View):
@@ -53,3 +57,78 @@ class SeriesView(View):
'cover_letter': revision.cover_letter,
'revisions': revisions,
})
+
+def post(self, request, *args, **kwargs):
+init_data = request.POST
+pa_id = init_data.get('patch', None)
+curr_rev = init_data.get('rev', None)
+patch = get_object_or_404(Patch, id=pa_id)
+series = get_object_or_404(Series, pk=kwargs['series'])
+context = PatchworkRequestContext(request)
+context.project = patch.project
+editable = patch.is_editable(request.user)
+
+revisions = get_list_or_404(SeriesRevision, series=series)
+for revision in revisions:
+revision.patch_list = revision.ordered_patches().\
+select_related('state', 'submitter')
+revision.test_results = TestResult.objects \
+.filter(revision=revision, patch=None) \
+.order_by('test__name').select_related('test')
+
+form = None
+createbundleform = None
+
+if editable:
+form = PatchForm(instance=patch)
+if request.user.is_authenticated():
+createbundleform = CreateBundleForm()
+
+if request.method == 'POST':
+action = request.POST.get('action', None)
+if action:
+action = action.lower()
+
+if action == 'createbundle':
+bundle = Bundle(owner=request.user, project=patch.project)
+createbundleform = CreateBundleForm(instance=bundle,
+data=request.POST)
+if createbundleform.is_valid():
+createbundleform.save()
+bundle.append_patch(patch)
+bundle.save()
+createbundleform = CreateBundleForm()
+context.add_message('Bundle %s created' % bundle.name)
+
+elif action == 'addtobundle':
+bundle = get_object_or_404(
+Bundle, id=request.POST.get('bundle_id'))
+try:
+bundle.append_patch(patch)
+bundle.save()
+context.add_message('Patch added to bundle "%s"' %
+bundle.name)
+except Exception as ex:
+context.add_message("Couldn't add patch '%s' to bundle %s:\
+ %s" % (patch.name, bundle.name, ex.message))
+
+# all other actions require edit privs
+elif not editable:
+return HttpResponseForbidden()
+
+elif action is None:
+form = PatchForm(data=request.POST, instance=patch)
+if form.is_valid():
+form.save()
+context.add_message('Patch ID: %s updated' % patch.pk)
+
+context['series'] = series
+context['patchform'] = form
+context['createbundleform'] = createbundleform
+context['project'] = patch.project
+context['revisions'] = revisions
+context['test_results'] = TestResult.objects \
+.filter(revision=None, patch=patch) \
+.order_by('test__name').select_related('test')
+
+return render_to_response('patchwork/series.html', context)
--
1.9.1
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [patchwork][PATCH v2 0/2] Series-view: Enable status/bundle edition
These changes enable patch status updating, adding a patch to an existing bundle and creating a new bundle from the series view. [YOCTO #10973] Changes in v2: Fixed javascript formatting and pep8 compliance. Jose Lamego (2): series.js: Get patch id and pass it to POST request series.py: Add POST call htdocs/js/series.js | 25 -- patchwork/views/series.py | 83 +-- 2 files changed, 104 insertions(+), 4 deletions(-) -- 1.9.1 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Removing/Disabling /etc/version
Hi Marc,
On Tuesday, 7 February 2017 2:20:09 PM NZDT Marc Ferland wrote:
> I would like to disable the /etc/version file from being installed to
> the rootfs. How do I proceed? It looks hard-coded at first glance...?
It is hardcoded, however it would be trivial to delete it in a shell function
added to ROOTFS_POSTPROCESS_COMMAND e.g. in the image recipe (or a class
inherited from the image recipe):
remove_etc_version () {
rm ${IMAGE_ROOTFS}${sysconfdir}/version
}
ROOTFS_POSTPROCESS_COMMAND += "remove_etc_version ; "
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] is there a list somewhere of OE/YP-supported system perf/monitoring tools?
On Tue, Feb 7, 2017 at 3:31 PM, Robert P. J. Day wrote: > > colleague asked me for a list of OE/YP recipes for monitoring system > performance/resource utilization/profiling, i'm unaware of any single > list that tracks that sort of thing so i'll just ask what people are > aware of. just off the top of my head: > > * sysstat > * atop > * collectd > * netdata > * rrdtool > * dstat * pcp http://pcp.io/ -- Maciej Borzecki RnDity -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
