[yocto] [PATCH 0/1] [error-report-web]
The following changes since commit 661cc25d79ce5a443b3ef842ea97b3e913cd2818: error-report-web: Sorting error tables (2014-09-08 17:02:24 +0300) are available in the git repository at: git://git.yoctoproject.org/poky-contrib roxana/YB6540 http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=roxana/YB6540 Roxana Ciobanu (1): error-report-web: Enhancements to the error pager Post/static/css/custom.css| 17 + templates/error-details.html | 22 -- templates/error-page.html | 2 +- templates/latest-errors.html | 25 - templates/search-details.html | 16 5 files changed, 62 insertions(+), 20 deletions(-) -- 1.9.1 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 1/1] error-report-web: Enhancements to the error pager
- add link to the Yocto Project web repositor
- add link to the Yocto Project Bugzilla instance
[YOCTO #6540]
Signed-off-by: Roxana Ciobanu
---
Post/static/css/custom.css| 17 +
templates/error-details.html | 22 --
templates/error-page.html | 2 +-
templates/latest-errors.html | 25 -
templates/search-details.html | 16
5 files changed, 62 insertions(+), 20 deletions(-)
diff --git a/Post/static/css/custom.css b/Post/static/css/custom.css
index f2a35a6..809f5a5 100644
--- a/Post/static/css/custom.css
+++ b/Post/static/css/custom.css
@@ -83,3 +83,20 @@ td a:visited {
th a, th span {
font-weight: normal;
}
+.dl-vertical dd {
+ margin-bottom: 10px;
+}
+.dd a {
+ display: block;
+ margin: 10px 0;
+}
+.popover-content p {
+ margin-top: 10px;
+}
+.popover-content p > a {
+ color: #0088CC;
+}
+.popover-content p > a:hover {
+ color: #005580;
+ text-decoration: underline;
+}
diff --git a/templates/error-details.html b/templates/error-details.html
index f2dc010..ffb5f7e 100644
--- a/templates/error-details.html
+++ b/templates/error-details.html
@@ -41,14 +41,24 @@
{{
detail.BUILD.BRANCH }}
Commit:
{{
detail.BUILD.COMMIT }}
+ {% if
"yocto-autobuilder" in detail.BUILD.NAME and "master" in detail.BUILD.BRANCH %}
+ http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id={{detail.BUILD.COMMIT}}";>View
commit
+ {% endif %}
Submitter:
- {{
detail.BUILD.NAME }}
+ {% if "@" in
detail.BUILD.EMAIL %}
+mailto:{{detail.BUILD.EMAIL}}";>{{detail.BUILD.EMAIL}}
+ {% else %}
+ {{
detail.BUILD.NAME }}
+ {% endif %}
+
- {% ifnotequal
detail.BUILD.EMAIL "" %}
- {% if "@" in
detail.BUILD.EMAIL %}
- mailto:{{detail.BUILD.EMAIL}}";>Email submitter
- {% endif %}
- {% endifnotequal %}
+
+ https://bugzilla.yoctoproject.org/enter_bug.cgi"; >Open a bug
+
{% endfor %}
{% endif %}
diff --git a/templates/error-page.html b/templates/error-page.html
index d811c77..a090e15 100644
--- a/templates/error-page.html
+++ b/templates/error-page.html
@@ -13,7 +13,7 @@
Statistics
- {% ifequal query "autobuilder" %}
+ {% ifequal d "autobuilder" %}
No Autobuilder errors found
{% else %}
No errors found
diff --git a/templates/latest-errors.html b/templates/latest-errors.html
index d002a65..3bafce7 100644
--- a/templates/latest-errors.html
+++ b/templates/latest-errors.html
@@ -184,12 +184,12 @@
{% ifequal d 'autobuilder' %}
-Latest errors
-Latest Autobuilder errors
+Latest errors
+Latest Autobuilder errors
{% else %}
Latest errors
-Latest
Autobuilder errors
+Latest
Autobuilder errors
{% endifequal %}
Statistics
@@ -318,12 +318,18 @@
{{
detail.BUILD.BUILD_SYS }}
[yocto] Integration of custom recipe with SDK
Hi, I am using Poky-8.0.2 danny version for development. I want to integrate my custom recipe with sdk generated by meta-toolchain-qte so that I can use header files and libraries generated by my custom recipe for cross compilation. I am not sure of the proper way to do it. Right now generated header files and libraries could be found in rootfs generated for the target machine but for SDK there is no progress. Any help is appreciable.. Thanks Navani -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Customizing task basehash
I have defined a class with a customized fetch task (that
copies files from a local directory to the ${S} directory).
I am looking for a way to cause the fetch task to run
whenever the contents of the local directory change
w.r.t. what was last fetched/copied to ${S}.
Seems to me that I could do this by including the hash
of the source directory contents into the basehash of
the fetch task.
But I can't see how to do that. It is possible, or am I
thinking in the wrong direction? Is there a better way
to achieve what I need?
MV
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-selinux] refpolicy update in master-next
On 9/18/14, 2:57 PM, Joe MacDonald wrote: Hey all, As we'd all discussed at different times in the past, we're well behind the curve on a refpolicy update for meta-selinux. With the 1.7 release of Yocto coming up, we thought it was important to update the policy sooner rather than later, so I'm starting that work now. It's being done in master-next and currently the only recipe that has been updated is the -mls one. Over the next few days I'll be updating the others, then working through testing and trying to make sure they're all sane. It would help me out immensely if you had time to kick the tires as well on your favourite policy variant. Depending on how long this takes, the next step is updating the userspace. Fortunately this time around, though, the current userspace is still officially up to the task of managing the current policy, so a full update isn't strictly required. It'd be a really nice thing to have done, though. :-) I spoke with Joe about this work this morning, and I think master-next is the right place to do this. So if you have immediate bug fixes, we'll try to apply them to both master and master-next. And then continue to use master-next to stage the policy changes (or anything else that requires a bit more 'soak' time) before merging. I'd like to try to get 'master' of meta-selinux fully synced and working with the 'master' of Poky around the time of Poky's release (within a week or so of the release at least).. then we can branch and let the master continue to flow with any "new" work. (It's a plan, I'm not sure if it'll happen or not.) If anyone has any concerns let me know.. otherwise I think this is the plan! --Mark -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Integration of custom recipe with SDK
On 09/18/2014 05:12 AM, Navani Srivastava wrote: Hi, I am using Poky-8.0.2 danny version for development. I want to integrate my custom recipe with sdk generated by meta-toolchain-qte so that I can use header files and libraries generated by my custom recipe for cross compilation. I am not sure of the proper way to do it. Right now generated header files and libraries could be found in rootfs generated for the target machine but for SDK there is no progress. If you use one of the methods described at http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#ref-classes-nativesdk then you need to make sure to get the nativesdk version of your recipe into the sdk. You should be able to do that by adding the nativesdk version of your recipe to the TOOLCHAIN_HOST_TASK variable. You could do that in your local.conf, or if you wanted a sticky version, create a meta-toolchain-qte.bbappend in your layer with the change. If you are unfamiliar with bbappends, they are described here: http://www.yoctoproject.org/docs/1.6.1/dev-manual/dev-manual.html#using-bbappend-files Hopefully that helps. Any help is appreciable.. Thanks Navani -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Nothing PROVIDES nativesdk-krb5
Good day Yocto Community, I have an ERROR when building my nativesdk recipe: ERROR: Nothing PROVIDES 'nativesdk-krb5' (but virtual:nativesdk:poky/meta/recipes-support/curl/curl_7.32.0.bb DEPENDS or otherwise requires it). Haven't seen a DEPENDS for krb5 in curl and openssl recipe. Is there any update on curl recipe to fix this? Thanks, Joseph -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
