tammranil has quit [Remote host closed the connection]
tammranil has joined #yocto
Xogium has quit [Ping timeout: 260 seconds]
Xogium has joined #yocto
jmd has joined #yocto
_whitelogger has joined #yocto
savolla has joined #yocto
frgo has quit [Read error: Connection reset by peer]
frgo has joined #yocto
dmoseley_ has joined #yocto
dmoseley has quit [Ping timeout: 260 seconds]
rfuentess has joined #yocto
savolla has quit [Quit: WeeChat 4.6.3]
savolla has joined #yocto
wmills__ has joined #yocto
wmills_ has quit [Ping timeout: 272 seconds]
chep has quit [Read error: Connection reset by peer]
chep has joined #yocto
leon-anavi has joined #yocto
alperak has joined #yocto
_matu3ba- has joined #yocto
_matu3ba- has quit [Ping timeout: 260 seconds]
jmd has quit [Remote host closed the connection]
vthor has quit [Excess Flood]
vthor has joined #yocto
vthor has quit [Changing host]
vthor has joined #yocto
_matu3ba- has joined #yocto
rfuentess has quit [Remote host closed the connection]
jmd has joined #yocto
florian has joined #yocto
Vonter has joined #yocto
olani_ has joined #yocto
bhstalel has joined #yocto
ablu has quit [Ping timeout: 265 seconds]
ablu has joined #yocto
olani_ has quit [Ping timeout: 248 seconds]
zeemate has joined #yocto
rfuentess has joined #yocto
<bhstalel>
regarding initramfs, can't we compile the kernel once ? why two compilations are done, with backup process ?
<bhstalel>
is it something to do with fitimage ?
clementp has joined #yocto
<frosteyes>
Hi folks. In the image.bbclass we have the reproducible_final_image_task. Where the timestamp is set with find ${IMAGE_ROOTFS} -print0 | xargs -0 touch -h --date=@$REPRODUCIBLE_TIMESTAMP_ROOTFS
<frosteyes>
I have a gitlab runner - running a docker yocto builder. It have problem setting those timestamps...
<frosteyes>
touch: setting times of '/builds/-Ldo4Ky9Y/0/project/xxx/pil/yocto/build/tmp/work/xxxx/x-rootfs/1.0/rootfs/usr/share/common-licenses/generic_Apache-2.0': Operation not permitted
<rburton>
bhstalel: likely the known bug where it has to rebuild the image to attach the initramfs on the end. this is why i sort of advocate splitting kernel and fit images entirely
<frosteyes>
Can it be some permission the docker container need for setting timestamp.. Or some permission for the touch process started by xargs.
<frosteyes>
More if anyone have experienced something similar.
<clementp>
Hello,
<clementp>
I'm using Yocto to build some container.
<clementp>
I'm bumping to scarthgap and I get the following issue when running supervisor
<clementp>
```
<clementp>
Traceback (most recent call last):
<clementp>
File "/usr/bin/supervisorctl", line 5, in <module>
<clementp>
from supervisor.supervisorctl import main
<clementp>
File "/usr/lib/python3.12/site-packages/supervisor/supervisorctl.py", line 27, in <module>
<clementp>
import getpass
<clementp>
ModuleNotFoundError: No module named 'getpass'
<clementp>
```
<clementp>
The getpass module is an internal module to cpython.
<clementp>
I'm missing something ?
<clementp>
I can see the file in the sysroot when building the container
<clementp>
cat: can't open '/usr/lib/python3.12/getpass.py': No such file or directory
<clementp>
nothing ..
_matu3ba- has quit [Ping timeout: 272 seconds]
<clementp>
Hmm ok it has been moved to a python3-unixadmin package ...
Daanct12 has quit [Quit: WeeChat 4.6.3]
<rburton>
clementp: 1) if you want all of python in your image you can add python3 to IMAGE_INSTALL. but 2) the supervisor recipe should have that in RDEPENDS, so that's a bug and a patch would be good
clementp has quit [Ping timeout: 272 seconds]
olani- has quit [Remote host closed the connection]
olani has quit [Ping timeout: 252 seconds]
Xagen has joined #yocto
Xagen has quit [Remote host closed the connection]
Xagen has joined #yocto
|Xagen has joined #yocto
Xagen_ has joined #yocto
Xagen__ has joined #yocto
Xagen___ has joined #yocto
Xagen has quit [Ping timeout: 260 seconds]
Xagen has joined #yocto
_matu3ba- has joined #yocto
|Xagen has quit [Ping timeout: 272 seconds]
|Xagen has joined #yocto
Xagen_ has quit [Ping timeout: 260 seconds]
Xagen_ has joined #yocto
Xagen__ has quit [Ping timeout: 272 seconds]
Xagen___ has quit [Ping timeout: 268 seconds]
Xagen__ has joined #yocto
Xagen has quit [Ping timeout: 272 seconds]
Xagen has joined #yocto
Xagen___ has joined #yocto
|Xagen has quit [Ping timeout: 276 seconds]
Xagen_ has quit [Ping timeout: 276 seconds]
|Xagen has joined #yocto
vvn has joined #yocto
Xagen_ has joined #yocto
Xagen__ has quit [Ping timeout: 276 seconds]
Xagen has quit [Ping timeout: 276 seconds]
MarcWeDLM has joined #yocto
Xagen has joined #yocto
<vvn>
hi there -- in order to have a distro ported on various BSPs, I'd expect a single distro layer with dynamic-layers for the different machine-specific configurations. Is that what you guys are doing or do you end up with some meta-company-bsp1, meta-company-bsp2 layers, etc.?
Xagen___ has quit [Ping timeout: 276 seconds]
Xagen__ has joined #yocto
Xagen___ has joined #yocto
|Xagen has quit [Ping timeout: 276 seconds]
Xagen_ has quit [Ping timeout: 248 seconds]
|Xagen has joined #yocto
Xagen has quit [Ping timeout: 276 seconds]
Xagen_ has joined #yocto
Xagen__ has quit [Ping timeout: 248 seconds]
Xagen has joined #yocto
Xagen___ has quit [Ping timeout: 276 seconds]
Xagen__ has joined #yocto
Xagen___ has joined #yocto
|Xagen has quit [Ping timeout: 276 seconds]
Xagen____ has joined #yocto
Xagen_ has quit [Ping timeout: 248 seconds]
|Xagen has joined #yocto
Xagen has quit [Ping timeout: 252 seconds]
Xagen__ has quit [Ping timeout: 252 seconds]
Xagen___ has quit [Ping timeout: 252 seconds]
Xagen____ has quit [Ping timeout: 252 seconds]
<rburton>
what you said is sensible
prabhakalad has quit [Ping timeout: 265 seconds]
prabhakalad has joined #yocto
bhstalel has quit [Quit: Client closed]
bhstalel has joined #yocto
<bhstalel>
vvn Why you need multiple bsp layers ?
_matu3ba- has quit [Quit: Konversation terminated!]
jmd has quit [Remote host closed the connection]
<vvn>
I did not say I need these layers. I asked if one usually ends up splitting the distro layer for every supported BSPs or if a single distro layer with dynamic-layers was enough.
<bhstalel>
I usually use one distro layer, and one bsp layer that has multiple machines (if the project works on multiple boards), otherwise, I create multiple bsp layers for different SoCs, but always one distro layer
jmd has joined #yocto
<vvn>
bhstalel: you usually don't need to write a machine conf for every supported boards, only if that is a custom hardware (in this case yes a meta-company-product1 BSP layer is recommended)
rfuentess has quit [Remote host closed the connection]
jmd has quit [Remote host closed the connection]
bhstalel has quit [Quit: Client closed]
vthor_ has joined #yocto
vthor has quit [Ping timeout: 248 seconds]
MarcWeDLM has quit [Quit: Client closed]
kanavin has quit [Remote host closed the connection]
kanavin has joined #yocto
kanavin has quit [Remote host closed the connection]
kanavin has joined #yocto
kanavin has quit [Remote host closed the connection]
jmd has joined #yocto
<AdrianF>
bhstalel: regarding initramfs and FIT image, what's the context? A few days ago some patches re-writing the FIT image have been merged.
davidinux has joined #yocto
kanavin has joined #yocto
kanavin has quit [Remote host closed the connection]
kanavin has joined #yocto
kanavin has quit [Remote host closed the connection]
jmd has quit [Remote host closed the connection]
kergoth has joined #yocto
jmd has joined #yocto
jmd has quit [Remote host closed the connection]
florian has quit [Ping timeout: 276 seconds]
pidge has joined #yocto
leon-anavi has quit [Quit: Leaving]
|Xagen has quit [Read error: Connection reset by peer]
Xagen has joined #yocto
savolla has quit [Ping timeout: 260 seconds]
savolla has joined #yocto
florian has joined #yocto
Vonter has quit [Ping timeout: 276 seconds]
kergoth has quit [Quit: Connection closed for inactivity]
druppy has joined #yocto
alimon has quit [Ping timeout: 276 seconds]
jpuhlman- has quit [Ping timeout: 276 seconds]
davidinux has quit [Ping timeout: 260 seconds]
Kubu_work has quit [Quit: Leaving.]
yudjinn has joined #yocto
<yudjinn>
hey is there a better way to define metadata on a function? I'd like to have a function that looks like `custom_func[abstract] () {...}` that I can later consume using `d.getVarFlags('custom_func').keys()`
<yudjinn>
but that flat out wont parse
jpuhlman has joined #yocto
jpuhlman has quit [Read error: Connection reset by peer]
jpuhlman has joined #yocto
ptsneves has quit [Ping timeout: 260 seconds]
ptsneves has joined #yocto
florian has quit [Ping timeout: 260 seconds]
ptsneves has quit [Ping timeout: 252 seconds]
Kubu_work has joined #yocto
druppy has quit [Remote host closed the connection]
druppy has joined #yocto
druppy has quit [Ping timeout: 252 seconds]
alperak has quit [Quit: Connection closed for inactivity]
jerrycash2 has quit [Read error: Connection reset by peer]