| Summary: | Updating busybox leaves the target on a broken state | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Ricardo Ribalda <ricardo.ribalda> | ||||||||
| Component: | core | Assignee: | Aníbal Limón <anibal.limon> | ||||||||
| Status: | RESOLVED FIXED | QA Contact: | |||||||||
| Severity: | major | ||||||||||
| Priority: | Medium | CC: | meta.mr.watcher, meta.watcher | ||||||||
| Version: | 1.6.1 | ||||||||||
| Target Milestone: | 1.6.2 | ||||||||||
| Hardware: | Other | ||||||||||
| OS: | x86_64 | ||||||||||
| Whiteboard: | |||||||||||
| OS type for building Yocto: | --- | Type of Regression: | --- | ||||||||
| Verified: | Documentation change: | Don't know | |||||||||
| Attachments: |
|
||||||||||
Can you publish your local.conf settings? Created attachment 2150 [details]
local.conf
Created attachment 2151 [details]
installed packages
There you are, I have also added the list of installed packages. I isolated the problem, A workaround exist for handle this situation into prerm recipe for busybox, it creates a symlink into /tmp/busybox-$PSEUDORANDOM for utilities that need and then export to PATH env var. But in debian don't work because all scripts are exec in separated instance. Done at, https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=c0b0f695f537541cf3247afd8bfd19e471ed81d7 If you want I can give it a try next week (I am at the ELCE now) and report the results. Thanks! Sure, You need to patch the two packages from 1.6.0 and 1.6.1. I applied the patch without problems in master and 1.6.x. Best regards. |
Created attachment 2144 [details] apt-get update output After updating my repo from 1.6.0. to 1.6.1 I did on the target: apt-get update apt-get upgrade While updating the busybox package the system was left unusable (extract of the update) Preparing to unpack .../busybox_1.22.1-r0.2_amd64.deb ... Unpacking busybox (1.22.1-r0.2) over (1.22.1-r0.1) ... update-alternatives: removing //bin/sed as no more alternatives exist for it /usr/bin/update-alternatives: line 186: sed: not found /usr/bin/update-alternatives: line 186: sed: not found Attached you will find the whole log of the upgrade. Thanks!