seninha has quit [Remote host closed the connection]
nemik has quit [Ping timeout: 244 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 244 seconds]
nemik has joined #yocto
sakoman has quit [Quit: Leaving.]
davidinux has quit [Ping timeout: 252 seconds]
davidinux has joined #yocto
MrFrank has quit [Read error: Connection reset by peer]
prabhakarlad has quit [Quit: Client closed]
MrFrank has joined #yocto
nemik has quit [Ping timeout: 244 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 252 seconds]
nemik has joined #yocto
starblue has quit [Ping timeout: 265 seconds]
starblue has joined #yocto
jmiehe has joined #yocto
jmiehe has quit [Client Quit]
sakoman has joined #yocto
jclsn has quit [Ping timeout: 264 seconds]
jclsn has joined #yocto
Estrella___ has joined #yocto
Estrella_ has quit [Ping timeout: 265 seconds]
vladest has quit [Remote host closed the connection]
marek has joined #yocto
marek has quit [*.net *.split]
sakoman has quit [Quit: Leaving.]
MrFrank has quit [Read error: Connection reset by peer]
thomasd13 has joined #yocto
MrFrank has joined #yocto
alessioigor has joined #yocto
nemik has quit [Ping timeout: 265 seconds]
nemik has joined #yocto
Payam__ has quit [Remote host closed the connection]
marek has joined #yocto
<LetoThe2nd>
yo dudX
frieder has joined #yocto
frieder has quit [Client Quit]
frieder has joined #yocto
Schlumpf has joined #yocto
rfuentess has joined #yocto
davidinux has quit [Ping timeout: 268 seconds]
davidinux has joined #yocto
zpfvo has joined #yocto
xmn has quit [Ping timeout: 264 seconds]
zpfvo has quit [Remote host closed the connection]
mckoan|away is now known as mckoan
<mckoan>
good morning
leon-anavi has joined #yocto
alimon has quit [Ping timeout: 268 seconds]
<marek>
Good morning, I have general question. I have embedded system with rootfs and data partition. For some files/directories I need to preserve changes done during device commisioning phase. For that purpose I have rootfs postprocess scritp which create symlinks for files/dirs in /data directory. So when I update rootfs configuration data remains
<marek>
untouched. Is there some other way to do this in more elegant way? How about overlayfs? I'm using rootfs in rw mode. Thanks
<LetoThe2nd>
marek: you can also pack the symlinks into proper recipes, thats a common approach. cleaner than postprocessing.
<marek>
LetoThe2nd you mean created them in recipes directly where I need them? They they are spread across layer and I have it now in one place
<LetoThe2nd>
marek: you can also have one recipe thats called "my-magic-symlink_1.0". it of course depends, but i personally do not look into postprocessing when trying to find out where a file or link comes from. it also bypasses all inspection mechanisms.
lexano has quit [Ping timeout: 260 seconds]
<LetoThe2nd>
marek: so in a nutshell, the choice is obviously yours but in my opinion it trades a "i find it simpler now" for technical debt.
<marek>
LetoThe2nd but if I have recipe "my-magic-symlink.bb" and I need to symlink something in /etc/mytestfile when create symlink I need to delete original file and how can I do that in recipe which don't create /etc/mytestfile then?
prabhakarlad has joined #yocto
<LetoThe2nd>
marek: obviously you would need to make the original recipe aware of that. or you can bbappend it and create the symlinks per recipe.
<marek>
LetoThe2nd ok thanks
lexano has joined #yocto
GillesM has joined #yocto
<GillesM>
hi I try the example from bitbake-layers create-layer meta-example ..
<GillesM>
I never see the bb.plain message after the do_build task
<LetoThe2nd>
GillesM: IIRC plain is not severe enough to be shown, it just ends up in the logs. can you try .warn()
<GillesM>
LetoThe2nd, thanks I will try
<GillesM>
LetoThe2nd, same result ..
<LetoThe2nd>
GillesM: and you are specifically bitbaking the example recipe?
ptsneves has joined #yocto
alessioigor has quit [Quit: alessioigor]
fenrig has joined #yocto
alessioigor has joined #yocto
florian has joined #yocto
<marek>
I'm getting: ` Failed to open stream: php_network_getaddresses: getaddrinfo for repo.packagist.org failed: Temporary failure in name resolution` when trying to fetch php packages in kirkstone, while in dunfell it works perfectly fine. I saw also in other recipe issue with python urllib3. Was something changed in kirkstone please? Thanks.
<GillesM>
LetoThe2nd, no bu I didn't add in IMAGE_APPEND ?
<LetoThe2nd>
GillesM: what are you actually running?
<LetoThe2nd>
marek: well, in which stage of the recipe is being run?
<marek>
LetoThe2nd in do compile
<GillesM>
core-image-minimal in qemu mode
<LetoThe2nd>
marek: then thats the problem. all stages except do_fetch are not supposed to do network access, and this is being enforced since kirkstone. you can disable this somehow (don't know right of the bat how, but you will find it), or better, fix your build strategy.
<LetoThe2nd>
GillesM: indeed, then the example recipe won't be built. just give "bitbake example" a try :-)
<marek>
LetoThe2nd many thanks. Will try to find it out how to disable it maybe.
mvlad has joined #yocto
davidinux has quit [Ping timeout: 244 seconds]
davidinux has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
<GillesM>
LetoThe2nd, I see warns on bitbake hello
<LetoThe2nd>
GillesM: sounds good then.
<GillesM>
LetoThe2nd, I don't have to add in IMAGE_INSTALL ?
<LetoThe2nd>
GillesM: if you want to add it to the image, then you have. to just build a recipe, no. you can just bitbake it directly.
<rburton>
marek: the proper fix is to do all the fetching in do_fetch, so checksums/caches/offline builds work properly. if PHP has some funky module fetcher like cargo/npm/etc then a new fetcher module would be the best solution.
<marek>
rburton ok thanks
<GillesM>
I want bitbake display some variable of image with bb.warn
<qschulz>
GillesM: python () { bb.warn(d.getVar('MYVAR')) } in your image recipe?
<GillesM>
yes .. I use this when I make recipe
ptsneves has quit [Ping timeout: 244 seconds]
<LetoThe2nd>
GillesM: what are you *actually* trying to do?
<GillesM>
but I don't see the bb.plain today
<GillesM>
to run the example file
<LetoThe2nd>
GillesM: I already told you, plain only goes into the logs. not to the console.
<GillesM>
LocutusOfBorg, I put warn
<qschulz>
GillesM: how are you building your image recipe?
<GillesM>
bitbake myimage
Schiller has joined #yocto
* LocutusOfBorg
blinks
<qschulz>
LocutusOfBorg: you've been summoned from the darkness, please express yourself
<qschulz>
:)
<LocutusOfBorg>
bitbake darkness -e |grep Locutus
<qschulz>
LocutusOfBorg: ah, old school I see. The cool kids from the block they use bitbake-getvar -r darkness Locutus
vladest has joined #yocto
<Schiller>
Does anyone use the class buildbot.reporters.mail.MailNotifier for the Autobuilder2 and manages to establish a STARTTSLconnection? When i follow the Buildbot documentation the client just hangs
<LocutusOfBorg>
I started when yocto was "ltib"
<LocutusOfBorg>
I remember projects done with danny, year 2012
<qschulz>
LocutusOfBorg: You indeed were summoned from the dark times :D
<LocutusOfBorg>
and since then I did project with *all* the releases on a daily basis
<LetoThe2nd>
LocutusOfBorg: why not share some of your wisdom? alternatively, tales from the crypt?
<LocutusOfBorg>
well, one day, maybe
<LocutusOfBorg>
but actually I have really nothing interesting to show...
<LocutusOfBorg>
I'm just using, developing, fixing, contributing to meta-oe and live happy
<GillesM>
qschulz, I am checking
<LetoThe2nd>
LocutusOfBorg: thats what all devs think, but it is not true. idea: "the 10 most stupid things upstream does to break cross compilation"
<LetoThe2nd>
LocutusOfBorg: somebody maintaining meta-oe certainly has seen a lot of that.
<LocutusOfBorg>
well, I also maintain my company-based-yocto-based distro
<LocutusOfBorg>
and I maintain virtualbox-* kernel modules in meta-oe, and kernel/glib/upstream breaking cross compilation is something I see on each release :D
<LetoThe2nd>
LocutusOfBorg: like i said, its not about showing super fancy (although fancy is also cool), but about the ins and outs of everyday work that newcomers should know.
<LetoThe2nd>
LocutusOfBorg: then theres your topic!
<LocutusOfBorg>
well, I give from time to time classes to my new colleagues
<LocutusOfBorg>
I even have slides
<LetoThe2nd>
LocutusOfBorg: so what do i do in order to have you submit for YPS 2022.11? if you even have content ready? ;-)
<LocutusOfBorg>
let me check if I find slides and if company allows me to do this
<LetoThe2nd>
LocutusOfBorg: +1
<LocutusOfBorg>
do you have an email? or can I share slides here via irc?
<LocutusOfBorg>
its a really beginner talk
<LocutusOfBorg>
but I don't know how many are interested in "what is yocto", maybe I might prepare something more deep
<LocutusOfBorg>
LetoThe2nd, I also have an Ubuntu developer summit in Prague in november, let me also check schedule
<olte>
And I think that there are likely many more similar issues
<rburton>
don't use them :)
<rburton>
use .gz if you must
<rburton>
but a git clone would be better
<kayterina[m]>
Hello, I have a recipe that uses another recipe's files. recipeA installs at /var/somepath/file.xml and recipeB has DEPENDS = "recipeA" and in do_compile() I reference $WORKDIR/var/somepath/file.xml. Is it acceptable by yocto standars or is there some more abstraction I can do?
<rburton>
don't refer to workdir, as it won't exist in a build from sstate
<rburton>
if A writes the files you want to share to the sysroot then B can depend on A and it will be in the sysroot
<rburton>
the sysroot is by default pruned a bit
<JaMa>
rburton: heh and it weren't crawlers, but olte's jenkins jobs.. :)
<rburton>
kayterina[m]: see SYSROOT_DIRS in staging.bbclass
<rburton>
JaMa: yeah maybe :)
<kayterina[m]>
So, WORKDIR/recipe-sysroot will not exist in sstate build?
Payam has quit [Ping timeout: 248 seconds]
nemik has quit [Ping timeout: 252 seconds]
nemik has joined #yocto
<kayterina[m]>
recipeA has SYSROOT_DIRS += "${localstatedir}" so that makes its /var available to other recipes.
prabhakarlad has quit [Quit: Client closed]
nemik has quit [Ping timeout: 265 seconds]
nemik has joined #yocto
<kayterina[m]>
There is a tmp/work/cortex/recipeB/0.1-r0/recipe-sysroot/sysroot-providers/recipeA
<kayterina[m]>
Should I reference it as "${RECIPE_SYSROOT}${localstatedir}" or ${STAGING_DIR_HOST}${localstatedir}? They are both inside workdir, how can I not reference workdir?
<kayterina[m]>
The files I want to use are in tmp/work/cortexa9/recipeB/0.1-r0/recipe-sysroot/var/
xmn has joined #yocto
Schiller has joined #yocto
<Schiller>
Hello, i want to use the MailNotifier from Buildbot with STARTTLS. Problem is, our Logins don't use the full E-Mail-Adresses, so without _whitelogger... But i have just the Parameter smtpUser. So i either run into the Error Helo command rejected: need fully-qualified hostname or Error: authentication failed: UGFzc3dvcmQ6. Is there a secound
<Schiller>
paremeter which i didn't find yet or an easy workaround? I don't want to set up an extra Mailing-Server to redirect.
<mrybczyn[m]>
I'm working on integrating the current kirkstone after the fixes from landgraf: on dropbear vs openssh. It doesn't work with core-image-weston, still a conflict here. From what I can see, the whole openssh conflict with dropbear, not only the ssh server itself
sakoman has joined #yocto
nemik has quit [Ping timeout: 260 seconds]
nemik has joined #yocto
MrFrank has quit [Read error: Connection reset by peer]
<mrybczyn[m]>
It adds IMAGE_FEATURE ssh-server-dropbear
nemik has quit [Ping timeout: 246 seconds]
nemik has joined #yocto
prabhakarlad has joined #yocto
kscherer has joined #yocto
<mrybczyn[m]>
I'm wondering why it doesn't conflict in other setups
MrFrank has joined #yocto
<mrybczyn[m]>
Do we agree that it is the openssh sshd server that conflicts and not some other packages like the sftp server?
inisider has joined #yocto
Schiller has quit [Ping timeout: 244 seconds]
seninha has joined #yocto
Schiller has joined #yocto
vvn has joined #yocto
thomasd13 has quit [Ping timeout: 244 seconds]
tnovotny has joined #yocto
MrFrank has quit [Read error: Connection reset by peer]
odra has quit [Remote host closed the connection]
odra has joined #yocto
odra_ has joined #yocto
odra has quit [Ping timeout: 268 seconds]
nemik has quit [Ping timeout: 268 seconds]
nemik has joined #yocto
gchamp has joined #yocto
nemik has quit [Ping timeout: 264 seconds]
nemik has joined #yocto
MrFrank has joined #yocto
<landgraf>
mrybczyn[m]: maybe it's not complementary packages which cause the conflict this time? I'm opening bugreport to investigate
rfuentess has quit [Remote host closed the connection]
Guest84 has joined #yocto
<Guest84>
Hi, I'm new to Yocto and I am trying to add meta-ros layer (ROS melodic) to my yocto Thud. I initially got the error "Nothing RPROVIDES 'python-pycryptodomex'". I searched online and found the recipe python-pycryptodomex_3.9.3.bb and python3-pycryptodomex_3.9.4.bb and added them to meta-ros. Now I am getting a new error "Postinstall scriptlets of
<Guest84>
['busybox'] have failed". I would appreciate any help.
<rburton>
Guest84: did you checkout the thud branch for the layer you took them from?
<rburton>
also thud is incredibly obsolete, don't use it
<qschulz>
Guest84: meta-openembedded/meta-python has this recipe, so just include this layer in its thud branch
<qschulz>
and also, as rburton said, don't use thud
<qschulz>
Dunfell at the very least, otherwise Kirkstone, both LTSes for still a year and a half (mini, maybe more if sponsors)
<Guest84>
rburton: Yes, I did checkout thud branch. I added these layers from meta-ros: meta-ros1-melodic, meta-ros1, meta-ros-common, meta-ros-backports-warrior.
olte has quit [Quit: leaving]
<Guest84>
rburton, qschulz, thank you, I am aware of thud being EOL, I have reached out to the vendor and have asked for a newer version of Yocto, hopefully will get it at some point.
<rburton>
rebasing the bsp to kirkstone is probably not that hard
inisider has quit [Remote host closed the connection]
<Guest84>
rburton: I will try rebasing to kirkstone, but I will definitely need some help from the community here :-)
Vonter has joined #yocto
jmiehe has joined #yocto
seninha has quit [Quit: Leaving]
MrFrank has quit [Read error: Connection reset by peer]
seninha has joined #yocto
frieder has quit [Remote host closed the connection]
tnovotny has quit [Quit: Leaving]
jmiehe has quit [Ping timeout: 268 seconds]
PhoenixMage has quit [Ping timeout: 265 seconds]
PhoenixMage has joined #yocto
seninha has quit [Quit: Leaving]
PhoenixMage has quit [Ping timeout: 260 seconds]
PhoenixMage has joined #yocto
mckoan is now known as mckoan|away
GillesM has quit [Quit: Leaving]
seninha has joined #yocto
seninha has quit [Remote host closed the connection]
seninha has joined #yocto
seninha has quit [Quit: Leaving]
MrFrank has joined #yocto
leon-anavi has quit [Quit: Leaving]
nemik has quit [Ping timeout: 264 seconds]
<Guest84>
trying to rebase thud to kirkstone I am getting this error "ERROR: Variable BBMASK_append file: ***conf/layer.conf line: 10 contains an operation using the old override syntax. Please convert this layer/metadata before attempting to use with a newer bitbake.". What are the steps to find the equivalent of BBMASK_append (thud) in Kirkstone?
kanavin has quit [Remote host closed the connection]
Haxxa has quit [Quit: Haxxa flies away.]
Haxxa has joined #yocto
cmd has quit [Remote host closed the connection]
kanavin has joined #yocto
kanavin has quit [Remote host closed the connection]
florian_kc has joined #yocto
prabhakarlad has quit [Quit: Client closed]
marek has quit [Ping timeout: 244 seconds]
Schiller has quit [Quit: Client closed]
zhmylove has joined #yocto
<zhmylove>
Hi everyone! I'm in a total mess of a documentation. I'd like to send a PR to Poky (looks like OpenEmbedded-Core is the correct place) and even got a write access to poky-contrib repo. But when I run scripts/create-pull-request, it just hungs on timeout to https of push.yoctoproject.org/poky-contrib/. What am I doing wrong? Thanks! Into which channel should I send such a question?
zhmylove has quit [Client Quit]
mvlad has quit [Remote host closed the connection]
sakoman has joined #yocto
jmiehe has joined #yocto
kanavin has joined #yocto
kanavin has quit [Remote host closed the connection]
nemik has quit [Ping timeout: 260 seconds]
nemik has joined #yocto
prabhakarlad has joined #yocto
nemik has quit [Ping timeout: 268 seconds]
nemik has joined #yocto
kanavin has joined #yocto
nemik has quit [Ping timeout: 265 seconds]
nemik has joined #yocto
prabhakarlad has quit [Quit: Client closed]
dkl has quit [Quit: %quit%]
dkl has joined #yocto
Guest84 has quit [Quit: Client closed]
seninha has joined #yocto
seninha has quit [Client Quit]
seninha has joined #yocto
Guest84 has joined #yocto
vvn has quit [Quit: WeeChat 3.6]
seninha has quit [Quit: Leaving]
seninha has joined #yocto
nemik has quit [Ping timeout: 265 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 244 seconds]
nemik has joined #yocto
MrFrank has quit [Read error: Connection reset by peer]
Piraty has quit [Quit: -]
camus1 has joined #yocto
camus has quit [Remote host closed the connection]