The changes made on May, 18th causes some trouble: 18 May 2007; Roy Marples <uberlord@gentoo.org> files/atieventsd.init: Fix the init script to work on baselayout-2 It looks like this file was saved using windows linebreaks. When running "/etc/init.d/atieventsd foobar" the output looks like: -su: /etc/init.d/atieventsd: /sbin/runscript^M: bad interpreter: File or command not found After running a "dos2unix /etc/init.d/atieventsd" all worked as expected. Please fix this ASAP, because it makes the whole init-system going mad. A lot of initscripts stop working, because the generated dependency file (/var/lib/init.d/depcache) doesn't work because of the windows linebreaks. Maybe portage should be more tolerant concerning this, maybe an autodetection of such linebreaks could be implemented to correct the depcache file automagically and display a warning about such hazardous files. Regards, Elias P. Reproducible: Always Steps to Reproduce: 1. Sync the portage tree to have the changes made on May, 18th in it 2. (Re-)Install x11-drivers/ati-drivers 3. Reboot your system or try to restart /etc/init.d/atieventsd
Eep. Should be fixed now, thanks for reporting. Please verify this is actually fixed on the rsync mirrors about an hour from now and close if it is actually fixed (I don't feel comfortable closing this since I'm pretty sure those line endings were correct on uberlord's box when he committed this, must have broken somewhere between testing and the cvs server...)
Seems to be o.k. now. Thx for fixing it that fast!
*** Bug 179117 has been marked as a duplicate of this bug. ***
*** Bug 179797 has been marked as a duplicate of this bug. ***
