Re: [yocto] [oe] Slideshow for FOSDEM
On Thu, Jan 4, 2018 at 1:22 PM, Andreas Müller wrote: > On Wed, Jan 3, 2018 at 6:29 PM, Philip Balister wrote: >> >> On 01/03/2018 09:47 AM, Paul Barker wrote: >> > Hi all, >> > >> > As we've only got one table at FOSDEM this year we're not going to >> > have space for as many bits of hardware as usual. I'd still like us to >> > show off the project and what people are building with OpenEmbedded & >> > Yocto Project though. Given the limited space I think the best way to >> > do this would be to put a slideshow on my laptop. >> > >> > I've made a start on this here: >> > >> > https://docs.google.com/presentation/d/1KYxhsxO-8GxhAreE0GKnTOCPdY6_4uXYIEp6Lc55MB8/edit?usp=sharing >> > >> > I've made this publicly editable so please feel free to add slides for >> > any OE features you want to show off and any projects (professional or >> > hobbyist) built with OE. If anyone can add a slide on project history >> > that would also be great. I'd also like a slide on the latest release >> > and the new features added. Photos of hardware projects using OE and >> > features like Toaster would be especially welcome! >> > >> > I'll give this a final edit before FOSDEM and the put it on rotation >> > on a laptop at the stand. Hopefully it will be useful for future >> > events as well. >> >> Can we build a small board with a largish screen so we can run the show >> on a device running an image built by OpenEmbedded? >> >> Philip >> > Hi, > > currently I am putting together something like a > 'diy-rpi-notebook-on-tripod' - WIP no photos yet. Would like to put a music > keyboard in front of it. Area required 1-2 square meters - no table > required. Is such thing accepted / of interest? > > Andreas Sadly I think we won't have space for this. We'll have one table and likely tables for other projects on both sides of us. You're welcome to bring the setup along anyway but I can't guarantee we'll be able to fit it in. Thanks, -- Paul Barker Togán Labs Ltd -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Upgrading Yocto Project Version - To Rocko
Hi there, I am new to the Yocto project and currently I have Yocto version 1.8 (Fido) installed on my Linux workstation. I was wondering, how can I upgrade to Yocto version 2.4 (Rocko)? Do I just remove the previous poky folder I downloaded and re-download a newer version of poky and checkout the branch and tags? Do share with me if any of you have the experience. THANK YOU! :) Vincent Kok Platform Application Engineer IOTG Customer Engineering Division (Transportation) Internet of Things Group (IOTG) [For makers] -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Upgrading Yocto Project Version - To Rocko
On 01/09/2018 01:55 PM, Kok, Vincent Chin Keong wrote: I was wondering, how can I upgrade to Yocto version 2.4 (Rocko)? Do I just remove the previous poky folder I downloaded and re-download a newer version of poky and checkout the branch and tags? The easiest is to perform a clean clone of the poky repo, and check out the tag you want. Alex -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Upgrading Yocto Project Version - To Rocko
How if I want to remain my database from previous version? How can I export them? Warmest regards, Vincent Kok Sent from my iPad On Jan 9, 2018, at 20:45, Alexander Kanavin mailto:alexander.kana...@linux.intel.com>> wrote: On 01/09/2018 01:55 PM, Kok, Vincent Chin Keong wrote: I was wondering, how can I upgrade to Yocto version 2.4 (Rocko)? Do I just remove the previous poky folder I downloaded and re-download a newer version of poky and checkout the branch and tags? The easiest is to perform a clean clone of the poky repo, and check out the tag you want. Alex -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Upgrading Yocto Project Version - To Rocko
Hi Vincent, When you are talking about database, are you talking about specific data from your generated project (such as the sstate cache) or are you talking about data in your current poky folder? If you are talking about project specific data I would recommend you create a new project and build from scratch when doing such a large upgrade (Fido --> Rocko), since a lot of stuffs have changed. For example bblayers.conf looks different (meta-yocto renamed to meta-poky) and so on. But if you have cusomizations done for fido you of course need ensure that these changes are manually exported to the new Rocko based project (for example point out custom layers in bblayers.conf and MACHINE in local.conf after creating your new project). If you are afraid of wiping git changes, and you already have an existing poky git clone you can just fetch the data (git fetch) then checkout the wanted branch, tag or revision. BR Petter 2018-01-09 14:35 skrev Kok, Vincent Chin Keong: > How if I want to remain my database from previous version? How can I export them? > > Warmest regards, > Vincent Kok > > Sent from my iPad > > On Jan 9, 2018, at 20:45, Alexander Kanavin wrote: > >> On 01/09/2018 01:55 PM, Kok, Vincent Chin Keong wrote: >> >>> I was wondering, how can I upgrade to Yocto version 2.4 (Rocko)? Do I just remove the previous poky folder I downloaded and re-download a newer version of poky and checkout the branch and tags? >> >> The easiest is to perform a clean clone of the poky repo, and check out the tag you want. >> >> Alex -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-swupd][PATCH 1/1] bundles.py: allow username/password encoded in URLs
On Thu, 2017-12-21 at 00:18 +0100, Ingo Flaschberger wrote: > Dear Patrick, > > this doesn't work: > 0162: """ > 0163: parsed_url = urllib.parse.urlsplit(url) > 0164: if parsed_url.username != None: > 0165: # Use the netloc with just the hostname, without > username/password. > *** 0166: parsed_url.netloc = parsed_url.hostname > 0167: # The username/password are installed permanently > in > the urllib.request module > 0168: # for future use with all URLs beneath url. > 0169: manager = > urllib.request.HTTPPasswordMgrWithDefaultRealm() > 0170: manager.add_password(None, parsed_url, > parsed_url.username, parsed_url.password) > Exception: AttributeError: can't set attribute Looks like netloc is a read-only attribute. That means one has to construct a new urllib.parse.SplitResult instead of updating the old one. > Using hostname as netloc will also remove an additional portnumber - > could this be a problem? Yes, that's also something that needs to be fixed. Can you update the patch as shown below, test it, and it if works send the final version to the list? Obviously I am not doing a good job with posting code that I can't test :-/ Am 20.12.2017 um 16:50 schrieb Patrick Ohly: > > Downloading content and version information via HTTP may need a > > username/password for basic authentication. To support this, > > SWUPD_VERSION_URL and SWUPD_CONTENT_URL can now contain URLs of the > > form http(s)://:@/. > > > > Original patch from: Ingo Flaschberger > > > > > > Signed-off-by: Patrick Ohly > > --- > > lib/swupd/bundles.py | 26 -- > > 1 file changed, 24 insertions(+), 2 deletions(-) > > > > diff --git a/lib/swupd/bundles.py b/lib/swupd/bundles.py > > index e1eec5a..48c7455 100644 > > --- a/lib/swupd/bundles.py > > +++ b/lib/swupd/bundles.py > > @@ -5,6 +5,7 @@ import subprocess > > import shutil > > import urllib.request > > import urllib.error > > +import urllib.parse > > from bb.utils import export_proxies > > from oe.package_manager import RpmPM > > from oe.package_manager import OpkgPM > > @@ -153,6 +154,27 @@ def copy_bundle_contents(d): > > for bndl in bundles: > > stage_empty_bundle(d, bndl) > > > > +def handle_plain_auth(url): > > +""" > > +Check for special urls with username/password (as in http://us > > er:password@host/), > > +extract those and install an auth handler which will provide > > them > > +to the HTTP server when needed. Returns the URL that is to be > > instead of the original one. > > +""" > > +parsed_url = urllib.parse.urlsplit(url) > > +if parsed_url.username != None: > > +# Use the netloc with just the hostname, without > > username/password. > > +parsed_url.netloc = parsed_url.hostname Instead: netloc = parsed_url.hostname if parsed_url.port is not None: netloc += ":%d" % parsed_url.port new_url = urllib.parse.SplitResult(parsed_url.scheme, netloc, parsed_url.path, parsed_url.query, parsed_url.fragment) > > +# The username/password are installed permanently in the > > urllib.request module > > +# for future use with all URLs beneath url. > > +manager = urllib.request.HTTPPasswordMgrWithDefaultRealm() > > +manager.add_password(None, parsed_url, > > parsed_url.username, parsed_url.password) > > +authHandler = urllib.request.HTTPBasicAuthHandler(manager) > > +opener = urllib.request.build_opener(authHandler) > > +urllib.request.install_opener(opener) > > +return urllib.parse.urlunsplit(new_source) Instead: return urllib.parse.urlunsplit(new_url) -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-swupd][PATCH 1/1] bundles.py: allow username/password encoded in URLs
Dear Patrick, it works if you replace: manager.add_password(None, parsed_url, parsed_url.username, parsed_url.password) with: manager.add_password(None, new_url, parsed_url.username, parsed_url.password) Kind regards, Ingo Flaschberger Am 09.01.2018 um 17:57 schrieb Patrick Ohly: On Thu, 2017-12-21 at 00:18 +0100, Ingo Flaschberger wrote: Dear Patrick, this doesn't work: 0162: """ 0163: parsed_url = urllib.parse.urlsplit(url) 0164: if parsed_url.username != None: 0165: # Use the netloc with just the hostname, without username/password. *** 0166: parsed_url.netloc = parsed_url.hostname 0167: # The username/password are installed permanently in the urllib.request module 0168: # for future use with all URLs beneath url. 0169: manager = urllib.request.HTTPPasswordMgrWithDefaultRealm() 0170: manager.add_password(None, parsed_url, parsed_url.username, parsed_url.password) Exception: AttributeError: can't set attribute Looks like netloc is a read-only attribute. That means one has to construct a new urllib.parse.SplitResult instead of updating the old one. Using hostname as netloc will also remove an additional portnumber - could this be a problem? Yes, that's also something that needs to be fixed. Can you update the patch as shown below, test it, and it if works send the final version to the list? Obviously I am not doing a good job with posting code that I can't test :-/ Am 20.12.2017 um 16:50 schrieb Patrick Ohly: Downloading content and version information via HTTP may need a username/password for basic authentication. To support this, SWUPD_VERSION_URL and SWUPD_CONTENT_URL can now contain URLs of the form http(s)://:@/. Original patch from: Ingo Flaschberger --- lib/swupd/bundles.py | 26 -- 1 file changed, 24 insertions(+), 2 deletions(-) diff --git a/lib/swupd/bundles.py b/lib/swupd/bundles.py index e1eec5a..48c7455 100644 --- a/lib/swupd/bundles.py +++ b/lib/swupd/bundles.py @@ -5,6 +5,7 @@ import subprocess import shutil import urllib.request import urllib.error +import urllib.parse from bb.utils import export_proxies from oe.package_manager import RpmPM from oe.package_manager import OpkgPM @@ -153,6 +154,27 @@ def copy_bundle_contents(d): for bndl in bundles: stage_empty_bundle(d, bndl) +def handle_plain_auth(url): +""" +Check for special urls with username/password (as in http://us er:password@host/), +extract those and install an auth handler which will provide them +to the HTTP server when needed. Returns the URL that is to be instead of the original one. +""" +parsed_url = urllib.parse.urlsplit(url) +if parsed_url.username != None: +# Use the netloc with just the hostname, without username/password. +parsed_url.netloc = parsed_url.hostname Instead: netloc = parsed_url.hostname if parsed_url.port is not None: netloc += ":%d" % parsed_url.port new_url = urllib.parse.SplitResult(parsed_url.scheme, netloc, parsed_url.path, parsed_url.query, parsed_url.fragment) +# The username/password are installed permanently in the urllib.request module +# for future use with all URLs beneath url. +manager = urllib.request.HTTPPasswordMgrWithDefaultRealm() +manager.add_password(None, parsed_url, parsed_url.username, parsed_url.password) +authHandler = urllib.request.HTTPBasicAuthHandler(manager) +opener = urllib.request.build_opener(authHandler) +urllib.request.install_opener(opener) +return urllib.parse.urlunsplit(new_source) Instead: return urllib.parse.urlunsplit(new_url) -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] rdepends = "python3-modules" in recipe does not install python3-modules in image
For this recipe the base package is called users.rpm and I can see it in the RPM. Using 'bitbake users -e | grep PN' I was able to find that PN is also set to users, which seems correct. However the recipe does not install python3-modules even though it's specified in RDEPENDS. I can get it to work by forcing python3-modules in the IMAGE_INSTALL variable, but this is not how I expect yocto to work based on the documentation. From: Alexander Kanavin Sent: Sunday, January 7, 2018 5:10:46 AM To: Matt Schepers Cc: yocto@yoctoproject.org Subject: Re: [yocto] rdepends = "python3-modules" in recipe does not install python3-modules in image On 01/06/2018 08:00 PM, Matt Schepers wrote: > How do I check what PN is set to? I can see users-dbg.rpm and > users-doc.rpm in the rpm folder. The recipe name is users.bb If the recipe is named users, then PN is most likely users as well. -doc and -dbg are supplementary packages. What is the main package called? You can look for it in the rpm directory for example. Alex -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] What is the procedure for creating a board support package?
I'm trying to follow the instructions at: http://www.yoctoproject.org/docs/current/bsp-guide/bsp-guide.html#creating-a-new-bsp-layer-using-the-yocto-bsp-script I followed the prompts exactly as specified (although the SMP support prompt did not appear), and I chose the default 4.12 kernel (presumably the guide is slightly out of date). I included the generated bsp in bblayers.conf as indicated. I invoked: bitbake core-image-minimal However, the resulting build was intel based, and not arm as one might expect since I asked for ARM when prompted by the yocto-bsp script. Is there a more hands-on document that I could be following? Peter. This communication, including any attached documentation, is intended only for the person or entity to which it is addressed, and may contain confidential, personal, and/or privileged information. Any unauthorized disclosure, copying, or taking action on the contents is strictly prohibited. If you have received this message in error, please contact us immediately so we may correct our records. Please then delete or destroy the original transmission and any subsequent reply. Thank you. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Embedded Linux Conference coming up in Portland, Oregon
If you have aspirations to present a talk at ELC/IOT summit this year, time is of the essence, as the CFP expires today. As a reminder, ELC is in Portland the 2nd week in March. The page is here: https://events.linuxfoundation.org/events/elc-openiot-north-america-2018/ This is the premier conference for embedded Linux in the US. The Yocto Project will also be hosting a Developer Day event on the Thursday following the conference. This is a paid training event with introductory and advanced tracks that provides direct access to maintainers and information on all the latest details about the project. Stay tuned for details. Jeffrey “Jefro” Osier-Mixon, Intel Corporation Open Source Community Manager -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] beta testing netbooting Yocto on Amazon, Google & Digital Ocean
Hi folks, I built a website to make it easy to netboot Run-From-RAM operating systems like Yocto Linux on cloud hosts (Google, Amazon & Digital Ocean). I wanted to see if anyone might be interested to give it a try as a beta test. It’s absolutely brand new so likely has bugs and issues. website is https://www.bootrino.com documentation is https://doc.bootrino.com console is https://console.bootrino.com Let me know if you’re interested cause I’d be interested to help directly if any issues come up. thanks! Andrew -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] What is the procedure for creating a board support package?
2018-01-09 19:38 skrev Peter Spierenburg: > I'm trying to follow the instructions at: > > http://www.yoctoproject.org/docs/current/bsp-guide/bsp-guide.html#creating-a-new-bsp-layer-using-the-yocto-bsp-script [1] > > I followed the prompts exactly as specified (although the SMP support prompt did not appear), and I chose the default 4.12 kernel (presumably the guide is slightly out of date). > > I included the generated bsp in bblayers.conf as indicated. > > I invoked: > > bitbake core-image-minimal > However, the resulting build was intel based, and not arm as one might expect since I asked for ARM when prompted by the yocto-bsp script.Is there a more hands-on document that I could be following? > > Peter. > > This communication, including any attached documentation, is intended only for the person or entity to which it is addressed, and may contain confidential, personal, and/or privileged information. Any unauthorized disclosure, copying, or taking action on the contents is strictly prohibited. If you have received this message in error, please contact us immediately so we may correct our records. Please then delete or destroy the original transmission and any subsequent reply. Thank you. Hi Peter, Have you set MACHINE = "myarm" in conf/local.conf in your project? That is required in order to enable full usage of your new bsp. If not it will by default be set to qemux86. Also note that you can type arm instead of qemu when doing it for the real target ($ ./yocto-bsp create myarm arm) BR Petter Petter Mabäcker Technux www.technux.se Links: -- [1] http://www.yoctoproject.org/docs/current/bsp-guide/bsp-guide.html#creating-a-new-bsp-layer-using-the-yocto-bsp-script -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
