kscherer has quit [Quit: Konversation terminated!]
Soopaman has quit [Quit: Leaving.]
Chocobo has quit [Remote host closed the connection]
davidinux has quit [Ping timeout: 268 seconds]
davidinux has joined #yocto
starblue has quit [Ping timeout: 246 seconds]
starblue has joined #yocto
<khem>
RP: yes, it will help clang-16 to compile packages
<khem>
JaMa: My default compiler is clang so mostly I missed it thus far and my CI loop was busy sorting gnome 44 patches so no have not gotten to it yet
\dev\ice has quit [Read error: error:1408F10B:SSL routines:ssl3_get_record:wrong version number]
<barath>
is there some logic behind some recipes using PN_git.bb and then setting PV = "1.3.3.7"instead of setting the PV in the filename? some convention/reasoning I havent come across yet?
dgriego_ has joined #yocto
camus has quit [Remote host closed the connection]
dgriego has quit [Ping timeout: 276 seconds]
camus has joined #yocto
dgriego_ has quit [Ping timeout: 255 seconds]
dgriego has joined #yocto
alessioigor has joined #yocto
<thomasd13>
barath, I think its easier for versioning systems when files dont get renamed all the time, after just the version info of the packages changed. But I could be wrong here
tunahan has joined #yocto
wooosaiiii has quit [Quit: wooosaiiii]
<barath>
in git it'll look like a rename, but yeah. the yocto manual just says "PV is generally not overridden within a recipe unless it is building an unstable (i.e. development) version from a source code repository (e.g. Git or Subversion)." but 🤷 doesn't seem to be quite followed everywhere
wooosaiiii has joined #yocto
mvlad has joined #yocto
Guest7090 has joined #yocto
<Guest7090>
khem The RTC problem we talked about last night has been resolved.
<Guest7090>
# Set system time from RTC on startup.
<Guest7090>
CONFIG_RTC_HCTOSYS=y
<Guest7090>
CONFIG_RTC_HCTOSYS_DEVICE="rtc0"
<Guest7090>
# Enable PC-TYPE CMOS
<Guest7090>
CONFIG_RTC_MC146818_LIB=y
<Guest7090>
CONFIG_RTC_DRV_CMOS=y
<Guest7090>
Additionally, updated CONFIG_RTC_DRV_PCF8563=m to CONFIG_RTC_DRV_PCF8563=y as you said. Now, "hwclock to system clock set" running later RTC init.
<Guest7090>
khem thank you.
Thorn has quit [Ping timeout: 250 seconds]
GillesM has joined #yocto
Guest7090 has quit [Quit: Client closed]
aak-rookie has joined #yocto
goliath has joined #yocto
frieder has joined #yocto
<JaMa>
early christmas oe-selftest - INFO - oe-selftest - OK - All required tests passed (successes=517, skipped=7, failures=0, errors=0)
<JaMa>
RP: will spend a bit more time investigating why that esdk task fails without uninative and then send the next batch of selftest fixes (the last issues I've reported were mostly caused by runqemu script changes I had locally, but now resolved and one issue was caused because I've build uninative-tarball with gcc-13 support only for x86-64 and the test was trying to use i686)
bryanb has joined #yocto
MathiasKoch[m] has joined #yocto
shivamurthy has joined #yocto
Peter[m]12 has joined #yocto
esben[m] has joined #yocto
ericson2314 has joined #yocto
Salamandar has joined #yocto
Saur[m] has joined #yocto
fury has joined #yocto
kergoth has joined #yocto
DasChaos[m] has quit [Ping timeout: 256 seconds]
berton[m] has quit [Ping timeout: 246 seconds]
shoragan[m] has quit [Ping timeout: 246 seconds]
Max[m] has quit [Ping timeout: 246 seconds]
MathiasKoch[m] has quit [Ping timeout: 248 seconds]
esben[m] has quit [Ping timeout: 248 seconds]
nothingtohide[m] has quit [Ping timeout: 246 seconds]
phako[m] has quit [Ping timeout: 246 seconds]
tunahan has quit [Quit: tunahan]
fmartinsons[m] has quit [Ping timeout: 260 seconds]
thematrixpasswor has quit [Ping timeout: 252 seconds]
DannyHadley[m] has quit [Ping timeout: 252 seconds]
khem has quit [Ping timeout: 265 seconds]
lorenzog[m] has quit [Ping timeout: 265 seconds]
Ablu[m] has quit [Ping timeout: 246 seconds]
p34nuts[m] has quit [Ping timeout: 268 seconds]
gstinocher[m] has quit [Ping timeout: 248 seconds]
KareemZarka[m] has quit [Ping timeout: 248 seconds]
Entei[m] has quit [Ping timeout: 246 seconds]
tunahan has joined #yocto
ejoerns[m] has quit [Ping timeout: 264 seconds]
TRO[m] has quit [Ping timeout: 256 seconds]
mborzecki has quit [Ping timeout: 256 seconds]
barath has quit [Ping timeout: 256 seconds]
Saur[m] has quit [Ping timeout: 248 seconds]
Peter[m]12 has quit [Ping timeout: 248 seconds]
ericson2314 has quit [Ping timeout: 248 seconds]
tomzy_0[m] has quit [Ping timeout: 246 seconds]
cperon has quit [Ping timeout: 246 seconds]
patersonc[m] has quit [Ping timeout: 246 seconds]
perceval[m] has quit [Ping timeout: 260 seconds]
falk0n[m] has quit [Ping timeout: 260 seconds]
mrybczyn[m] has quit [Ping timeout: 268 seconds]
lrusak[m] has quit [Ping timeout: 246 seconds]
jandryuk[m] has quit [Ping timeout: 252 seconds]
kayterina[m] has quit [Ping timeout: 268 seconds]
ramax[m] has quit [Ping timeout: 260 seconds]
kiwi_29_[m] has quit [Ping timeout: 264 seconds]
AlexanderKrimm[m has quit [Ping timeout: 264 seconds]
agherzan has quit [Ping timeout: 260 seconds]
Niraj[m] has quit [Ping timeout: 268 seconds]
Salamandar has quit [Ping timeout: 248 seconds]
florian_kc has joined #yocto
<destmaster84>
on build my recipe I'm getting this error: requires libbz2.so.1.0()(64bit)
aak-rookie has quit [Quit: Client closed]
<destmaster84>
I've added the bz2zip in the "depends" but i still have this error
<qschulz>
destmaster84: you likely need bz2zip built for the host?
<JaMa>
bz2zip? you mean bzip2?
<qschulz>
so bz2zip-native in DEPENDS?
<destmaster84>
yes bz2zip
Max[m] has joined #yocto
<destmaster84>
my recipe requires it
<destmaster84>
libbz2.so.1.0()(64bit), but no providers found in RDEPENDS
<JaMa>
ok, for me libbz2.so.1.0 is provided by bzip2 and I have no bz2zip
<qschulz>
destmaster84: find the package that provides this library
lorenzog[m] has joined #yocto
<qschulz>
by using oe-pkgdata-util find-path '*libbz2.so*'
nothingtohide[m] has joined #yocto
perceval[m] has joined #yocto
fmartinsons[m] has joined #yocto
falk0n[m] has joined #yocto
azcraft has joined #yocto
thematrixpasswor has joined #yocto
<destmaster84>
libbz2 bzip2-dev bzip2-dbg ... bzip2 seems to be the right package
DasChaos[m] has joined #yocto
TRO[m] has joined #yocto
ramax[m] has joined #yocto
<qschulz>
destmaster84: no :)
p34nuts[m] has joined #yocto
<qschulz>
destmaster84: the package you want is libbz2
<qschulz>
I should actually have told you to use oe-pkgdata-util find-path '*libbz2.so.1.0*' and this would have likely returned libbz2 only
<qschulz>
bzip2 **may** be the **recipe** providing the libbz2 **package** though, that is absolutely possible
<qschulz>
but there;s a big difference between a recipe and a package
mrybczyn[m] has joined #yocto
<destmaster84>
clear
<JaMa>
destmaster84: it belongs to DEPENDS not RDEPENDS_${PN} (which might be also wrong syntax depending on which release you're using, newer need RDEPENDS:${PN})
<JaMa>
qschulz: he said that he is getting the error "on build", he is probably missing build time dependency not runtime package
<JaMa>
but with "depends" and non-existent "bz2zip" it's hard to guess what error he is actually asking us to resolve
<destmaster84>
and the error is" ERROR: Required build target 'abe-cm4-image' has no buildable providers.
<destmaster84>
Missing or unbuildable dependency chain was: ['abe-cm4-image', 'stereotool', 'libbz2']"
kayterina[m] has joined #yocto
d-s-e has joined #yocto
kiwi_29_[m] has joined #yocto
<JaMa>
not surprising
<qschulz>
JaMa: destmaster84: I think there's a misunderstanding here, what exactly is the error and when is it happening
<qschulz>
the one about the missing *libbz2.so.1.0*
<JaMa>
and why are you adding libbz2 in DEPENDS when 20 minutes ago I said bzip2?
KareemZarka[m] has joined #yocto
<qschulz>
JaMa: because I said they need libbz2 **package**, because I assumed we were talking about a missing RDEPENDS
<qschulz>
destmaster84: so if you could give a bit more info on the issue, we may give you better advice :)
<JaMa>
my crystal balls guessed that this error is part of build-deps QA error which really means DEPENDS
jandryuk[m] has joined #yocto
Max[m] has quit [Quit: Bridge terminating on SIGTERM]
khem has quit [Quit: Bridge terminating on SIGTERM]
patersonc[m] has quit [Quit: Bridge terminating on SIGTERM]
fmartinsons[m] has quit [Quit: Bridge terminating on SIGTERM]
perceval[m] has quit [Quit: Bridge terminating on SIGTERM]
nothingtohide[m] has quit [Quit: Bridge terminating on SIGTERM]
falk0n[m] has quit [Quit: Bridge terminating on SIGTERM]
lorenzog[m] has quit [Quit: Bridge terminating on SIGTERM]
thematrixpasswor has quit [Quit: Bridge terminating on SIGTERM]
TRO[m] has quit [Quit: Bridge terminating on SIGTERM]
DasChaos[m] has quit [Quit: Bridge terminating on SIGTERM]
p34nuts[m] has quit [Quit: Bridge terminating on SIGTERM]
ramax[m] has quit [Quit: Bridge terminating on SIGTERM]
mrybczyn[m] has quit [Quit: Bridge terminating on SIGTERM]
berton[m] has quit [Quit: Bridge terminating on SIGTERM]
cperon has quit [Quit: Bridge terminating on SIGTERM]
Ablu[m] has quit [Quit: Bridge terminating on SIGTERM]
DannyHadley[m] has quit [Quit: Bridge terminating on SIGTERM]
kayterina[m] has quit [Client Quit]
kiwi_29_[m] has quit [Client Quit]
KareemZarka[m] has quit [Client Quit]
jandryuk[m] has quit [Client Quit]
<JaMa>
if stereotool links with libbz2.so.1.0, then it needs bzip2 in DEPENDS even if stereotool is some prebuilt binary which built without it (until it failed in package_qa on build-deps QA issue)
<destmaster84>
JaMa, sorry I will try to be more clear about the error
<JaMa>
once added shlibs code in do_package will automatically add the runtime dependency as needed (before build-deps and rdeps QA is triggered)
khem has joined #yocto
<destmaster84>
Yes, the stereotool is a prebuilt binary... I've added the bzip2 to the DEPENDS
Salamandar has joined #yocto
patersonc[m] has joined #yocto
shoragan[m] has joined #yocto
barath has joined #yocto
esben[m] has joined #yocto
ericson2314 has joined #yocto
AlexanderKrimm[m has joined #yocto
TRO[m] has joined #yocto
Ablu[m] has joined #yocto
DasChaos[m] has joined #yocto
lrusak[m] has joined #yocto
mborzecki has joined #yocto
<destmaster84>
and this is the error:
<destmaster84>
ERROR: stereotool-1.0-r0 do_package_qa: QA Issue: /home/pi/waveart/stereotool/stereo_tool_gui_pi2 contained in package stereotool requires libbz2.so.1.0()(64bit), but no providers found in RDEPENDS:stereotool? [file-rdeps]
<destmaster84>
so, I suppose that I need to add something on do_package, right?
gstinocher[m] has joined #yocto
fmartinsons[m] has joined #yocto
Entei[m] has joined #yocto
<qschulz>
destmaster84: you need to add libbz2 **package** to RDEPENDS:stereotool (if your recipe is called stereotool, RDEPENDS:${PN} would be fine too)
Peter[m]1 has joined #yocto
ejoerns[m] has joined #yocto
phako[m] has joined #yocto
Saur[m] has joined #yocto
thematrixpasswor has joined #yocto
KareemZarka[m] has joined #yocto
DannyHadley[m] has joined #yocto
Niraj[m] has joined #yocto
perceval[m] has joined #yocto
jandryuk[m] has joined #yocto
ramax[m] has joined #yocto
cperon has joined #yocto
lorenzog[m] has joined #yocto
Max[m] has joined #yocto
kiwi_29_[m] has joined #yocto
kayterina[m] has joined #yocto
berton[m] has joined #yocto
nothingtohide[m] has joined #yocto
falk0n[m] has joined #yocto
tomzy_0[m] has joined #yocto
<JaMa>
destmaster84: it's still failing like this with bzip2 in DEPENDS? please share log.do_package shlibs should find libbz2.so.1.0 from bzip2 automatically (unless e.g. you're using 64bit /home/pi/waveart/stereotool/stereo_tool_gui_pi2 in 32bit OE build or something like that - in which case explicit RDEPENDS:${PN} won't help as well)
olani has joined #yocto
<qschulz>
JaMa: if they don't need bzip2 at compile time, there's no need to have it DEPENDS
<JaMa>
and as you confirmed it's prebuilt binary, then 'libbz2.so.1.0()(64bit)' might just not match what OE bzip2 rprovides (log.do_package will show you)
<destmaster84>
JaMa ...
<destmaster84>
NOTE: Couldn't find shared library provider for libbz2.so.1.0, used by files: /home/yoctocm4/rpi-build/tmp/work/cortexa72-poky-linux/stereotool/1.0-r0/packages-split/stereotool/home/pi/waveart/stereotool/stereo_tool_gui_pi2
<destmaster84>
I'm a bit confused... seems to be in 32bit OE instead of 64bit ... How I can check it?
<destmaster84>
Maybe I do a big mistake .... let me check
karl has quit [Quit: You think water moves fast? You should see ice.]
<JaMa>
qschulz: it doesn't have to be in DEPENDS when it's prebuilt binary, but it's better, because then shlibs code will add it automatically to RDEPENDS only as long as it's still needed (if the next prebuilt version no longer links with libbz2.so it just won't add the RDEPENDS)
<JaMa>
qschulz: while with explicit RDEPENDS in the recipe you would need to review log.do_package after each major update which nobody will ever do :)
<JaMa>
destmaster84: check with file /home/pi/waveart/stereotool/stereo_tool_gui_pi2 to see what this binary actually is
<destmaster84>
file stereo_tool_gui_pi2
<destmaster84>
stereo_tool_gui_pi2: ELF 64-bit LSB executable, ARM aarch64, version 1 (GNU/Linux), dynamically linked, interpreter /lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, stripped
<destmaster84>
other libraries in DEPENDS work fine ... the issue is only the libbz2
<JaMa>
and TMPDIR/pkgdata/*/runtime-reverse/libbz2-1 ?
<JaMa>
'bitbake-getvar -r stereotool DEPENDS' to double-check that you have bzip2 there
<JaMa>
mine has: FILERPROVIDES:/usr/lib/libbz2.so.1.0.8:libbz2: libbz2.so.1()(64bit) but not libbz2.so.1.0()(64bit) which is used in your prebuilt binary
kiwi_29_[m] has quit [Ping timeout: 240 seconds]
Niraj[m] has quit [Ping timeout: 240 seconds]
nothingtohide[m] has quit [Ping timeout: 252 seconds]
cperon has quit [Ping timeout: 252 seconds]
Saur[m] has quit [Ping timeout: 252 seconds]
ramax[m] has quit [Ping timeout: 246 seconds]
MathiasKoch[m] has quit [Ping timeout: 246 seconds]
patersonc[m] has quit [Ping timeout: 246 seconds]
DannyHadley[m] has quit [Ping timeout: 248 seconds]
mrybczyn[m] has quit [Ping timeout: 248 seconds]
Entei[m] has quit [Ping timeout: 248 seconds]
esben[m] has quit [Ping timeout: 248 seconds]
KareemZarka[m] has quit [Ping timeout: 246 seconds]
Salamandar has quit [Ping timeout: 246 seconds]
shoragan[m] has quit [Ping timeout: 246 seconds]
TRO[m] has quit [Ping timeout: 246 seconds]
ericson2314 has quit [Ping timeout: 264 seconds]
Peter[m]1 has quit [Ping timeout: 265 seconds]
Ablu[m] has quit [Ping timeout: 265 seconds]
DasChaos[m] has quit [Ping timeout: 265 seconds]
barath has quit [Ping timeout: 265 seconds]
tomzy_0[m] has quit [Ping timeout: 260 seconds]
perceval[m] has quit [Ping timeout: 260 seconds]
phako[m] has quit [Ping timeout: 260 seconds]
ejoerns[m] has quit [Ping timeout: 260 seconds]
fmartinsons[m] has quit [Ping timeout: 260 seconds]
agherzan has quit [Ping timeout: 260 seconds]
mborzecki has quit [Ping timeout: 260 seconds]
gstinocher[m] has quit [Ping timeout: 260 seconds]
AlexanderKrimm[m has quit [Ping timeout: 260 seconds]
lrusak[m] has quit [Ping timeout: 260 seconds]
lorenzog[m] has quit [Ping timeout: 265 seconds]
thematrixpasswor has quit [Ping timeout: 265 seconds]
jandryuk[m] has quit [Ping timeout: 265 seconds]
Max[m] has quit [Ping timeout: 265 seconds]
khem has quit [Ping timeout: 265 seconds]
berton[m] has quit [Ping timeout: 256 seconds]
falk0n[m] has quit [Ping timeout: 256 seconds]
p34nuts[m] has quit [Ping timeout: 256 seconds]
kayterina[m] has quit [Ping timeout: 264 seconds]
<destmaster84>
JaMa exacly!
<destmaster84>
this is in the libbz2-1:
<destmaster84>
RPROVIDES:libbz2: libbz2 (=1.0.8)
<destmaster84>
I need to add a bbappend for the libbz2.so.1.0()(64bit) ?? What is the best workaround to solve it?
ericson2314 has joined #yocto
<RP>
JaMa: there was someone else running into selftest issues on the list so I think there are some fixes needed somewhere :/
agherzan has joined #yocto
shoragan[m] has joined #yocto
seninha has joined #yocto
<JaMa>
destmaster84: FILERPROVIDES is the important line for this not RPROVIDES
<JaMa>
RP: you mean issues caused by my changes? I've noticed couple threads related to selftest but none of them looked related to my changes nor something I was already debugging as well (I would have replied if I had something to add)
<RP>
JaMa: no, not your changes. Someone running into devtool failing out the box for them
<RP>
JaMa: I just wondered if you had a fix for their issue
<JaMa>
destmaster84: if you can rebuild the binary then rebuilt it against libbz2.so.1, if you cannot you can alter the binary as long as you verify that this libbz2 is ABI compatible with whatever version was used to build stereotool
<JaMa>
"oe-selftest for devtool failed
<JaMa>
" thread from today?
<RP>
JaMa: yes
<JaMa>
I have seen a lot of strange failures but shadow-native:do_install wasn't one of them (AFAIR)
<JaMa>
if he provides more info as requested by Alex, then it might ring a bell, but right now it doesn't
<JerryM>
if there hasn't been a response on the mailing list what would be the best course of action? wait a bit longer (what would be consider appropriate?). reply or repost or..?
AlexanderKrimm[m has joined #yocto
Max[m] has joined #yocto
ejoerns[m] has joined #yocto
SmoothBrain has joined #yocto
phako[m] has joined #yocto
<SmoothBrain>
Ola,
<SmoothBrain>
I like the concept in IMAGE_FEATURES[validitems] where it serves as indirect documentation is the layer.conf.
<SmoothBrain>
Is there a is it by design that DISTRO_FEATURES equivalent?
<JaMa>
JerryM: first rebase to make sure it wasn't merged already (replies are not send unless there are issues in the change)
<JaMa>
JerryM: if it wasn't I would check master-next (if it's there than it's still on the radar of someone) and if it isn't even in master-next and it's lets say 2 weeks or more, then I would send ping
SmoothBrain has quit [Quit: Client closed]
<JerryM>
JaMa in this case it wasn't a patch but a general question and a reply to an old thread with a patch I seemingly needed but that didn't seem to have had an update after some feedback
<JerryM>
though the general gist still applies I suppose
tunahan has quit [Quit: tunahan]
tunahan has joined #yocto
nemik has quit [Ping timeout: 240 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 265 seconds]
nemik has joined #yocto
<qschulz>
JerryM: if it wasn't sent following the contributions guidelines, it was probably just missed. Would you be able to send the patch properly to the mailing list?
<JerryM>
qschulz I can update the patch most likely, but it wasn't originally mine so I just fix it and add my own signed off?
<qschulz>
JerryM: yes, keep the author in the From field of the git commit (it should be the first line in the mail body if git-send-email is setup properly) and add your Signed-off-by after the author's
destmaster84 has quit [Quit: Client closed]
<JerryM>
qschulz I will have a look at it thank you
<RP>
JerryM: was this the ldconfig one?
<JerryM>
RP yes actually
<RP>
JerryM: I did flag that to look into, we probably can put it in for testing
<JerryM>
RP alright do you still want me to update/fix the patch?
<RP>
JerryM: what fixes are needed?
<JerryM>
I think the issue was with the From field according to the replies in the topic
<RP>
JerryM: ok, I can fix that. I've pulled it into master-next for testing
<RP>
JerryM: the reason it hadn't been acted upon was the discussion about whether it was correct or not. I think your feedback answers that
davidinux has quit [Ping timeout: 260 seconds]
davidinux has joined #yocto
<JerryM>
RP alright thank you. I'm still trying to get used to these mailing lists and figuring out what one should or should not do
tunahan has quit [Quit: tunahan]
tunahan has joined #yocto
d-s-e has joined #yocto
kscherer has joined #yocto
<RP>
JerryM: things do get overlooked so please do remind where something is falling through the cracks
xmn has joined #yocto
xmn has quit [Client Quit]
xmn has joined #yocto
<d-s-e>
Is there a recommended way how to add Go applications? I see a lot of discussion but not really some consensus.
<JerryM>
RP I will keep that in mind, the two weeks mentioned previously sound like a good indication
_azcraft has joined #yocto
azcraft has quit [Ping timeout: 265 seconds]
vladest has quit [Ping timeout: 250 seconds]
rob_w has quit [Quit: Leaving]
<JerryM>
while I'm here I tried to use systemd v250 on dunfell but needed a patch from master/kirkstone which wouldn't usually be needed for dunfell would this be okay to backport regardless?
<RP>
JerryM: it depends on the patch but that isn't what we'd usually accept
<RP>
JerryM: it could be useful to post about it, see where there is high demand for it
<JerryM>
RP that's what I figured, though as far as I can tell the patch does not interfere with dunfell
<JerryM>
@RP
<JerryM>
RP should I "post" with the patch in that case or just start a topic as I wasn't really sure if sending in a patch while asking for feedback would be okay
<RP>
JerryM: right, it is meant to be a stable branch and changes add risk so that is why we'd be hesitant
<RP>
JerryM: posting a patch and asking for feedback should be fine
<JerryM>
RP should I tag that specifically with something like [RFC] or wouldn't that really matter?
<RP>
JerryM: RFC would seem appropriate
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
<JerryM>
RP okay thank you
florian has joined #yocto
florian has quit [Ping timeout: 248 seconds]
invalidopcode1 has quit [Remote host closed the connection]
invalidopcode1 has joined #yocto
sakoman has joined #yocto
<khem>
guest7090: OK this is on rpi4 ? if so can you send a patch where these options are clubbed into a rtc.cfg and apply this via SRC_URI in linux-raspberrypi
Guest79 has joined #yocto
brazuca has joined #yocto
florian has joined #yocto
<JerryM>
another question about backporting, normally I can test patches on dunfell, but if I packport and it is not available on e.g. kirkstone should I send it in there too even if I can't test it?
diego_r has quit [Ping timeout: 252 seconds]
sugarbeet has quit [Ping timeout: 260 seconds]
thomasd13 has quit [Ping timeout: 260 seconds]
Guest79 has quit [Quit: Client closed]
<khem>
I think that will be good, with a note about testing, it will atleast alert the maintainers and users of those releases
nemik has quit [Ping timeout: 248 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 265 seconds]
jtoomey has joined #yocto
nemik has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
<zelgomer>
do_unpack:append() { <some shell script here> } this fails with invalid syntax, and when i look at the generated run.do_unpack, it looks like do_unpack() is a python function and it just blindly slapped my shell code onto the end of it. is this how this is supposed to work? i never realized before, do i have to know in what language a function was defined to be able to append or prepend to it? i thought
<zelgomer>
bitbake would know to do the right thing to switch between the two languages
frieder has quit [Remote host closed the connection]
<zelgomer>
thanks, i could do that or i could just write my :append in python. my question is more a surprise that this doesn't work the way i expected. it means that if i ever write do_foo:append()s all over my layer, and then some day down the road the implementation of do_foo changes from shell to python, then it breaks all of my recipes
<qschulz>
zelgomer: use postfuncs or insert a task between two other tasks, but yes a blanket layer-wide do_foo:append() isn't very robust :)
<ptsneves>
Hey. What does one do when a mirror fetch running wget continues downloading a file that failed the previous mirror fetching, leading to a corrupt download file? It happens that the first mirror offers a corrupt file that should be completely discarded, and not assumed to be a partial file like the default case.
dgriego has joined #yocto
seninha has joined #yocto
<barath>
anyone had issues with SDKs + shadow.inc + syslog being disabled for nativesdk recipes? that plus the login.defs file used errors out my opkg-based SDK due to SYSLOG_SU_ENAB etc being unknown items...
<barath>
not sure if it's a bug or if I'm at fault somehow. it works when I comment out the patches disabling syslog for native shadow.inc
zpfvo has quit [Remote host closed the connection]
amsobr has joined #yocto
ptsneves has quit [Ping timeout: 252 seconds]
goliath has joined #yocto
florian_kc has quit [Ping timeout: 255 seconds]
florian has quit [Ping timeout: 260 seconds]
rfuentess has quit [Remote host closed the connection]
JerryM has quit [Quit: Client closed]
invalidopcode1 has quit [Remote host closed the connection]
invalidopcode1 has joined #yocto
leon-anavi has quit [Quit: Leaving]
Minvera has joined #yocto
brazuca has joined #yocto
seninha has quit [Quit: Leaving]
seninha has joined #yocto
tangofoxtrot has quit [Ping timeout: 268 seconds]
tangofoxtrot has joined #yocto
vladest has joined #yocto
tangofoxtrot has quit [Ping timeout: 260 seconds]
tangofoxtrot has joined #yocto
florian has joined #yocto
alessioigor has quit [Quit: alessioigor]
starblue has joined #yocto
brazuca55 has joined #yocto
brazuca55 has quit [Client Quit]
brazuca23 has joined #yocto
brazuca2 has joined #yocto
brazuca has quit [Ping timeout: 260 seconds]
brazuca23 has quit [Ping timeout: 260 seconds]
florian has quit [Ping timeout: 255 seconds]
Haxxa has quit [Quit: Haxxa flies away.]
Haxxa has joined #yocto
brazuca2 is now known as brazuca
mvlad has quit [Remote host closed the connection]
rsalveti has quit [Quit: Connection closed for inactivity]
<paulg>
well, in a way that is good. They seem to value the testing exposure (and really how many people can rock up and say "we build the world, and here is what we see.")
<RP>
paulg: right, I'm trying to show we can offer something to the wider ecosystem
<paulg>
hopefully they get it and it won't take a brick to the head.
rsalveti has joined #yocto
* paulg
totally should have gone into marketing...
Minvera has quit [Remote host closed the connection]
<ernstp>
python3-jinja2-3.1.2-r0 do_python_rdep: QA: rdepends on python3-markupsafe but they are not set as dependencies
<ernstp>
python3-requests-2.28.2-r0 do_python_rdep: QA: rdepends on python3-urllib3 python3-charset-normalizer python3-certifi python3-idna but they are not set as dependencies.
seninha has quit [Quit: Leaving]
brazuca has joined #yocto
brazuca has quit [Quit: Client closed]
goliath has quit [Quit: SIGSEGV]
tunahan has quit [Quit: tunahan]
tunahan has joined #yocto
tunahan has quit [Quit: tunahan]
tunahan has joined #yocto
<JaMa>
paulg: VW management also looks like good career, you won't build the world, but at least you would be able to buy more significant portion of it :)