[
https://issues.apache.org/jira/browse/CASSANDRA-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis updated CASSANDRA-1816:
--------------------------------------
Component/s: Packaging
Affects Version/s: (was: 0.7.0 rc 1)
Fix Version/s: 0.7.0
> cassandra deb should depend on adduser
> --------------------------------------
>
> Key: CASSANDRA-1816
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1816
> Project: Cassandra
> Issue Type: Bug
> Components: Packaging
> Environment: Debian squeeze
> Reporter: paul cannon
> Priority: Minor
> Fix For: 0.7.0
>
> Attachments: cass-1816.txt
>
>
> The cassandra debian package uses the addgroup and adduser commands in its
> postinst script, which are found in the 'adduser' package, but the cassandra
> debian package does not depend on adduser. When a user does not already
> have adduser installed, this will lead to an error like:
> {noformat}
> Setting up cassandra (0.7.0~rc1) ...
> /var/lib/dpkg/info/cassandra.postinst: 50: addgroup: not found
> dpkg: error processing cassandra (--configure):
> subprocess installed post-installation script returned error exit status 127
> {noformat}
> Yes, this won't happen much, because systems without adduser installed are
> rare. But adduser is not "Essential: yes", so it will happen sometimes in
> bare-bones VMs or development environments.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
