Bug 6768 - Updating busybox leaves the target on a broken state
Summary: Updating busybox leaves the target on a broken state
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: 1.6.1
Hardware: Other x86_64
: Medium major
Target Milestone: 1.6.2
Assignee: Aníbal Limón
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2014-09-26 10:36 UTC by Ricardo Ribalda
Modified: 2014-10-13 19:10 UTC (History)
2 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know

Attachments
apt-get update output (292.60 KB, text/x-log)
2014-09-26 10:36 UTC, Ricardo Ribalda 		no flags Details
local.conf (10.76 KB, application/octet-stream)
2014-10-01 05:51 UTC, Ricardo Ribalda 		no flags Details
installed packages (25.96 KB, text/plain)
2014-10-01 05:52 UTC, Ricardo Ribalda 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ricardo Ribalda 2014-09-26 10:36:11 UTC 
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!
Comment 1 Aníbal Limón 2014-09-30 22:38:46 UTC 
Can you publish your local.conf settings?
Comment 2 Ricardo Ribalda 2014-10-01 05:51:35 UTC 
Created attachment 2150 [details]
local.conf
Comment 3 Ricardo Ribalda 2014-10-01 05:52:15 UTC 
Created attachment 2151 [details]
installed packages
Comment 4 Ricardo Ribalda 2014-10-01 05:53:02 UTC 
There you are, I have also added the list of installed packages.
Comment 5 Aníbal Limón 2014-10-06 19:25:32 UTC 
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.
Comment 7 Ricardo Ribalda 2014-10-13 19:08:32 UTC 
If you want I can give it a try next week (I am at the ELCE now) and report the results.

Thanks!
Comment 8 Aníbal Limón 2014-10-13 19:10:41 UTC 
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.