Hi Trent, On Sat, 28.07.2007 at 07:25:06 +1000, Trent W. Buck <[EMAIL PROTECTED]> wrote: > During installation: > | Selecting previously deselected package roundup. > | (Reading database ... 221017 files and directories currently installed.) > | Unpacking roundup (from .../roundup_1.3.3-3_all.deb) ... > | groupmod: 113 is not a unique GID
this should be a warning only, not really an error. Of course, groupmod issues that as an error, but the script, as you outline below, ignores it, turning the error into a warning instead. > | Setting up roundup (1.3.3-3) ... > | Starting Roundup HTTP-Server: roundup-server. > | > | Press return to continue. Apparently, the installation went ok. > Upon investigation: > | $ cd /var/lib/dpkg/info > | $ grep -n groupmod roundup.* > | roundup.preinst:18: groupmod -g `id -u roundup` roundup || true > | $ id roundup > | uid=113(roundup) gid=112(roundup) groups=112(roundup) > > The postinst is trying to forcibly set the GID to match the UID, and > this is not working because that GID is already in use. Well, it tries to set the GID=UID, but not forcibly (that's what the "|| true" phrase at the end of the statement accomplishes - if it does not work, then it just leaves the gid as is. So everyone who does not already have the gid used, gets their GID=UID, and everyone else simply gets some GID and some UID. > Is it even necessary to futz with the GID? No, it's not necessary to adjust the GID, but it's convenient and often seen in other packages to have UID=GID. > If not, this line could simply be removed. That line could simply be removed, but unless you can demonstrate that the installation *fails*, I'm not going to do it. Best, --Toni++ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
