On 12/07/2016 19:44, "Romain Bazile" <[email protected]> wrote:
>Hi Belen, > > >Thanks for answering. >I finally had some time to go through testing again! >I cleaned the poky folder (removed build dirs), dropped the database and >started again. > >I answered inlined to your questions. > > >On 07/07/2016 12:04, Barros Pena, Belen wrote: > > >Hi Romain, > >Thanks for giving Toaster a go, and sorry for the troubles. Let's see if >we can work out what's going on. > >On 06/07/2016 19:10, "[email protected] on behalf of Romain >Bazile" <mailto:[email protected]> ><[email protected] on behalf of >[email protected]> ><mailto:[email protected][email protected] >> wrote: > >Hello everyone, > >I set up a small production setup for Toaster, based on the information > > >>from the Krogoth manual at >http://www.yoctoproject.org/docs/2.1/toaster-manual/toaster-manual.html . > >Everything is working well, except when I add a custom layer (like, in >this example, meta-raspberry, located at >git://git.yoctoproject.org/meta-raspberrypi ) > > >I have a question about this. I am assuming you had to import >meta-raspberrypi because it was not listed in the compatible layers of >your Toaster project. Which release did you select when creating your >Toaster project? Krogoth? > > >Yes, exactly! I used the Krogoth branch. > >When I try to get the list of recipes, Toaster informs me that >"Toaster does not have recipe information for the *meta-raspberrypi * >layer. >Toaster learns about layers when you build them. If this layer provides >any recipes, they will be listed here after you build the >*meta-raspberrypi * layer." > > >This is expected: unfortunately, Toaster does not parse layers until build >time, so right after importing and before building Toaster just knows the >location of the Git repository, and only because you typed that when >importing the layer ;) > >This makes sense to me. However, what does not is how I go about >building the layer... > > >I tried putting the layer name in the "recipe I want to build" box, but >it fails miserably with a >"Existing git repository at /var/www/toaster/poky, but with different >remotes ('origin git://git.yoctoproject.org/poky (fetch), origin >git://git.yoctoproject.org/poky (push), ', expected >'git://git.yoctoproject.org/meta-raspberrypi'). Toaster will not >continue out of fear of damaging something." > >This makes sense too as I didn't even fed Toaster with a valid recipe >name. > > >Exactly. You don't build the layer per se: you build one or more recipes >provided by the layer. > >But when I try with rpi-basic-image (and after changing the machine name >to raspberrypi2), I have the same error: >"Existing git repository at /var/www/toaster/poky, but with different >remotes ('origin git://git.yoctoproject.org/poky (fetch), origin >git://git.yoctoproject.org/poky (push), ', expected >'git://git.yoctoproject.org/meta-raspberrypi'). Toaster will not >continue out of fear of damaging something." > > >I am using the local setup, instead of the production one, and with that I >don't seem to be able to replicate the issue. This is what I did: > >1. I created a new project, selecting the Krogoth release >2. I imported meta-raspberrypi with git repo >git://git.yoctoproject.org/meta-raspberrypi, master as the git revision >and dependencies openembedded-core and meta-oe >3. I changed the machine to raspberrypi2 >4. I built rpi-basic-image > >The build is running happily. Are these the steps you followed? Or are you >doing something different? > > > >So, this is what I tried to do (I already have another project with >another machine and a successful build, but no other build going on): > >1. New empty project, with Krogoth release, named gateway-rasp-krogoth > >2. Import of meta-raspberrypi, same settings as yours > >3. machine to raspberrypi2 >4. build done > > >This left me perplexed, so I tried again. >One difference though, I made a mistake while typing, and not thinking >straight I put "HEAD" as a revision for the repository. >It did not like that and crashed the build with the same error. Mmm, Toaster should probably handle that case a bit better. I will discuss with some people and see if there is anything we could do. >And, when I tried to put the name of the revision back to master, it >would apparently save the setting, but when I reload the layer config >page, the setting went back to HEAD. > >So, I think the mistake was mine (I must have put "HEAD" instead of >"master"). But it seems like toaster doesn't save the git revision when I >try to change it. Yes, this is a very annoying bug we didn't have time to fix for the stable release. There is a patch now on master for it http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=36dec688c7e50e02e 55c070f04c396e2d1aa3ef3 You could try to cherrypick it, but there is a chance it won't apply. If you try, let me know what happens if you have a moment :) Cheers Belén > > > >Thanks, > > > > >Cheers, > > >Thanks! > >Belén > >This also happens with another recipe (like rpi-hwup-image for example). > >I'm not sure what I should be doing to prevent this. > >I already checked that all the layers that meta-raspberrypi depends on >are known to Toaster. > > >Thanks for reading me! > > >Cheers, >-- > >Romain Bazile > >-- >_______________________________________________ >toaster mailing list >[email protected]https://lists.yoctoproject.org/listinfo/toaster > > > > > > > >-- >Romain Bazile > > -- _______________________________________________ toaster mailing list [email protected] https://lists.yoctoproject.org/listinfo/toaster
