kanavin has quit [Remote host closed the connection]
kanavin has joined #yocto
florian has quit [Ping timeout: 250 seconds]
jatedev has quit [Quit: Client closed]
florian has joined #yocto
florian has quit [Ping timeout: 250 seconds]
sakoman has joined #yocto
chelesty[m] has quit [Quit: You have been kicked for being idle]
goliath has quit [Quit: SIGSEGV]
florian_kc has joined #yocto
paulg has quit [Ping timeout: 240 seconds]
florian_kc has quit [Ping timeout: 250 seconds]
manuel1985 has quit [Quit: Leaving]
paulg has joined #yocto
goliath has joined #yocto
dev1990 has quit [Quit: Konversation terminated!]
dev1990 has joined #yocto
ziga_ has quit [Ping timeout: 256 seconds]
goliath has quit [Ping timeout: 256 seconds]
goliath has joined #yocto
huseyinkozan has quit [Quit: Konversation terminated!]
Skinny has joined #yocto
<Skinny>
Hi all! This weekend seemed a good weekend to start my Yocto journey! After reading a log of blobs I dove in and I tried to build my first custom system (based on the qemu x86-64 for now). I'm having a bit of a hard time grabbing the concept of recipes. It seems that the 'meta-cloudservices' layer somehow contains the salt(stack) applications. I
<Skinny>
only need 'that', do I stil have to add the complete "layer" to my project ?
<Skinny>
I have added meta-cloud-services and meta-cloud-services/meta-openstack to my project and added "IMAGE_INSTALL:append = " salt-minion"" to my local.conf. That started to complain about missing dependencies (which I can understand) but now I have a list of over 10 layers added to my project and it still fails to "bake"
<Skinny>
grembeter[m] I figured it must have been something like that.. checked all meta layers out on the same branch and it's now building..
<Skinny>
What's the easiest /preferred way of keeping those layers in sync ?
<Skinny>
as in : I'd like to share this project (build dir) with my coworkers through git. How do I make sure they check out the right branch of every layer ?
<grembeter[m]>
So that, you need additional git repository, that keeps info about “how to checkout (and build) your project”. And you share it.
florian_kc has quit [Ping timeout: 250 seconds]
goliath has quit [Quit: SIGSEGV]
<Skinny>
Thanks! will look into those. Build is almost succesful :)
<Skinny>
``ERROR: salt-3001.1-r0 do_package: QA Issue: salt: Files/directories were installed but not shipped in any package:
<Skinny>
/etc
<Skinny>
/etc/salt
<Skinny>
/etc/logrotate.d
<Skinny>
/etc/salt/master
<Skinny>
/etc/salt/minion
<Skinny>
/etc/logrotate.d/salt
<Skinny>
Please set FILES such that these items are packaged. Alternatively if they are unneeded, avoid installing them or delete them within do_install.
<Skinny>
salt: 6 installed and not shipped files. [installed-vs-shipped]
<Skinny>
it sort of makes sense but curious about where and how to solve this (local.conf ?)
<Skinny>
Adding `FILES_salt += "/etc/salt/master"` to my local.conf doesn't make a difference
<rburton>
Do that in the salt recipe itself
<Skinny>
(for that one file)
<Skinny>
hmm.. that sounds like the recipe (from git) is not ok (out of the box) ?
<Skinny>
adding a file in the recipe removes the error for that file but somehow that doesn't sounds right
<Skinny>
sorry for being a n00b but doesn't this way of excluding those files (by editing the recipe) keep me from sharing a yocto project in git ? Now I'm editing something that's pulled from an external source
amitk has joined #yocto
<barometz>
that's what a bbappend is for
<barometz>
you add a bbappend for the recipe which modifies it without modifying the original files
<barometz>
(or, if possibly, you make a pull request in the upstream repository so it's fixed at the source)
<Skinny>
barometz I know the files mentioned are necessary to run the salt-minion correctly but I need/want to add them from my own layer. I think bbappend (googling that now) is what I need
goliath has joined #yocto
<Skinny>
ok, I have a working build now that I added the mentioned files to a .bbappend file. yay! However I'd like to have the logrotate files from the salt recipe actually included in my build so modified my local.conf with `IMAGE_INSTALL:append = " logrotate salt-minion"`
<Skinny>
This actually installs logrotate but the system starts complaining again about not having the `/etc/logrotate.d/salt` shipped. Who's responsibility is it (normally) to include those files into the produced image ?
<fray>
do you know what the salt file is for? It would be either the recipe OR an init script to generate it
<Skinny>
I know salt (as in: I use that piece of software) and now I want to include it in a yocto build
<Skinny>
I want the default files that are coming out of the salt compilation (/etc/salt and /etc/logrotate.d/salt) to be included in my output
<Skinny>
when I add `FILES:${PN} += "/etc/salt/master /etc/salt/minion /etc/logrotate.d/*"` to the .bb file of the salt recipe, the errors go away but no files are on the target filesystem
<Skinny>
same behaviour when I add them to a .bbappend file (to be expected imo)
<Skinny>
I would have expected that the files mentioned above (which are part of the output of the salt build) to be included in the final image
GNUmoon has quit [Remote host closed the connection]
GNUmoon has joined #yocto
sakoman has quit [Quit: Leaving.]
blauskaerm[m] has joined #yocto
argonautx has joined #yocto
amitk has quit [Ping timeout: 256 seconds]
amitk has joined #yocto
florian_kc has joined #yocto
Tokamak has joined #yocto
florian_kc has quit [Ping timeout: 250 seconds]
amitk has quit [Ping timeout: 250 seconds]
<moto-timo>
You need to install the files in do_install maybe?
Tokamak has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]