hal-0.5.11-r4 can't get sizes of partitions >1Tb
Testeted on Segeate 1.5Tb
Steps to Reproduce:
1. Try to automount fixed or removable device with partition size >1Tb
Created attachment 177449 [details, diff]
New ebuild with patch solving this problem
Is it the same error wich was fixed in the hal git repository a while ago (see the link below) and still hasn't made its way into portage?
If this fix could be applied to the package which is available in portage it would also solve bug 233187.
(In reply to comment #2)
> Is it the same error wich was fixed in the hal git repository a while ago (see
> the link below) and still hasn't made its way into portage?
OMG, it's the same problem and still hasn't fixed at portage.
> If this fix could be applied to the package which is available in portage it
> would also solve bug 233187.
It would be wonderfull ;]
Adding this to the new "4" patchset as patch number 10. Thank you for your bug report. Rafael, thank you for linking the upstream commit, I have taken that fix.
*** Bug 233187 has been marked as a duplicate of this bug. ***
+*hal-0.5.11-r7 (04 Feb 2009)
+ 04 Feb 2009; <firstname.lastname@example.org> metadata.xml, +hal-0.5.11-r7.ebuild:
+ Avoid circular dependencies between HAL and X by dropping migration script
+ and py86 dependency, closes bug #225091 by Ster0n <email@example.com>.
+ Properly ignore Dell recovery partitions, patch supplied by Pacho Ramos
+ <firstname.lastname@example.org> in bug #236784. Stop hiding unmounted
+ partitions, as suggested by Kirill Igorevich Cherniy
+ <email@example.com> in bug #247025. Upstream patch identified by
+ Rafael <firstname.lastname@example.org> fixes detection of partitions over ~1.2TB in
+ size, closes bug #253815 by Yar Odin <email@example.com>. Cease using
+ deprecated keys in our installed examples, as pointed out by Sebastian
+ Günther <firstname.lastname@example.org> in bug #256304.