cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "paul cannon (Updated) (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-3480) allow 'cassandra' deb to replace 'apache-cassandra1'
Date Wed, 09 Nov 2011 21:09:51 GMT


paul cannon updated CASSANDRA-3480:

    Attachment: 3480.patch.txt
> allow 'cassandra' deb to replace 'apache-cassandra1'
> ----------------------------------------------------
>                 Key: CASSANDRA-3480
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Packaging
>         Environment: Debian-based distros
>            Reporter: paul cannon
>            Assignee: paul cannon
>            Priority: Minor
>         Attachments: 3480.patch.txt
> Datastax has begun distributing [1], due to a miscommunication, a debian package identical
to the one distributed by Apache, but with its package name changed to "apache-cassandra1".
Datastax now intends to go back to using the Apache packages unchanged, but it is going to
take some time since we have also released a suite of tools, demos, products, and documentation
that refer to the "apache-cassandra1" name, and it will take some more QA and documentation
updates before we can make the full transition back. In the meantime, though, more people
are installing the apache-cassandra1 deb. 
> To minimize confusion between the two, and facilitate the transition away from apache-cassandra1,
I recommend that we add these lines to Cassandra's debian/control:
> {noformat}
> Conflicts: apache-cassandra1
> Replaces: apache-cassandra1
> {noformat}
> that users of apache-cassandra1 will be able to install the cassandra deb from Apache
without losing their configuration or needing to fully uninstall one, then install the other.
It will also keep users from mistakenly trying to install both packages at the same time (it
won't work if they try; they'll see errors, but they might not make sense).
> [1]

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message