Description of problem: When anaconda shows partition sizes, it has GB unit equal to 1000*1024*1024 (1048832062) bytes. For example, virtual drive that is 8589934592 ( = 8*1024*1024*1024) bytes is shown like 8.19GB, (= 8192/1000). Users might expect it to be all 1024-based or all 1000-based, not the mix. Version-Release number of selected component (if applicable): anaconda-20.25.14-1.fc20.x86_64
Blocking according to: The installer must be able to create and install to any workable partition layout using any file system and/or container format combination offered in a default installer configuration. Explanation: as user I'm not understanding sizes installer shows and unable to create layout with exact size I need to.
we really appreciate all the reports, but I think you might be setting a bit too low a bar on blocker nominations. a blocker on that criterion would be something like 'it explodes when i try and create an xfs partition', not 'the units are a bit off'...
I agree it's a bug, the units should be either MB, GB or MiB, GiB not some blend. But -1 as a blocker, suggest reset to Rawhide.
-1 blocker in case I won't be able to make the blocker meeting.
Discussed in 2013-12-09 Blocker Review meeting [1]. Voted as a RejectedBlocker and RejectedFreezeException. If the report is accurate this obviously ought to be fixed, but doesn't have any consequences significant enough to violate any criteria. also rejected as FE as it's too late to change something like this which could break other things. [1] http://meetbot.fedoraproject.org/fedora-blocker-review/2013-12-09/