#41039: Installing MacPorts on Mavericks Renames "staff" Group To "macports" -----------------------------+-------------------------------- Reporter: roberthuston@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.2.1 Resolution: | Keywords: Port: | -----------------------------+-------------------------------- Changes (by ryandesign@…): * component: ports => base Old description:

After upgrading to Mavericks, I installed MacPorts 2.2.1 using the "Mavericks" version of the installer. Today, when doing an "ls -l" in Terminal, I noticed that my default user group now says "macports" instead of "staff." However, when I look at the gid that is allocated to the "macports" group, it is indeed the value 20 that is normally associated with "staff." Somehow the MacPorts installation has hijacked the "staff" name. How can I get it restored to its proper name?

A listing of my /etc/group file still has

staff:*:20:root

as one of the entries, and there are no "macports" entries. So where is this remapping of the "staff" into "macports" happening?

New description: After upgrading to Mavericks, I installed MacPorts 2.2.1 using the "Mavericks" version of the installer. Today, when doing an "ls -l" in Terminal, I noticed that my default user group now says "macports" instead of "staff." However, when I look at the gid that is allocated to the "macports" group, it is indeed the value 20 that is normally associated with "staff." Somehow the MacPorts installation has hijacked the "staff" name. How can I get it restored to its proper name? A listing of my /etc/group file still has {{{ staff:*:20:root }}} as one of the entries, and there are no "macports" entries. So where is this remapping of the "staff" into "macports" happening? -- Comment: I'm not sure why this is happening, but to answer your question about where this is happening, read the top of the /etc/group file: {{{ ## # Group Database # # Note that this file is consulted directly only when the system is running # in single-user mode. At other times this information is provided by # Open Directory. # # See the opendirectoryd(8) man page for additional information about # Open Directory. ## }}} -- Ticket URL: <https://trac.macports.org/ticket/41039#comment:1> MacPorts <http://www.macports.org/> Ports system for OS X

#41039: Installing MacPorts on Mavericks Renames "staff" Group To "macports" -----------------------------+-------------------------------- Reporter: roberthuston@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.2.1 Resolution: | Keywords: Port: | -----------------------------+-------------------------------- Comment (by roberthuston@…): I just attached two window captures of both the "macports" group and the "staff" group. You can see that they both share the same ID of 20. Is it safe to delete the macports entry? -- Ticket URL: <https://trac.macports.org/ticket/41039#comment:3> MacPorts <http://www.macports.org/> Ports system for OS X

#41039: Installing MacPorts on Mavericks Renames "staff" Group To "macports" -----------------------------+-------------------------------- Reporter: roberthuston@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.2.1 Resolution: | Keywords: Port: | -----------------------------+-------------------------------- Comment (by roberthuston@…): Digging more into the installer targets of the MacPorts project Makefile, the installation process creates a MacPorts user and a macports group. The user ID will be the next available ID, but the group ID ends up being 20, which is also the same ID used for staff. Is this a misuse of gid's or is it the correct UNIX way. Either way, I sometimes see things as "staff" and other times as "macports," usually after running the port command itself. -- Ticket URL: <https://trac.macports.org/ticket/41039#comment:5> MacPorts <http://www.macports.org/> Ports system for OS X

#41039: Installing MacPorts on Mavericks Renames "staff" Group To "macports" -----------------------------+-------------------------------- Reporter: roberthuston@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.2.1 Resolution: | Keywords: Port: | -----------------------------+-------------------------------- Comment (by adrian@…): I just ran into this issue too - quite shocking to see all your files owned by group macports, but doesn't seem to cause great problems. I fixed this by deleting the macports user and group using /System/Library/CoreServices/Directory Utility.app and then running a small script produced from the macports pkg installer's postinstall script. Save this as create-macports-user-group.sh and then run with "sudo ./create-macports-user-group.sh" {{{ #!/bin/bash # Abstraction variables: DSCL=/usr/bin/dscl RUNUSR=macports # create the user to use for privilege dropping DSEDITGROUP=/usr/sbin/dseditgroup if ! ${DSCL} -q . -read /Groups/${RUNUSR} > /dev/null 2>&1 ; then echo "Creating group \"${RUNUSR}\"" ${DSEDITGROUP} -q -o create ${RUNUSR} fi if ! ${DSCL} -q . -list /Users/${RUNUSR} > /dev/null 2>&1 ; then echo "Creating user \"${RUNUSR}\"" NEXTUID=501 while [[ -n "`${DSCL} -q /Search -search /Users UniqueID $NEXTUID`" ]]; do let "NEXTUID=NEXTUID+1" done ${DSCL} -q . -create /Users/${RUNUSR} UniqueID $NEXTUID # These are implicitly added on Mac OSX Lion. AuthenticationAuthority # causes the user to be visible in the Users & Groups Preference Pane, # and the others are just noise, so delete them. # https://trac.macports.org/ticket/30168 ${DSCL} -q . -delete /Users/${RUNUSR} AuthenticationAuthority ${DSCL} -q . -delete /Users/${RUNUSR} PasswordPolicyOptions ${DSCL} -q . -delete /Users/${RUNUSR} dsAttrTypeNative:KerberosKeys ${DSCL} -q . -delete /Users/${RUNUSR} dsAttrTypeNative:ShadowHashData ${DSCL} -q . -create /Users/${RUNUSR} RealName MacPorts ${DSCL} -q . -create /Users/${RUNUSR} Password \* ${DSCL} -q . -create /Users/${RUNUSR} PrimaryGroupID $(${DSCL} -q . -read /Groups/${RUNUSR} PrimaryGroupID | /usr/bin/awk '{print $2}') ${DSCL} -q . -create /Users/${RUNUSR} NFSHomeDirectory ${PREFIX}/var/macports/home ${DSCL} -q . -create /Users/${RUNUSR} UserShell /usr/bin/false fi if [[ $(sw_vers -productVersion | /usr/bin/awk -F . '{print $2}') -eq 4 ]]; then GID=$(${DSCL} -q . -read /Groups/${RUNUSR} PrimaryGroupID | /usr/bin/awk '{print $2}') if [[ "$(${DSCL} -q . -read /Users/${RUNUSR} PrimaryGroupID 2>/dev/null | /usr/bin/awk '{print $2}')" != "$GID" ]]; then echo "Fixing PrimaryGroupID for user \"${RUNUSR}\"" ${DSCL} -q . -create /Users/${RUNUSR} PrimaryGroupID $GID ${DSCL} -q . -create /Users/${RUNUSR} RealName MacPorts fi fi if [[ "$(${DSCL} -q . -read /Users/${RUNUSR} NFSHomeDirectory)" = "NFSHomeDirectory: /var/empty" ]]; then echo "Updating home directory location for user \"${RUNUSR}\"" ${DSCL} -q . -create /Users/${RUNUSR} NFSHomeDirectory ${PREFIX}/var/macports/home fi }}} After that the macports user and groups PrimaryGroupID was 502, instead of 20. -- Ticket URL: <https://trac.macports.org/ticket/41039#comment:8> MacPorts <http://www.macports.org/> Ports system for OS X