From: Daniel Pocock <daniel@pocock.com.au>
To: linux-btrfs@vger.kernel.org
Subject: btrfs-tools in Debian squeeze-backports?
Date: Mon, 02 Jan 2012 15:29:49 +0100 [thread overview]
Message-ID: <4F01BF5D.2070801@pocock.com.au> (raw)
These are the btrfs-tools versions on Debian:
squeeze:
kernel: 2.6.32
tools: 0.19+20100601-3
squeeze-backports:
kernel: 2.6.39
tools: nothing (so user ends up with 0.19+20100601-3)
wheezy/testing/sid:
kernel: 3.1.6-1
tools: 0.19+20111105-2
Using the 2.6.39 kernel from squeeze-backports, do I need a newer
btrfs-tools and is there a particular reason it is not in
squeeze-backports too?
Or should I not be trying to use the versions in squeeze at all - should
I be on testing/wheezy or unstable?
The Debian btrfs wiki and the regular btrfs wiki don't really suggest a
good starting point (other than suggesting the btrfs has been in Debian
since squeeze)
http://wiki.debian.org/Btrfs
If I try to use the version from testing or unstable, I get this error
on a squeeze setup:
btrfs-tools depends on e2fslibs (>= 1.41.99); however:
Version of e2fslibs on system is 1.41.12-4stable1.
http://packages.debian.org/search?keywords=btrfs-tools
next reply other threads:[~2012-01-02 14:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-02 14:29 Daniel Pocock [this message]
2012-01-02 14:43 ` btrfs-tools in Debian squeeze-backports? Hugo Mills
2012-01-02 14:55 ` cwillu
2012-01-02 15:01 ` Daniel Pocock
2012-01-02 15:14 ` Hugo Mills
2012-01-02 16:25 ` (renamed thread) btrfs metrics Daniel Pocock
2012-01-02 16:39 ` Hugo Mills
2012-01-04 11:48 ` Daniel Pocock
2012-01-04 18:46 ` Kok, Auke-jan H
2012-01-05 10:09 ` Daniel Pocock
2015-08-30 12:31 ` (renamed thread) btrfs metrics, free space reporting Daniel Pocock
2015-08-31 2:03 ` Qu Wenruo
2012-01-04 18:05 ` btrfs-tools in Debian squeeze-backports? Jan Schmidt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F01BF5D.2070801@pocock.com.au \
--to=daniel@pocock.com.au \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.