Well no feedback from the community :-(
So I ran preupgrade from F16 again on the hunch it would fix up the Rpmdb and should then
do a pretty fast install as all the packages are already installed.
That worked. So no need for anyone to answer. I have a Beefy Miracle, aptly named for
me.
Someone should look at the JBoss-as package issue.
Also perhaps allow people to skip offending application packages in the install rather
than force an exit.
Regards,
William
On May 31, 2012, at 12:02 PM, William Henry <whenry(a)redhat.com> wrote:
To understand what happened see my email regarding the JBoss failure.
It all started there.
Basically because of that failure I tried to force the JBoss-as package install under f16
kernel boot 3/4 ways through the f17 install. After successfully installing all the rest
of the packages using f17 installer process, the install failed due to the rpmdb changing
underneath. That was me forcing the JBoss-as installation I guess. So after the installed
exited. Reboot shows no beefy miracle in the grub list.
So now it's no longer the offending JBoss-as package it's more a how do I recover
from this failure at this point. Or if I can't should I just install f17 from scratch
and hope my /home backup will recover nicely into f17.
William
--
users mailing list
users(a)lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines:
http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away:
http://ask.fedoraproject.org