From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.1 (X11; Linux i686; U;) Gecko/20020417
Description of problem:
I did a full limbo v2 install. then upgrade to null. This is on a 30GB
disk. It lacks 35MB on the root partition. This means the auto partition of
limbo sucked. I guess this is unfixable now, but null can
allow for a better auto partinioning scheme giving / a bit more MB's
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.do full install of limbo, chosing auto partion on big disk(30GB)
2.upgrade to null
Actual Results: I had to cancel lots of packages, ignore dependancies and
hope it would fit. This took 5 re-selections. It's difficult to select,
because it will want to upgrade 'all'. You have to deselect some of the first
release packages of null that weren't on limbo (like desktop-extra)
or do 'do not install packages that have dependancies) and hope that
gets you past this part.
If this is just an issue for limb->null, it's not too bad, and null
can be armored by giving it a better autopartion scheme for upgrades to
8.0 or later. If this is also a problem for 7.3->null, then this might be a
big show stopper for real users with real upgrades.
workaround: first rpm -e kernel-BOOT kernel-debug kernel-enterprise worked for
me. It's now installing packages.
What autopartitioning class did you choose (desktop/workstation/custom/server)?
Whatever was the default. It was just a "hit return to install it all" type
install I performed.
If you got kernel-debug and kernel-enterprise you must have done an install
which selected 'Everything', which is not a default choice.
Did you choose Personal Desktop, Workstation, Server, or Custom?
With limbo i do not remember. With null I selected "upgrade current"
I can't really investigate the issue without that information.
If I do an Everything install using a 20GB drive and dedicate all of it to
autopartitioning then I can upgrade fine.
Did you choose to erase everything on the drive, or do you have non-Linux
partitions which are using up space?
Closing due to inactivity.
Please reopen this bug report if you continue to have problems.
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.