For background, I have just analysed the history in the git.gnome.org repo I
mention. There hasn't been a change recently there, a.f.a.i.c.t. More
specifically, their BTRFS detection code has been in there since Feb 23, 2009
(!!!) unaltered. So that makes it a part of upstream ever since GParted 0.4.4.
That gives me little reason to expect that packagers would change anything
about the patch that is wreaking havoc at this point.
Let me add: I have only done a targeted history search, there might be other
reasons why the patch would be removed/changed (and
Aurimas might have concrete information on the debianized version that I don't
have available), but this is what I _do have_ at the moment:
$ git remote -v
origin git://git.gnome.org/gparted (fetch)
origin git://git.gnome.org/gparted (push)
$ git log -i --grep=BTRFS --pickaxe-all
commit dc1ab54d8f2c40d628df01f48f6773bfe5fdab34
Author: Curtis Gedak <ged...@src.gnome.org>
Date: Mon Feb 23 20:22:30 2009 +0000
Added detection of btrfs file system
svn path=/trunk/; revision=1075
$ git describe dc1ab54d8f2c40d628df
GPARTED_0_4_3-10-gdc1ab54
$ git tag --contains dc1ab54d8f2c40d628df
GPARTED_0_4_4
GPARTED_0_4_5
GPARTED_0_4_6
GPARTED_0_4_7
GPARTED_0_4_8
GPARTED_0_5_0
GPARTED_0_5_1
GPARTED_0_5_2
GPARTED_0_6_0
GPARTED_0_6_1
GPARTED_0_6_2
GPARTED_0_6_3
GPARTED_0_6_4
--
gparted crash at start: glibmm-ERROR **
https://bugs.launchpad.net/bugs/617885
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
