<JaMa>
there is still surprising number of people sometimes complaining about "broken" syntax
<RP>
JaMa: it suggests people don't take the stable branch updates :(
* RP
is wondering how invasive/progressive we should be with changes in master
<JaMa>
RP: yes or expect their evil-bsp provider to release updated "build" for them
<LetoThe2nd>
i actually guess that its more likely caused by outdated information and tutorials. YP/OE are and have always been kind of moving targets, and many resources are never updated. on a side note, this is exactly what i am just working on.
<JaMa>
it would be much easier with time machine (to add explanation in old versions people will still use when some incompatible change is implemented) or being able to plan these incompatible changes couple releases in advance (so that bitbake can already warn if it notices new syntax which isn't yet supported) :)
<JaMa>
e.g. the variable renames work perfectly when you need to update them for new OE, but if you happen to switch your build to some older version which doesn't recognize the new variables yet, then it's easy to miss (happened to me last week when bisecting some issue in the same build directory and the same local.con)
mckoan_ has joined #yocto
mckoan has quit [Ping timeout: 256 seconds]
mckoan_ is now known as mckoan|away
mckoan|away is now known as mckoan
<RP>
JaMa: I did propose adding BB_RENAMED_VAR support to older bitbake's so we could detect use of the new names
<RP>
JaMa: wouldn't be perfect but would help the maintainers who probably stay up to date on bitbake
* RP
has sent an arch list discussion about the unpack problem
frieder has quit [Read error: Connection reset by peer]
frieder has joined #yocto
Schlumpf has quit [Quit: Ping timeout (120 seconds)]
seninha has joined #yocto
<LetoThe2nd>
RP: is this related to the directory wipe problem that Kristian asked about?
Juanosorio94 has joined #yocto
GillesM has joined #yocto
GillesM has quit [Remote host closed the connection]
frieder has quit [Read error: Connection reset by peer]
frieder_ has joined #yocto
frieder_ has quit [Read error: Connection reset by peer]
frieder has joined #yocto
<RP>
LetoThe2nd: no, that is something else :(
Schlumpf has joined #yocto
<RP>
LetoThe2nd: fixing these other issues might help make that other code more robust though
pjoh has joined #yocto
pjoh has quit [Client Quit]
pjoh has joined #yocto
olani- has joined #yocto
Tyaku has joined #yocto
olani- has quit [Remote host closed the connection]
Schlumpf has quit [Quit: Client closed]
wCPO has quit [Quit: Ping timeout (120 seconds)]
nemik has quit [Ping timeout: 240 seconds]
nemik has joined #yocto
wCPO has joined #yocto
nemik has quit [Ping timeout: 240 seconds]
nemik has joined #yocto
schtobia has joined #yocto
olani has quit [Remote host closed the connection]
olani has joined #yocto
davidinux has quit [Ping timeout: 244 seconds]
<LetoThe2nd>
RP: kay
davidinux has joined #yocto
acki_ has joined #yocto
hcg has joined #yocto
tre has quit [Remote host closed the connection]
nemik has quit [Ping timeout: 255 seconds]
nemik has joined #yocto
jmiehe has joined #yocto
nemik has quit [Ping timeout: 255 seconds]
nemik has joined #yocto
prabhakarlad has quit [Quit: Client closed]
<LetoThe2nd>
whats the plans for honister? technically support ends... tomorrow.
Juanosorio94 has quit [Quit: Client closed]
<qschulz>
LetoThe2nd: we'd need to ask Anuj, there are 18 commits on top of 3.4.4 tag and they sent a 12-patch series last night
<LetoThe2nd>
qschulz: yeah, i was just wondering because i'm finally revisiting our documentation.
<qschulz>
LetoThe2nd: I'd say just treat it as EOL
<qschulz>
I would assume it'll get at best one more release
<qschulz>
but it could also very much go how thud went, 2.6.4 + 60 patches to date
<qschulz>
no more release
<LetoThe2nd>
qschulz: gatesgarth is similar
ptsneves has quit [Quit: Client closed]
<RP>
LetoThe2nd: one more point release
prabhakarlad has joined #yocto
<LetoThe2nd>
RP: kaythanks.
sakoman has joined #yocto
hcg has quit [Quit: Client closed]
ptsneves has joined #yocto
pjoh has quit [Quit: Client closed]
<dacav>
Hi there. I have a situation with a shell recipe using a `trap`, which is not executed when the install script works.
<dacav>
could it be that it is overwritten by `trap bb_exit_handler 0` ?
<dacav>
if so, is using a subshell the right way to go?
ptsneves has quit [Ping timeout: 252 seconds]
goliath has quit [Quit: SIGSEGV]
nemik has quit [Ping timeout: 276 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 246 seconds]
nemik has joined #yocto
frieder has quit [Ping timeout: 250 seconds]
prabhakarlad has quit [Quit: Client closed]
frieder has joined #yocto
mckoan is now known as mckoan|away
marex has quit [Ping timeout: 255 seconds]
marex has joined #yocto
prabhakarlad has joined #yocto
bps3 has quit [Ping timeout: 276 seconds]
Tyaku has quit [Quit: Lost terminal]
frieder has quit [Remote host closed the connection]
<JaMa>
RP: thanks for joining that glibc bug ticket
nemik has quit [Ping timeout: 258 seconds]
nemik has joined #yocto
Wouter0100 has quit [Remote host closed the connection]
Wouter0100 has joined #yocto
dz1 has joined #yocto
dz1 has quit [Client Quit]
dz1 has joined #yocto
nemik has quit [Ping timeout: 244 seconds]
nemik has joined #yocto
mvlad has quit [Remote host closed the connection]
<jaskij[m]>
RP: about that fsck error, I noticed the second to last element in the thread stack is somewhere in `libpthread`. I've had a different run-in with this `lxcfs` bug: https://github.com/lxc/lxcfs/issues/469 - it is conceivable that `fsck.ext4` is dividing by the number of CPUs, which would return 0 because of that. I have a different build environment which is under `kvm`, not `lxc`, I'll check if the issue persists using the same commits there.
<jaskij[m]>
(as an aside: does it matter that `fsck.ext4` uses host `libpthread`?)
acki_ has joined #yocto
seninha has joined #yocto
Wouter0100 has quit [Read error: Connection reset by peer]
Wouter0100 has joined #yocto
jmiehe has quit [Quit: jmiehe]
goliath has quit [Quit: SIGSEGV]
nemik has quit [Ping timeout: 246 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 240 seconds]
nemik has joined #yocto
leon-anavi has quit [Quit: Leaving]
fennec has quit [Quit: WeeChat 3.5]
Net147 has quit [Ping timeout: 246 seconds]
Net147 has joined #yocto
Net147 has quit [Changing host]
Net147 has joined #yocto
<RP>
JaMa: not sure I'm helping :/
<RP>
jaskij[m]: hmm, we should probably let the e2fsprogs people know that can return zero :/
<jaskij[m]>
RP: True, although I'm hesitant since it's an lxcfs bug which is already fixed and just waiting for the next release. I'm not sure if they would be willing to merge a workaround in this case.
<jaskij[m]>
Also: I'm not familiar with e2fsprogs or wix, how hard would it be to get out the command used by wix in a build? So that I can make a repro smaller than requiring usage of Yocto.
<jaskij[m]>
RP: if you can help me with the repro, I can have it written up tomorrow evening. I was about to go to sleep when I got your ping.
otavio has quit [Remote host closed the connection]
florian has quit [Remote host closed the connection]