On 03/01/2016 11:43 PM, Philip Tricca wrote: > On 03/01/2016 02:58 PM, Alejandro del Castillo wrote: >> I first started looking at busybox postinst (modified on meta-selinux) since >> I >> am getting errors during "opkg upgrade buysbox". The errors that I am getting >> are of the form: >> >> update-alternatives: Error: not linking /bin/gunzip to >> /usr/lib/busybox/bin/gunzip since /bin/gunzip exists and is not a link >> >> Which only happen for utilities that don't have any alternative installed >> after >> removing busybox, hence no symlink. Utilities that do have an alternative >> installed are correctly processed, for example: >> >> update-alternatives: Linking /usr/bin/ar to /usr/bin/x86_64-nilrt-linux-ar >> >> The root problem is that meta-selinux on commit >> 521ca9c9cf370840e9f8c808a7955aa5da7c356e replaced the temporary symlink >> creation >> on postinst with sh wrappers, which breaks update-alternatives when it tries >> to >> update symlinks (which are now sh wrappers). >> >> Is there a reason why the postinst needs to be different on the selinux >> version >> of busybox? If the postinst is just creating temporary symlinks which will go >> away once the update-alternatives block later on the script runs, do we need >> the >> sh wrappers? > > Thanks for the additional context Alejandro. I don't have enough history > yet to pull answers to stuff like this out at will though. Hopefully > someone with the right background will chime in. Either way I'll circle > back once the easy stuff in the backlog is done and we'll try to sort > something out.
Sounds good, I hope someone can provide background since it looks to me like the postinst is wrong, but I don't have historic context. Let me know if I can help in any way. -- Cheers, Alejandro -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
