Summary: | portmap hangs due to non-existent default user | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Michael Wardle <michael> |
Component: | New packages | Assignee: | Network Filesystems <net-fs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | major | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Michael Wardle
2004-12-29 19:03:46 UTC
the portmap ebuild adds the rpc user Ironically it's applying Red Hat's rpc_user patch that inadvertently causes this nasty behavior in the first place! I currently have portmap-5b-r8 yet I had to manually add the rpc user. My system started out at Gentoo 2004.0 or 2004.1. Why would I not have the rpc user if my currently installed version should create the rpc user? Does the pkg_setup routine only get called on the first installation of a package? yes you're also running an outdated portmap I've just sync'd with 2004.3 and am performing an update world; -r9 is coming soon. :-) If upgrading the package is insufficient to create the required user, then lots of other people are going to be bitten by the same bug. :-( Is it possible to make this an action on every install (including upgrades)? i interpreted your question wrong pkg_setup is run everytime that ebuild is emerged In this case, it's a mystery why the "rpc" user wasn't created when I upgraded to -r8 some months ago. Perhaps enewuser has only been recently made available and I had an older version of portage (or its libraries). I notice a version of enewuser in eclass/eutils.eclass you wrote (found by Googling), but I'm not too sure how this gets sucked into portage and thus the ebuilds. |