As far as I can tell, after updating to the new busybox portage broke. It appears busybox replaces the find command and patch command with commands that just don't work with portage. So after trying to emerge anything, I will usually get an error that says the patch didn't apply. Also, at the end it would say something along the lines of couldn't scan /etc /var/qmail ... I just installed the patch ebuild and copied its binary over the busybox's symlink, and that fixed the patch problem, but the find problem still persists especially with dispatch-conf or etc-update. Is my system the only one effected by this? Reproducible: Always Steps to Reproduce: 1. Update busybox with createsymlinks use flag 2. Try to emerge anything Actual Results: See Details Expected Results: gentoo not breaking
Also it replaces the ar command which broke emerge also. Arrgh. I am removing as many of these symlinks as I can.
This bug is sorta invalid. And your in for a world of hurting if you had that USE flag enabled (remove it). The make-symlinks is intended for use only with making binary pkgs mainly when your cross compiling. The feature was added by dragonheart some time ago if I recall correctly. dragonheart? Anyway we can QA this and ensure nobody else makes the same mistake?
Sure, I'll add it to my list.
well, luckily ar, find, and patch were all installed in /usr/bin so I just removed the relevant busybox symlinks. Is there a quicker way of restoring functionality to this crippled box. By the way it also replaced ifup/down so I'm not rebooting this anytime soon. I'm guessing unemerging busybox would leave my system lacking some critical system tools? Know of how I can have my system reemerge packages that produce the files busybox replaced?
thank god for awk. I removed all the symlinks that had /usr/bin /usr/sbin "alternative binaries". Do you guys see anything in this list that gentoo depends upon for proper operation: /bin/addgroup /bin/adduser /bin/arping /bin/ash /bin/busybox /bin/delgroup /bin/deluser /bin/dos2unix /bin/dpkg /bin/dpkg-deb /bin/dumpkmap /bin/dumpleases /bin/fdflush /bin/ftpget /bin/ftpput /bin/hush /bin/ip /bin/ipcalc /bin/iplink /bin/iproute /bin/iptunnel /bin/lash /bin/length /bin/loadfont /bin/msh /bin/mt /bin/nc /bin/nslookup /bin/pipe_progress /bin/realpath /bin/rpm /bin/rpm2cpio /bin/rx /bin/tftp /bin/time /bin/traceroute /bin/unix2dos /bin/usleep /bin/vlock /sbin/adjtimex /sbin/chroot /sbin/crond /sbin/fbset /sbin/freeramdisk /sbin/getty /sbin/httpd /sbin/ifdown /sbin/ifup /sbin/inetd /sbin/klogd /sbin/loadkmap /sbin/logread /sbin/makedevs /sbin/rdate /sbin/syslogd /sbin/udhcpc /sbin/udhcpd /sbin/vconfig /sbin/watchdog
qpkg -l busybox will tell you what busybox was installed. emerge -C busybox will remove everying installed if you do something like: echo "{paste file list here}" | xargs -n 1 qpkg -f -v you will get a list of packages needed to emerge to reget the files busybox overwrote.
Just be carefull when doing so. What could maybe happen is when you overwrite the symlink (say modutils) it could overwrite the /bin/busybox and then when something attempts to run (sed) it could in turn run insmod/modprobe etc.. Good luck recovering.
yep remove symlinks and the remerge. I have put some save guards in.
Is this still the case, 6 years later? To me it makes sense that for those commands (find and others) that portage relies on the GNU versions of, the busybox ebuild doesn't put the symlink in place. Anyway, this is interesting for me, I just wanted to add myself to the CC list.
so dont use the USE flag
*** Bug 703936 has been marked as a duplicate of this bug. ***