<ewi>
yep, i read that. the problem is that build runs without errors and user is created in core-image-full-cmdline/rootfs/etc/passwd, but it is not there when I boot the image. image is a genericx86-64 linux
<mckoan>
ewi: define "is not there"
<ewi>
on installed os
<mckoan>
ewi: how did you implement it?
KhazAkar has joined #yocto
<mckoan>
ewi: how did you test user is created?
<ewi>
I looked at the contents of tmp...etc/passwd and shadow
<ewi>
in the build environment
Saur has joined #yocto
<ewi>
mckoan: it is implemented as in documentation you linked
<mckoan>
ewi: so it will work
<ewi>
no, because it is getting default passwd file from somewhere else
xmn has quit [Read error: Connection reset by peer]
<ad__>
hi, need to remove hostapd from the kirkstone image, i tried PACKAGECONFIG:remove = "hostapd", no way
<alperak>
i think, you should do IMAGE_INSTALL:remove += "hostapd" in image recipe.
ptsneves has quit [Ping timeout: 246 seconds]
<ad__>
alperak: tried that too, same, still built
<ad__>
maybe it's a dependence of some other package ?
ptsneves has joined #yocto
<KhazAkar>
Depends what you have in your local.conf
<KhazAkar>
Or layer you use
<ad__>
ok. How can i check who needs hostapd ?
<KhazAkar>
Either by manually looking at layer files with tool like ripgrep to find hostapd or there's probably some info flag to bitbake, recipetool or something else
<ad__>
ok thanks
<KhazAkar>
Sorry for not exactly answering, I'm still learning Yocto for a project :)
<ad__>
anyway, if i remove also hostapd-example, still hostapd is built :(
awafaa has quit [Server closed connection]
awafaa has joined #yocto
zpfvo has quit [Remote host closed the connection]
<KhazAkar>
Maybe some feature triggers it to build?
<KhazAkar>
Like DISTRO_FEATURE
<ad__>
thanks, grepping around :)
linfax has quit [Ping timeout: 256 seconds]
zpfvo has joined #yocto
flynn378 has quit [Server closed connection]
flynn378 has joined #yocto
zpfvo has quit [Client Quit]
ray-san has quit [Ping timeout: 256 seconds]
halstead has quit [Server closed connection]
halstead has joined #yocto
bhstalel has quit [Quit: Client closed]
sayo9394__ has quit [Remote host closed the connection]
sayo9394__ has joined #yocto
<rburton>
does anyone have an intel board and use genericx86-64 that would be willing to test that a small change I have boots?
Kubu_work has quit [Quit: Leaving.]
sakman has quit [Quit: Leaving]
<RP>
rburton: they burn if you look at them now? :)
<rburton>
haha
<rburton>
i genuinely have one x86 machine in the study and that's the NAS
<RP>
rburton: I'm not sure what I have outside my build machine and laptop. I don't have much hardware now :/
<rburton>
actually alex is going out in an hour, i can borrow his gaming pc. that should be able to boot a normal efi stick.
sakman has joined #yocto
florian has quit [Ping timeout: 246 seconds]
jmd has joined #yocto
<alperak>
let's say i wrote a recipe and i can get it built with gcc. what other tests do i need to do before submitting it to oe or poky? in short, what tests are done after a recipe is written to get it accepted?
<rburton>
check that it works with sysvinit and systemd if it has an init script, check that it builds with musl, check that it builds with at least one other arch (say qemux86-64 and qemuarm64)
frieder has quit [Remote host closed the connection]
<rburton>
also check that it's important enough to go in the layer you propose. the bar for new recipes in oe-core/poky is _high_.
<rburton>
meta-oe has a lower bar but does group recipes by high level function
<mckoan>
rburton: which test?
<rburton>
alperak: the tests done by the oe-core maintainers involve running it through the autobuilder, autobuilder.yoctoproject.org
<rburton>
so that's qemuarm/ppc/mips/x86 for systemd/sysvinit for glibc/musl
danlor has quit [Quit: Client closed]
sayo9394__ has quit [Remote host closed the connection]
alimon has quit [Read error: Connection reset by peer]
mckoan is now known as mckoan|away
sayo9394__ has joined #yocto
<alperak>
thanks for the explanations. i would like to keep the maintainers less hassle possible :D
ewi has quit [Quit: Leaving]
alimon has joined #yocto
prabhakarlad has joined #yocto
alessioigor has joined #yocto
sayo9394__ has quit [Remote host closed the connection]
sayo9394__ has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
jmd has quit [Remote host closed the connection]
jmd has joined #yocto
goliath has joined #yocto
jmd has quit [Remote host closed the connection]
jmd has joined #yocto
jmd has quit [Remote host closed the connection]
jmd has joined #yocto
jmd has quit [Read error: Connection reset by peer]
jmd has joined #yocto
jmd has quit [Read error: Connection reset by peer]
KhazAkar has quit [Quit: Connection closed for inactivity]
jmd has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
sayo9394__ has quit [Remote host closed the connection]
sayo9394__ has joined #yocto
jmd has quit [Remote host closed the connection]
jmd has joined #yocto
jmd has quit [Read error: Connection reset by peer]
lexano has quit [Ping timeout: 268 seconds]
gmorell has quit [Server closed connection]
gmorell has joined #yocto
lukma has quit [Server closed connection]
lukma has joined #yocto
jmd has joined #yocto
jmd has quit [Remote host closed the connection]
jmd has joined #yocto
florian has joined #yocto
jmd has quit [Remote host closed the connection]
lexano has joined #yocto
dvergatal has joined #yocto
jmd has joined #yocto
jmd has quit [Remote host closed the connection]
jmd has joined #yocto
sayo9394__ has quit [Remote host closed the connection]
sayo9394__ has joined #yocto
jmd has quit [Read error: Connection reset by peer]
jmd has joined #yocto
jmd has quit [Read error: Connection reset by peer]
jmd has joined #yocto
Nonkel has joined #yocto
<Nonkel>
Hello
<Nonkel>
I’m busy with the installation of “network-manager”. I add this line to my local.conf: IMAGE_INSTALL += " networkmanager networkmanager-nmtui networkmanager-bash-completion"
<Nonkel>
But the packet is not found in my image, what do I wrong or is needed to configure?
jmd has quit [Remote host closed the connection]
Haxxa has quit [Quit: Haxxa flies away.]
jmd has joined #yocto
<khem>
Nonkel: do IMAGE_INSTALL:append = " etworkmanager networkmanager-nmtui networkmanager-bash-completion"
<khem>
I missed the n at the beginning :) but you get the point, use append instead of +=
<Nonkel>
yes, thanks i gone try this!
Haxxa has joined #yocto
ptsneves has quit [Ping timeout: 246 seconds]
tlhonmey has joined #yocto
alperak has quit [Quit: Client closed]
jmd has quit [Remote host closed the connection]
<khem>
my systemd+openssh distro is failing ptests a lot of them with this error - http://sprunge.us/MEqtAC
<alperak>
when i use REQUIRED_DISTRO_FEATURES, if the person has not added 'foo' to DISTRO_FEATURES, the recipe build will give an error. what i wanted to do was this: if 'foo' is not added to DISTRO_FEATURES, the recipe should automatically add 'foo' itself. :)
tlhonmey has quit [Quit: Client closed]
<khem>
thats not how it is supposed to work.
<khem>
distro features are global policy which drives the recipes not other way around
<khem>
so you provide knobs in recipes which can be triggered based upon a DISTRO_FEATURE
<adrianf>
Nonkel: the networkmanager package is a "meta package". It's empty. But it pulls in many other networkmanager-* packages. Just adding IMAGE_INSTALL:append = " networkmanager" should add a bunch of packages. The IMAGE_INSTALL:append can be set in the image recipe or e.g. the local.conf file. network-manager is probably nothing.
<adrianf>
Also note the space after the ". It's important.
<alperak>
khem JPEW thanks!
sayo9394__ has quit [Remote host closed the connection]
sayo9394__ has joined #yocto
<Nonkel>
my application needs network-manager
alessioigor has quit [Quit: alessioigor]
<Nonkel>
this is the ubuntu package network-manager named
<rburton>
if your app demands the NM daemon to be running then RDEPENDS:${PN} = "networkmanager-daemon" seems like the right thing
<rburton>
or just networkmanager
<rburton>
if you need the libraries at build time then DEPENDS = "networkmanager"
<Nonkel>
i van add this to my local,conf?
<rburton>
the recipe
<rburton>
for your application
<Nonkel>
can you give me more information please where a need to add this? i'm not yet familiar with Yocto.
<rburton>
you said "my application needs network-manager"
<Nonkel>
yes
<rburton>
what is "your application"? is it a recipe you wrote?
<Nonkel>
not my application, for now i install this by hand when my image is created
<rburton>
so just add network-manager to your image's IMAGE_INSTALL
<rburton>
IMAGE_INSTALL:append = " network-manager" is the easiest way to do that, without seeing your image recipe
<rburton>
you can do it in local.conf if you've not written your own image recipe yet
<rburton>
(but you should write your own image recipe)
florian has joined #yocto
<Nonkel>
after adding this i got the error: Nothing RPROVIDES 'systemd-journal-remotenetwork-manager'
<rburton>
you left out the space that I carefully included before "network"