ntp ebuild has default ntpd config file which sets ntpd to run as ntp:ntp, yet the ebuild does not create this user or group. Reproducible: Always Steps to Reproduce: 1. 2. 3.
yes, it does if you emerged from a binary package that may be why
Doesn't it rather defeat the object of binary packages if they don't do all the setup required? My methodology is to build packaes on a compile server. Then all other machines rsync against the compile server, getting the binary packages as well as the rest of the portage tree. Are you saying that I can't rely on binary packages to install properly?
doesnt it defaet the point of filing a bug if you dont provide all the information ? :P i just changed the ebuild around in cvs so it should work *** This bug has been marked as a duplicate of 25152 ***
