**** BEGIN LOGGING AT Tue Apr 23 02:59:57 2019 **** BEGIN LOGGING AT Tue Apr 23 07:43:30 2019 Apr 23 18:58:27 Hello folks; we are facing an interesting issue with a customer. They have a product we are updating from sumo (from some time after its release) to latest sumo (with security fixes). It seems a backport made for busybox has broken our environment. OE-Core:d0555e89514f2641387ef061f9ffcd1c8ced008c is a "fix" for CVE-2011-5325 wich JaMa did but it seems busybox get fully broken after it. rburton RP are you Apr 23 18:58:33 aware of this? Apr 23 19:25:26 otavio_: not sure what you mean by broken but I haven't noticed a problem. Apr 23 20:41:46 otavio_: Hmmm sec Apr 23 20:42:08 otavio_: Yeah, I thought we already undid that in sumo Apr 23 20:42:16 otavio_: That broke me too :( Apr 23 20:43:03 otavio_: Er, wait.. Apr 23 20:44:32 otavio_: It was b1c25a68bfcf8309557867eb533b50ce489bc06e that broke everything for me and then not-doing that is what brings things back to working again Apr 23 20:44:50 otavio_: What breakage do you see exactly? Apr 23 21:19:21 otavio_: no, I'm not. You might want to ping armin Apr 23 22:03:14 Tartarus: it fails to populate all alternatives symlinks Apr 23 22:03:41 reverting the commit, solves it for us Apr 23 22:11:56 otavio_: Are you working with artifacts from before that commit too? Or clean build? Apr 23 22:13:40 otavio_: Also, can you test just moving to 1.28.2 ? Apr 23 22:14:15 Reverting that change isn't an option imho, it blows up other cases (we ended up just switching to real tar, but we had no symlinks being made basically). Apr 23 23:50:32 Tartarus: we can try bumping it tomorrow, sure **** ENDING LOGGING AT Wed Apr 24 02:59:57 2019