Mailing-List: contact bigtop-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: bigtop-dev@incubator.apache.org
Date: Fri, 13 Jul 2012 21:20:34 +0000 (UTC)
From: "Sean Mackrory (JIRA)" <jira@apache.org>
To: bigtop-dev@incubator.apache.org
Message-ID: <762873811.50478.1342214434686.JavaMail.jiratomcat@issues-vm>
In-Reply-To: <2000333513.50476.1342214314861.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Updated] (BIGTOP-674) Installing hadoop-mapreduce package
 uses 'hadoop' group before creation
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/BIGTOP-674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sean Mackrory updated BIGTOP-674:
---------------------------------

    Summary: Installing hadoop-mapreduce package uses 'hadoop' group before creation  (was: BigTop)
    
> Installing hadoop-mapreduce package uses 'hadoop' group before creation
> -----------------------------------------------------------------------
>
>                 Key: BIGTOP-674
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-674
>             Project: Bigtop
>          Issue Type: Bug
>         Environment: Debian 12.04, probably other DEB and RPM-based distros
>            Reporter: Sean Mackrory
>            Assignee: Sean Mackrory
>
> When installing the hadoop-mapreduce package, users and files are assigned to the 'hadoop' group before that group has been created.
> I'm still working on verifying all the details for RPMs, but I will attached a patch that fixes this for DEBs (and quite possibly for RPMs too). It doesn't make sense to me why the group has not been added earlier. The hadoop group is added in the hadoop.spec file on line 510, and in the hadoop.preinst script - and I think both of these are supposed to execute before the lines where I've added the group in the attached patch.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira