Summary: | Plain e2fsprogs release should not be supporting ext4 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Maurice Volaski <mvolaski> |
Component: | [OLD] Core system | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | bensberg, correo, kanelxake, yamadharma |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Maurice Volaski
2007-02-19 01:30:23 UTC
*** Bug 168315 has been marked as a duplicate of this bug. *** With ext4 patches the e2fsprogs does not even pass its own tests, see bug #159834. Could we at least have an ext4 USE flag to control applying of the patches? And if enabled print a warning that the tool is not fully compatible with ext3. That sounds reasonable to me. *** Bug 159834 has been marked as a duplicate of this bug. *** fixed in 1.39-r2 It's not fixed. You didn't provide ext4 flag or ebuild. I have to mask the newer version just to use ext4 - and this means I won't get the newest fixes. nor do i plan to if you want ext4, use 1.39-r1 until it gets merged into a real version (In reply to comment #7) > nor do i plan to > > if you want ext4, use 1.39-r1 until it gets merged into a real version > Grreate! And now when you've droped ext4 support and my system at work doesn't boot I must search in bug list, why. Ofcause, i fix my trouble, but would you possible to do more correct fixes next time. maybe some day if you are a developer you can make these sort of calls ... until then, you're not having to maintain the package, so you can deal with the reality *** Bug 212099 has been marked as a duplicate of this bug. *** |