rking on changing this in the last cycle but AFAICT not all issues
were able to be resolved in time. Kai, do you have a status update?
Thanks
Paul
--
Paul Eggleton
Intel System Software Products
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
:30 +1300)
are available in the Git repository at:
git://git.yoctoproject.org/layerindex-web paule/fixes14
http://git.yoctoproject.org/cgit.cgi/layerindex-web/log/?h=paule/fixes14
Paul Eggleton (6):
Drop LICENSE.diff2html
update: fix exception with -x/--nofetch option
recipes: improved
/?h=paule/recipesymbol
Paul Eggleton (29):
RRS: collect history independent of current recipes
RRS: Add deleted recipe handling
RRS: use more robust RFC2822 date conversion
RRS: skip problematic OE-Core commits (when a dependency)
RRS: handle downgrades
RRS: use more robust method
I submit one?
Quentin sent one yesterday (with the same subject). If you could give it a try
and confirm it fixes the failure that would be great.
Thanks
Paul
--
Paul Eggleton
Intel System Software Products
--
___
yocto mailing list
yocto@yoctoproje
{{ detail.BUILD.AUTO_CONF | safe
> }}
> +{% endif %}
We cannot use the safe filter here - doing so could open up an XSS
vulnerability, since anyone can upload anything to the error-report application
and the content could include links or othe
est/ref-manual/ref-manual.html#migration
BTW if you (or anyone else) finds anything we missed documenting here then
please do let us know - things do slip by, especially upstream changes.
Cheers,
Paul
--
Paul Eggleton
Intel System Software Products
--
___
Hi Yann
On Wednesday, 23 October 2019 2:25:48 AM NZDT Yann CARDAILLAC wrote:
> On Mon, Oct 21, 2019 at 9:37 PM Paul Eggleton
> wrote:
> > On Tuesday, 22 October 2019 4:15:03 AM NZDT Yann CARDAILLAC wrote:
> > > https://bugzilla.yoctoproject.org/show_bug.cgi?id=13527
>
Update pytz and beautifulsoup4.
Signed-off-by: Paul Eggleton
---
requirements.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/requirements.txt b/requirements.txt
index 84f2ea54..07d8495e 100644
--- a/requirements.txt
+++ b/requirements.txt
@@ -1,5 +1,5 @@
amqp
Update Pillow version to incorporate a fix for a denial-of-service
vulnerability (which should not affect this application however, as it
does not use Pillow to process external images):
https://nvd.nist.gov/vuln/detail/CVE-2019-16865
Signed-off-by: Paul Eggleton
---
requirements.txt | 2
/layerindex-web paule/requirements1
http://git.yoctoproject.org/cgit.cgi/layerindex-web/log/?h=paule/requirements1
Paul Eggleton (2):
requirements.txt: update to fix CVE-2019-16865
requirements.txt: bump a couple more versions
requirements.txt | 6 +++---
1 file changed, 3 insertions(+), 3
at some of the templates used for authentication originally came from
here:
https://github.com/macdhuibh/django-registration-templates
The LICENSE file indicates MIT for those though.
The txt files are tricky because any stray newlines will affect formatting. I
would probably avoid touching the
Typo, there has to be a ? in front of the id or otherwise we don't get
linked to the right commit. This would have affected recently added layers
with a cgit web frontend.
Signed-off-by: Paul Eggleton
---
templates/layerindex/editlayer.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion
ut is also useful in its own right.
Note: for readability, SRCREVs are only shown when PV has not changed.
Signed-off-by: Paul Eggleton
---
layerindex/forms.py | 19 ++
layerindex/urls.py | 12 +-
layerindex/views.py
For the purposes of the branch comparison function I'm about to add it
would be useful to track the value of SRCREV, so we can see if it has
changed even if PV hasn't.
Signed-off-by: Paul Eggleton
---
layerindex/migrations/0043_recipe_srcrev.py | 20
layerindex/models.py
(2019-10-14 09:20:33 +1300)
are available in the Git repository at:
git://git.yoctoproject.org/layerindex-web paule/branch_comparison
http://git.yoctoproject.org/cgit.cgi/layerindex-web/log/?h=paule/branch_comparison
Paul Eggleton (3):
Track SRCREV for each recipe
Add branch comparison
r day)
you're picking bitbake out of a repo where zeus is a valid branch.
FYI on layers.openembedded.org you also need to select the Python environment
for the branch - python3 in this case.
I've made both of these changes so it should index correctly the next time
around.
Cheers
Paul
--
ng
new settings in case the user doesn't add the default to their edited settings
file).
Cheers
Paul
--
Paul Eggleton
Intel System Software Products
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
at part. You can
set it on the command line but there almost certainly will be other issues, so
let's fix those first and then you might not have to deal with this part.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
On Thursday, 3 October 2019 11:44:53 AM NZDT akuster808 wrote:
> On 10/2/19 3:20 PM, Paul Eggleton wrote:
> > So it's that time again - we need to start building up the raw material for
> > the release notes and migration guide for the upcoming 3.0 release, and I'd
> > like
add things to the migration guide page, but bear
in mind I don't always have all of the context for every change.
Thanks!
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctop
://git.yoctoproject.org/layerindex-web paule/dissector-backports3
http://git.yoctoproject.org/cgit.cgi/layerindex-web/log/?h=paule/dissector-backports3
Paul Eggleton (3):
README: add basic documentation on db backup and restore
requirements.txt: update
Add a space between text and glyphicons
nt in the
bitbake recipe. These will be automatically available through the REST
API but won't (yet) be visible in the UI.
-- snip --
(Removing snip lines obviously)
Thanks,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
--
__
ate python2 recipes.
> >
> > A question to community,
> > - Would you recommend maintaining this layer separately in the current
> > github.com/Xilinx location or be included under meta- openembedded layers.
> > - Would you suggest having a separate mailing list ?
&
dependencies (2019-09-17 15:35:44 +1200)
are available in the Git repository at:
git://git.yoctoproject.org/layerindex-web paule/dissector-backports2
http://git.yoctoproject.org/cgit.cgi/layerindex-web/log/?h=paule/dissector-backports2
Paul Eggleton (15):
dockersetup.py: add connectivity check
that migration to the database in the normal way:
./manage.py migrate layerindex
Of course if your database already has those new fields the latter will fail,
in this instance you could simply add --fake since the result would have been
the same.
Cheers,
Paul
--
Paul Eggleton
Intel
ded the mentioned string to PR in
> bbclasses' in poky. Honestly, I do not believe this is the best idea
> (on other hands it is working xD ) ...
I would say PR_append = "${DISTRO_VERSION}" in your custom distro config work
- did you try that?
Cheers,
Paul
--
Pau
Fixes "Importing None" message since we had not yet initialised the
layerbranch variable.
Signed-off-by: Paul Eggleton
---
layerindex/tools/import_layers.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/layerindex/tools/import_layers.py
b/layerindex/tools/import
The new viewset has a different URL and uses pagination, so we need to
take that into account.
Signed-off-by: Paul Eggleton
---
layerindex/tools/import_layers.py | 92 ++-
1 file changed, 55 insertions(+), 37 deletions(-)
diff --git a/layerindex/tools
hild
items to that and add pagination to avoid result size issues.
Signed-off-by: Paul Eggleton
---
layerindex/restviews.py | 25 ++---
layerindex/urls.py | 1 +
2 files changed, 23 insertions(+), 3 deletions(-)
diff --git a/layerindex/restviews.py b/layerindex/restview
)
are available in the Git repository at:
git://git.yoctoproject.org/layerindex-web paule/restapi-fixes
http://git.yoctoproject.org/cgit.cgi/layerindex-web/log/?h=paule/restapi-fixes
Paul Eggleton (3):
API: fix recipes API performance regression
import_layers: use recipesExtended viewset
import_layers
in the Git repository at:
git://git.yoctoproject.org/layerindex-web paule/dissector-backports2
http://git.yoctoproject.org/cgit.cgi/layerindex-web/log/?h=paule/dissector-backports2
Paul Eggleton (4):
dockersetup.py: add connectivity check
docker: fix comment at top of Dockerfile
9ce9f7d2d1870a90b95809f43bae5d4e9f1ebd93:
dockersetup: fix regression with https enabled (2019-07-31 09:03:46 +1200)
are available in the Git repository at:
git://git.yoctoproject.org/layerindex-web paule/importlayers
http://git.yoctoproject.org/cgit.cgi/layerindex-web/log/?h=paule/importlayers
Paul Eggleton (15):
API
-web/log/?h=paule/dissector-backports
Amber Elliot (6):
docker: add setup script
admin.py: Add custom SiteAdmin model.
Upgrade django-registration to version 3.0.
Add user security questions
layerindex/urls.py: improve formatting
requirements.txt: Require secure version of Django.
Paul
formatting
requirements.txt: Require secure version of Django.
Paul Eggleton (119):
Add ability to hide branches
Split out recipe dependency handling to its own function
docker: Add docker-compose file
update_classic_status: recognise pythonhosted.org as python
update_classic_status: set
-14 10:05:53
+1300)
are available in the Git repository at:
git://git.yoctoproject.org/layerindex-web paule/fixes13
http://git.yoctoproject.org/cgit.cgi/layerindex-web/log/?h=paule/fixes13
Paul Eggleton (7):
Split out patch status read to a method on the Patch model
Record patch
d the basics of why a change has been made, then it's likely that
the commit message wasn't good enough. Unlike other issues, once a commit goes
in the message is set in stone within the git history, so if you are working
on a change, *please* take a minute or two to document it adequately in the
commit message so that others looking back can understand it.
Thanks,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
ine (well, the packagegroup packages
that it produces) was intended to be, although I guess there might be some
argument about what should and should not be in there.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
--
___
yocto mailing l
to
test one or more components that you're developing with the SDK.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
ex updating and it appears that's not working
at the moment. I have asked Michael to look into it. Thanks for the report,
I'll reply back here when things are sorted out.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
--
___
yocto ma
> Sorry for the late response. I'm no longer involved with the Yocto
> > Project. Last word I heard was that point of contact for Patchwork-
> > related work was Paul Eggleton.
> >
> > Hope this helps.
> >
> > Jose
> Thanks.
> >
> > On Mon,
On Thursday, 7 February 2019 11:24:24 AM NZDT akuster wrote:
>
> Hello Paul.
>
> On 2/6/19 2:00 PM, Paul Eggleton wrote:
> > The following changes since commit
61e9b048591adab88d1996646286e1d7df024bea:
> >
> > Fix drop-down alignment on duplicates p
/layerindex-web/log/?h=paule/fixes12
Paul Eggleton (10):
Send people an email when another user adds them as a maintainer
Add links to other branch recipes in recipe detail
Fix errors due to races deleting bitbake temp files
local.conf: allow for upstream_tracking.inc to be missing
Use try
Hongxu Jia
> > > gnupg 2.2.11 2.2.12Hongxu Jia
> > > help2man-native 1.47.6 1.47.8Hongxu Jia
> > > libxcrypt 4.1.14.4.1 Khem Raj
> &g
paule/fixes11
http://git.yoctoproject.org/cgit.cgi//log/?h=paule/fixes11
Paul Eggleton (30):
Track and enable reporting on duplicate inc files
Replace nvd3 with Chart.js
update: handle if there is no origin/master branch in bitbake repo
settings: add settings for CAPTCHA accessibility
l
I have just taken care of meta-qt3 and meta-qt4, FWIW.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
On Friday, 9 November 2018 11:41:42 AM NZDT Paul Eggleton wrote:
> You could accomplish the latter using PACKAGECONFIG_pn-python3 = "pgo" at
> the configuration level
Oops, I meant PACKAGECONFIG_remove_pn-python3 = "pgo" here.
Cheers,
Paul
--
Paul Eggleton
Intel Ope
On Monday, 5 November 2018 4:32:26 PM NZDT Paul Eggleton wrote:
> On Wednesday, 31 October 2018 11:06:31 AM NZDT Scott Rifenbark wrote:
> > I have an initial section at
> > https://yoctoproject.org/docs/2.6/ref-manual/ref-manual.html#moving-to-the-yocto-project-2.6-release,
>
https://wiki.yoctoproject.org/wiki/FutureMigrationGuide
BTW I think the section on postinstalls (from Richard's input) is a little terse
and needs expansion - most importantly it needs to describe what actions the
user might need to take. I'll take care of this on review if nobody else does.
Cheers,
Paul
You can ignore the warning (it's just a warning)
2) Remove the .bb entry from BBFILES in meta-saxo/conf/layer.conf (you can add
it back if and when you need it - of course that does mean you could forget to
do that and then wonder why adding a .bb file doesn't work)
3) Set BBFILE_PATTERN_I
through the commits in the release for the
more general changelog, so most things will get picked up that way, but it's
really helpful if people with first-hand knowledge of the implications of some
of these changes are involved in how they get documented.
Thanks,
Paul
--
Paul Eggleton
Intel Open
ttp://layers.openembedded.org/layerindex/branch/master/machines/?
q=mpc8315e=1
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
> > waiting for a new eSDK is not practical given that the developers may have
> > to iterate on the changes to the library quite a bit before they get it
> > just right for their new something.
> >
> > Is there a way to update the eSDK sysroots with recipes that are in the
> > wo
to be fixed anyway.)
Signed-off-by: Paul Eggleton
---
layerindex/views.py | 1 +
1 file changed, 1 insertion(+)
diff --git a/layerindex/views.py b/layerindex/views.py
index 4eed0cef..5ac7ffab 100644
--- a/layerindex/views.py
+++ b/layerindex/views.py
@@ -869,6 +869,7 @@ class RecipeDetailView
parently fixed itself. If the issue returns or anyone else sees anything
strange like this happening then please let me know.
Cheers
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
)
are available in the Git repository at:
git://git.yoctoproject.org/layerindex-web paule/fixes10
http://git.yoctoproject.org/cgit.cgi/layerindex-web/log/?h=paule/fixes10
Paul Eggleton (12):
update: fix error on LAYERRECOMMENDS failure
admin: allow changing branch on layerbranch records
Hi Randy
On Friday, 28 September 2018 11:22:29 AM NZST Randy MacLeod wrote:
> On 09/27/2018 05:28 PM, Nicolas Dechesne wrote:
> > On Thu, Sep 27, 2018 at 10:43 PM Paul Eggleton
> > wrote:
> >> I'm very happy to announce that we've finally been able to upgrade the
>
will take a bit more time to properly enable so I'll send out a separate email
with further details when they are ready.
As always, please let me know if you have any comments or notice any issues.
(I've already seen a few minor problems in the update logs so I'll be looking
into those.)
Ch
and bitbake.sock. For now the simplest way to deal with
this is to ignore the errors since we don't care about these files,
we just want the temp dir gone.
Signed-off-by: Paul Eggleton
---
layerindex/update_layer.py | 11 ++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/layerindex
completed item (2018-09-20 16:04:49 +1200)
are available in the Git repository at:
git://git.yoctoproject.org/layerindex-web paule/fixes9
http://git.yoctoproject.org/cgit.cgi/layerindex-web/log/?h=paule/fixes9
Paul Eggleton (5):
comparison: use style on hidden select instead of CSS class
lse that could not be built (and the reason for
that will be in the message above).
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
(as part of setup, just as you need to set up the board/device before
running any tests - you just need to ensure this gets documented somewhere).
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
as this is patching OE-Core, the patch needs to be sent to the
openembedded-c...@lists.openembedded.org mailing list, if you could
please use that for the next revision that would be great.
Thanks,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
--
for layer_type (2018-09-20 15:53:07 +1200)
are available in the Git repository at:
git://git.yoctoproject.org/layerindex-web paule/fixes8
http://git.yoctoproject.org/cgit.cgi//log/?h=paule/fixes8
Paul Eggleton (10):
import_otherdistro: fix update recording code
Upgrade to Bootstrap 3
/cgit.cgi/layerindex-web/log/?h=paule/fixes7
Paul Eggleton (15):
docker: remove one step from proxy setup
docker: correct comment in .gitconfig
update: do not try to parse a layer that failed to fetch
Disable git interactive password prompts
Limit selection of "Base" layer type
re
On Thursday, 30 August 2018 11:44:10 AM NZST Paul Eggleton wrote:
> On Wednesday, 29 August 2018 10:46:27 PM NZST Paul Eggleton wrote:
> > I know Konrad promised to update the docker-compose setup to be closer
> > to what we'd done recently with the docker setup, but I n
f this (and many other things) for you. I guess you based
your recipe on linux-dummy.bb, but that recipe is special and shouldn't be
used as a template for a real kernel.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
--
___
yocto-bs
> // Robert
>
> On 07/31/2018 03:57 PM, Robert Yang wrote:
> > Hi Paul,
> >
> > On 07/24/2018 04:33 PM, Paul Eggleton wrote:
> >> Hi Robert,
> >>
> >> On Monday, 23 July 2018 12:30:01 PM CEST Robert Yang wrote:
> >>> Now the lo
On Wednesday, 29 August 2018 10:46:27 PM NZST Paul Eggleton wrote:
> Hi folks
>
> I know Konrad promised to update the docker-compose setup to be closer
> to what we'd done recently with the docker setup, but I needed something
> urgently and wanted to learn how to use docker-com
/layerindex-web/log/?h=paule/docker-compose
Let me know what you think - it works well enough for me here, although the
setup commands are now a bit ugly on their own.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
--
___
yocto mailing
During debugging a parsing issue, we don't really want to continue if a
parsing error occurs, and in that situation I usually end up using
Ctrl+C to exit early. Add an option to exit immediately upon error to
avoid having to do that.
Signed-off-by: Paul Eggleton
---
layerindex/update.py
-14 15:09:36 +0200)
are available in the Git repository at:
git://git.yoctoproject.org/layerindex-web paule/fixes6
http://git.yoctoproject.org/cgit.cgi/layerindex-web/log/?h=paule/fixes6
Paul Eggleton (3):
rrs: fix recipe/maintainer count showing at top
Hide navbar on comparison select
We don't want to see the navbar on this page because otherwise it lets
you select branches and click on Stats etc. which doesn't make any sense
in this context.
Signed-off-by: Paul Eggleton
---
templates/base_toplevel.html | 2 ++
templates/layerindex
We were using the main badge class as a selector here to show the recipe
or maintainer count, and that meant that it also showed up at the top
next to the login button if there were some layers to review. Use a
proper id to stop that from happening.
Signed-off-by: Paul Eggleton
---
templates
in the template to avoid the functions being called more than necessary.
Signed-off-by: Paul Eggleton
---
layerindex/models.py | 8
layerindex/views.py | 2 +-
templates/layerindex/updatelist.html | 6 --
3 files changed, 13 insertions(+), 3 deletions(-)
diff
-by: Paul Eggleton
---
layerindex/update.py | 4
1 file changed, 4 insertions(+)
diff --git a/layerindex/update.py b/layerindex/update.py
index 14529498..aea7cd09 100755
--- a/layerindex/update.py
+++ b/layerindex/update.py
@@ -540,6 +540,10 @@ def main():
except KeyboardInterrupt
with a non-zero return code so that update.py knows it has failed
Signed-off-by: Paul Eggleton
---
layerindex/update_layer.py | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/layerindex/update_layer.py b/layerindex/update_layer.py
index 2b39e8ef..d9c93360 100644
--- a/layerindex
d17080d325b9b82e8b844c207053eb2b3ac111ad:
Show links to include files on recipe detail (2018-08-13 16:04:16 +0200)
are available in the Git repository at:
git://git.yoctoproject.org/layerindex-web paule/layerupdate
http://git.yoctoproject.org/cgit.cgi/layerindex-web/log/?h=paule/layerupdate
Paul Eggleton (5):
update: avoid
changes since commit fca74f3ac3c6536c50cb0a518fe78447a284dc55:
Update TODO list (2018-08-06 12:36:31 +0200)
are available in the Git repository at:
git://git.yoctoproject.org/layerindex-web paule/otherdistro
http://git.yoctoproject.org/cgit.cgi/layerindex-web/log/?h=paule/otherdistro
Paul
s from a recipe and then package its
output though, I think that should work.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
-web paule/otherdistro
http://git.yoctoproject.org/cgit.cgi//log/?h=paule/otherdistro
Paul Eggleton (31):
forms: clear out comparison recipe/layerbranch if status doesn't accept them
Add a script to import layers from an existing layer index
update_classic_status: fix matching on wrong l
at:
git://git.yoctoproject.org/layerindex-web paule/fixes5
http://git.yoctoproject.org/cgit.cgi/layerindex-web/log/?h=paule/fixes5
Paul Eggleton (9):
docker: drop names/emails from settings.py
docker: fix copying .gitconfig for proxy setup
README: tweak to make Docker setup more prominent
lly I'd like to see it stay and get fixed up, but the
issue is having the time to fix it and maintain it - if you do by any chance
then that would be great.
At the moment I believe "simpleremote" does still work, it's just the actual
classes that are broken, but I didn't give it
so that this will work
if that is extended in future? Of course that will mean initialising Django
earlier, I'm not sure if that will have any side-effects that we wouldn't want.
If you could give that a try though that would be great.
Thanks,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
t; in a
dvb-apps_%.bbappend for the recipe in your own layer, and then the
blacklisting will be disabled for that recipe.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
YI you can enable buildhistory and use the buildhistory-collect-srcrevs
script to generate all those SRCREV lines so you don't have to do that
by hand:
https://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#maintaining-build-output-quality
Cheers,
Paul
--
Paul Eggleton
Intel Open
fline?
> >>
> >> Thanks
> >> --
> >> ___
> >> yocto mailing list
> >> yocto@yoctoproject.org
> >> https://lists.yoctoproject.org/listinfo/yocto
>
>
--
Paul Eggleton
Intel Open Source Technology Centre
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
On Monday, 16 July 2018 10:16:55 PM CEST Paul Eggleton wrote:
> On Monday, 16 July 2018 8:24:53 PM CEST Konrad Scherer wrote:
> > I recently noticed that if gcc is removed in the 'apt-get purge' step,
> > the bitbake sanity checker will fail due to missing 'gcc' when doing a
&
cipe was moved and the move wasn't handled properly. I have a fix
and will be sending it shortly.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
On Monday, 16 July 2018 8:24:53 PM CEST Konrad Scherer wrote:
> On 07/13/2018 03:29 AM, Paul Eggleton wrote:
> > On Thursday, 12 July 2018 10:16:12 PM CEST you wrote:
> >> I just noticed that the image doesn't contain git. Was this
> >> deliberate or an oversight?
some documentation when I get
> back.
OK great, thanks.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
ust need to make sure everything we now have in the README is
covered by the compose file (everything that's practical to cover, anyway).
Cheers,
Pau;
--
Paul Eggleton
Intel Open Source Technology Centre
--
___
yocto mailing list
yocto@y
it. In particular I haven't yet explored docker-compose as you have,
although it looks like it would make deploying all of this a bit easier.
Let me know what you think.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
--
___
yocto
or his:
https://github.com/halstead/layerindex-web/commit/b9791710ff97550fa9110ab89a70c42b1fc86581
I think we probably want to break all of this down into a set of discrete
commits rather than one big one, and then it'll be a bit clearer. I'll do a
first pass and come back to you both.
Cheers,
Pa
orarily. Devtool (as recommend by
others on this thread) is designed to enable this workflow in a much safer
manner.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
On Monday, 9 July 2018 10:45:58 AM CEST Robert Yang wrote:
> On 07/09/2018 04:36 PM, Paul Eggleton wrote:
> > On Monday, 9 July 2018 10:34:07 AM CEST Paul Eggleton wrote:
> >> On Monday, 9 July 2018 6:11:30 AM CEST Robert Yang wrote:
> >>> Fixed:
> >>>
On Monday, 9 July 2018 10:34:07 AM CEST Paul Eggleton wrote:
> Hi Robert,
>
> On Monday, 9 July 2018 6:11:30 AM CEST Robert Yang wrote:
> > Fixed:
> > Assume there is no master branch in hello layer:
> > $ update.py -l hello -b master
> > INFO: Skipping upda
h fixed the problem, now it skips it since the
> branch doesn't exists when --nocheckout.
This fix doesn't seem right. The intention of --nocheckout is to not check
anything
out, i.e. use whatever HEAD is in the current repository. It wouldn't be correct
to get the commit from the origin in this
t would have started as a result of this patchset (or indeed recent
changes, other than perhaps an upgrade of django-reversion), have you been
using loaddata/dumpdata prior to this?
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
yer that recommends another which they don't submit (perhaps a
commercial layer?). The system shouldn't refuse to handle it or indicate that
it's broken (it isn't, there might be reduced functionality but the layer will
still
be parseable by bitbake).
I'll leave these changes unmerged for a bit in case yo
for formatting the text, URLs will be made into clickable links, and
four "levels" are supported (info, success, warning and error).
Signed-off-by: Paul Eggleton
---
layerindex/admin.py | 1 +
layerindex/context_processors.py | 7 +--
layerindex/
1 - 100 of 1520 matches
Mail list logo
