On Tue, 2011-04-26 at 19:03 -0500, Eric Evans wrote:
There is one for each version now (06x, 07x, and 08x). The unstable
suite continues to point to latest-and-greatest. The wiki has been
updated.
Where, exactly, is this on the wiki? I had been using the CloudConfig
page [1], which still only
On Wed, Apr 27, 2011 at 1:46 PM, David Strauss da...@davidstrauss.net wrote:
On Tue, 2011-04-26 at 19:03 -0500, Eric Evans wrote:
There is one for each version now (06x, 07x, and 08x). The unstable
suite continues to point to latest-and-greatest. The wiki has been
updated.
Where, exactly,
Thanks Eric!
On Apr 26, 2011, at 7:03 PM, Eric Evans wrote:
On Sat, 2011-04-23 at 16:49 -0700, David Strauss wrote:
I just noticed that, following the Cassandra 0.8 beta release, the Apt
repository is encouraging servers in my clusters to upgrade. Beta
releases should probably be on
On Tue, 2011-04-26 at 19:03 -0500, Eric Evans wrote:
There was already a repo for cassandra-0.6 (called 06x), it just fell
through the cracks with the last release.
There is one for each version now (06x, 07x, and 08x). The unstable
suite continues to point to latest-and-greatest. The wiki
On Sat, 2011-04-23 at 16:49 -0700, David Strauss wrote:
I just noticed that, following the Cassandra 0.8 beta release, the Apt
repository is encouraging servers in my clusters to upgrade. Beta
releases should probably be on different channels (or named
differently) than stable ones.
There was
If you don't want your APT-sourced packages to upgrade automatically, I suggest
pinning the package.
The apt_preferences(5) man page tells you how to do this.
The gist is to add the following lines:
Package: cassandra
Pin: version 0.6.13
Pin-Priority: 1100
(setting the version to the
On Mon, 2011-04-25 at 15:25 -0700, Gregory Szorc wrote:
If you don't want your APT-sourced packages to upgrade automatically,
I suggest pinning the package.
I'm aware that I can pin the package, but it's still a workaround for
the Cassandra Apt repository not being set up according to best
