I performed "emerge --update tomcat" to pick up the -r1 version. When removing the old version, the last step it performed was removing the "tomcat" user and group. Since this is the last step performed in the upgrade, it leaves the system without these. Could not reproduce it, as the 'emerge sync' removed tomcat-4.1.24 ebuild. Fixed it by unmerging and re-emerging tomcat; this time received message along the lines of "user and group tomcat preserved". Might also work to just emerge tomcat again.
yeah I have this too [me too ;)] strange thing is, in the ebuild in the function pkg_postrm() it says ... if [ -z "${INSTALLED}" ] ... remove users, which should be correct as in src_installing the var INSTALLED="yes" is set ... so ... hmm ... my bash knowledge is too small :((
Hrm... think this is a problem in the Portage --update code, not the ebuild. In any case I'm going to sit on this for a while since the tomcat user will be merged into baselayout soon.
anyway, I fixed this in the meantime by doing: groupadd tomcat useradd -d /opt/tomcat -g tomcat tomcat cd /opt/tomcat && chown -R tomcat.tomcat * cd /var/log && chown tomcat.tomcat tomcat is this correct? should some of the files in /opt/tomcat bleong to root? how about /var/log/tomcat?
Fixed in 5.0.18 and the new 4.1.29
*** Bug 148058 has been marked as a duplicate of this bug. ***
