<Guest92>
Can you please tell me why am I getting error with new yocto executing this code as this worked in old yocto. I'll appreicate your response
enok has joined #yocto
fotte has joined #yocto
frieder has joined #yocto
enok has quit [Ping timeout: 255 seconds]
ehussain has joined #yocto
ahussain has joined #yocto
ehussain has quit [Ping timeout: 258 seconds]
ahussain is now known as ehussain
zpfvo has joined #yocto
ahussain has joined #yocto
ehussain has quit [Ping timeout: 258 seconds]
ahussain is now known as ehussain
jmiehe has joined #yocto
jmiehe has quit [Client Quit]
ehussain has quit [Read error: Connection reset by peer]
florian has joined #yocto
florian_kc has joined #yocto
Jones42 has joined #yocto
rfs613- has joined #yocto
rfs613 has quit [Ping timeout: 252 seconds]
kalj has joined #yocto
wbw has joined #yocto
jmd` has joined #yocto
jmd` has quit [Remote host closed the connection]
jmd has quit [Remote host closed the connection]
jmd has joined #yocto
florian_kc has quit [Ping timeout: 252 seconds]
zkrx has quit [Ping timeout: 258 seconds]
goliath has joined #yocto
zkrx has joined #yocto
jmiehe has joined #yocto
kalj has quit [Quit: Client closed]
jmiehe has quit [Client Quit]
rfs613 has joined #yocto
rfs613- has quit [Ping timeout: 255 seconds]
mbulut has joined #yocto
wbw has quit [Ping timeout: 256 seconds]
viric has left #yocto [#yocto]
sakoman has quit [Ping timeout: 272 seconds]
eminboydak has quit [Quit: Client closed]
xmn has joined #yocto
sakoman has joined #yocto
amitk has joined #yocto
Noor has joined #yocto
<Noor>
hello all
<Noor>
May I know what does this warning to show up "WARNING: base-files-3.0.14-r89 do_packagedata: Error talking to server: Timed out waiting for server"
<RP>
Noor: you have a hash equivalence server configured which isn't contactable
<Noor>
RP is this due to high number of PARALLEL_MAKE/BB_NUMBER_THREAD?
<Noor>
we face this issue on freshly installed host only
<Noor>
we face this warning on freshly installed host only
<RP>
Noor: it could be if it is intermittent
<RP>
it would be high numbers of BB_NUMBER_THREADS as PARALLEL_MAKE wouldn't affect it
jmiehe has joined #yocto
<Noor>
Thanks
Noor has quit [Quit: Client closed]
enok has joined #yocto
jmiehe has quit [Quit: jmiehe]
enok has quit [Ping timeout: 260 seconds]
Minvera has joined #yocto
Daanct12 has quit [Quit: WeeChat 4.3.5]
jmd has quit [Remote host closed the connection]
jmd has joined #yocto
Guest92 has quit [Ping timeout: 256 seconds]
jmd has quit [Remote host closed the connection]
jmd has joined #yocto
BenBE has quit [Ping timeout: 272 seconds]
Xagen has joined #yocto
Guest92 has joined #yocto
<RP>
jonmason: you have remembered you have two high bugs?
<jonmason>
RP: yes, and need to update them
<jonmason>
I _think_ I have an idea why one of them is not working
fotte has quit [Ping timeout: 255 seconds]
BenBE has joined #yocto
Articulus has quit [Quit: Leaving]
florian has quit [Quit: Ex-Chat]
Guest92 has quit [Ping timeout: 256 seconds]
florian_kc has joined #yocto
zpfvo has quit [Remote host closed the connection]
mvlad has joined #yocto
Guest92 has joined #yocto
amitk has quit [Ping timeout: 252 seconds]
florian__ has joined #yocto
florian_kc has quit [Ping timeout: 258 seconds]
Guest92 has quit [Ping timeout: 256 seconds]
leon-anavi has quit [Quit: Leaving]
goliath has quit [Quit: SIGSEGV]
mbulut has quit [Quit: Leaving]
mbulut has joined #yocto
florian__ has quit [Ping timeout: 252 seconds]
jmd has quit [Remote host closed the connection]
jmd has joined #yocto
florian__ has joined #yocto
jmd has quit [Read error: Connection reset by peer]
jmd has joined #yocto
<jonmason>
RP: just updated 15562 (systemd sbsa-ref failing to boot). Do you know if other machines are seeing this issue or just sbsa-ref?
<jonmason>
it's worded like there are others but no listing of them is made
jmd has quit [Remote host closed the connection]
jmd has joined #yocto
enok has joined #yocto
jmd has quit [Remote host closed the connection]
jmd has joined #yocto
enok has quit [Ping timeout: 252 seconds]
florian__ has quit [Ping timeout: 255 seconds]
alessioigor has joined #yocto
<khem>
RP:I am seeing a systemd wreck on a arm64/imx8/coral board, its using kernel 5.4 I dont know if that combo of systemd 256 and kernel 5.4 is regressing, would like to hear from others too
jmd has quit [Remote host closed the connection]
frieder has quit [Remote host closed the connection]
mvlad has quit [Remote host closed the connection]
<mbulut>
i have a recipe A that installs a systemd template unit and a recipe B that DEPENDS on A and instantiates the template
<mbulut>
do_package however complains about not being able to find the service unit / template
<mbulut>
the template exists in package B's sysroot though
<mbulut>
any idea what else i could check?
prabhakalad has quit [Ping timeout: 260 seconds]
florian__ has joined #yocto
prabhakalad has joined #yocto
<mbulut>
do_package: Didn't find service unit 'foo@foobar.service', specified in SYSTEMD_SERVICE:foobar. Also looked for service unit 'foo@.service'
Xagen has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<mbulut>
but there is a recipe-sysroot/lib/systemd/system/foo@.service
alessioigor has quit [Remote host closed the connection]
<mischief>
probably the class only deals with units installed by the recipe
ptsneves has joined #yocto
fotte has joined #yocto
prabhakalad has quit [Remote host closed the connection]
prabhakalad has joined #yocto
dmoseley_ has quit [Ping timeout: 245 seconds]
<mbulut>
added some debug prints into systemd_check_services() in systemd.bbclass to find out...
dmoseley has joined #yocto
ptsneves has quit [Ping timeout: 252 seconds]
enok has joined #yocto
enok has quit [Client Quit]
florian__ has quit [Ping timeout: 260 seconds]
prabhakalad has quit [Ping timeout: 245 seconds]
prabhakalad has joined #yocto
prabhakalad has quit [Ping timeout: 252 seconds]
prabhakalad has joined #yocto
BenBE has quit [Ping timeout: 244 seconds]
fotte has quit [Ping timeout: 244 seconds]
florian__ has joined #yocto
florian__ has quit [Ping timeout: 255 seconds]
Xagen has joined #yocto
<mischief>
is it possible to build two kernels for one machine for use in different images in one invocation of bitbake? e.g. bitbake core-image-uses-kernel1 core-image-uses-kernel2. we'd like to see about using two different Kconfigs for different images..