Thanks Sven.
I'm not sure if this is a valid bug or not. I understand why it doesn't
work in your case, but it could be argued that it's too much of an edge
case to expect the postinst to handle it.
So I think the workarounds are:
1) Do not have the puppet user or group in NIS/LDAP.
2) Have both the puppet user and group in NIS/LDAP.
There's some discussion of how this should be handled as standard here:
http://wiki.debian.org/AccountHandlingInMaintainerScripts
http://lists.debian.org/debian-devel/2007/08/msg00197.html
I found a bug that deals with it differently here:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=386091
I don't think it's worth maintaining a delta in Ubuntu for this issue.
If you wish, you can submit this bug to Debian (see
http://www.debian.org/Bugs/Reporting). If the bug is fixed in Debian,
then Ubuntu will pick it up. If you do submit a Debian bug, please link
to it from here to help tracking.
Thanks again for your time on this issue. Even though I don't think this
particular issue is worth fixing in Ubuntu, I appreciate your
contribution.
** Bug watch added: Debian Bug tracker #386091
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=386091
** Changed in: puppet (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/1012649
Title:
puppet-common postinst assumes puppet group is present if puppet user
is present
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1012649/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
