This is an edit for the lighttpd ebuild that adds ppc-macos to IUSE and uses that to conditionally set the lighttpd user's shell to /usr/bin/false instead of /bin/false. NOTE: the build still fails, because of some bug in the build system I can't figure out. This just fixes the (easy) problem of /bin/false not existing. Reproducible: Always Steps to Reproduce: 1. emerge lighttpd Actual Results: emerge died saying /bin/false doesn't exist Expected Results: /usr/bin/false is used instead
Created attachment 52523 [details] the new ebuild This is the new ebuild that conditionally sets lighttpd's shell to /usr/bin/false
I asked around and it appears that in debian, mandriva, as well as redhat, the false that is in coreutils gets installed to /bin/false. I'd be curious why/how this isn't the case in gentoo.
OK, I take that back. I've checked at least 6 other gentoo boxen and they all have the sym link /usr/bin/false -> /bin/false. So unless I'm mistaken, I think you need to check to make sure your install isn't broken. Try re-emerging coreutils for starters. voidengineer
on OSX /bin/false doesn't exist, and the appropriate file is in /usr/bin/false. However, the enewuser and enewgroup scripts handle this transparently, to use /bin/false on Linux and /usr/bin/false on ppc-macos. Since ppc-macos is a keyword flag it should not be in IUSE. It seems to me that you should simply call enewuser like this: enewuser lighttpd -1 -1 "${LIGHTTPD_DIR}" lighttpd because this way automatically the /bin/false (or equivalent) shell is chosen for Linux, Darwin and BSD at the moment. Maybe more are added in the future, then the ebuild is already compliant.
This enewuser issue has already been fixed as of lighttpd-1.3.13. a libtoolize is being hardcoded into some perl script, that should be changed to glibtoolize and glibtool. Changing this bug's summary and stuff to beter reflect the actual problem.
this package has an impressive list of USE flags: [ebuild N ] www-servers/lighttpd-1.4.1-r1 (-doc) -fam -gdbm -ipv6 -ldap -lua (-mysql) -pcre -php -ssl -test -webdav -xattr 741 kB [1] fam - depends on app-admin/fam (not keyworded) gbdm - depends on sys-libs/gdm (keyworded) ipv6 - [no dependencies] ldap - depends on >=net-nds/openldap-2.1.26 (not keyworded) lua - depends on lua (keyworded) pcre - depends on libpcre (keyworded) php - depends on >=dev-php/php-cgi-4.3.0 (not keyworded) ssl - [no dependencies] test - depends on perl-core/Test-Harness (not keyworded) webdav - depends on dev-db/sqlite (keyworded) xattr - depends on sys-apps/attr (not keyworded) I did not find bugs for the not keyworded packages.
1.3.11 isn't even in portage anymore. Is this still a problem with the current versions? Can anybody provide output from the failing emerge? (and emerge --info)
This problem is outdated, as the package isn't there any more, neither the arch the problem was reported on.
