On Sat, 28 Dec 2013 23:56:30 +0100, Michael Schwendt wrote:
What "dependency error" did it report? And how did you query the installed packages as well as the remote repos for what would be available_after_ the upgrade?
Many users still misread such error messages and don't manage to work around them as a result. Often, the installed packages are okay, but during they upgrade they would get replaced and break dependencies.
The exact error message was "WARNING: problems were encountered during transaction test: broken dependencies kmod-VirtualBox-3.12.5-200.fc19.x86_64-4.3.6-1.fc19.1.x86_64 requires kernel-3.12.5-200.fc19.x86_64 Continue with upgrade at your own risk."
In response I removed kmod-VirtualBox, akmod-VirtualBox, and VirtualBox. Then I did a fedup --clean and reattempted fedup --network 20. This went well until the reboot. Following the reboot I select the Fedup option, but nothing really happened. I ended up back in my Fedora 19 system while running the new Fedora 20 kernel.
As an update on the other machine where I was having problems with the net install. I checked for any meaningful logs but found that none exist. The /var/log directory hasn't even been created. So, then I tried to run a grub2-mkconfig, grub2-install, dracut series to potentially fix the problem. The file sizes did change a bit, but the end result was the same.
Brian
Hi
On Sun, Dec 29, 2013 at 9:51 AM, Brian Hanks wrote:
In response I removed kmod-VirtualBox, akmod-VirtualBox, and VirtualBox. Then I did a fedup --clean and reattempted fedup --network 20. This went well until the reboot. Following the reboot I select the Fedup option, but nothing really happened. I ended up back in my Fedora 19 system while running the new Fedora 20 kernel. As an update on the other machine where I was having problems with the net install. I checked for any meaningful logs but found that none exist. The /var/log directory hasn't even been created. So, then I tried to run a grub2-mkconfig, grub2-install, dracut series to potentially fix the problem. The file sizes did change a bit, but the end result was the same.
Which version of fedup? Make sure you have the latest
https://fedoraproject.org/wiki/FedUp#Why_does_my_upgrade_to_Fedora_20_fail_....
Rahul
On Dec 29, 2013, at 7:51 AM, Brian Hanks bhanks@bhanks.net wrote:
This went well until the reboot. Following the reboot I select the Fedup option, but nothing really happened. I ended up back in my Fedora 19 system while running the new Fedora 20 kernel.
You chose the fedup option in GRUB, but instead of getting text status of the progessing update, you got what appeared to be normal F19 boot?
If /var is a separate partition/LV instead of on rootfs, this behavior occurs. Please post your fstab if unsure. Do you have any encrypted partitions or volumes? Please post the result of lsblk if yes.
Chris Murphy
On Sun, 29 Dec 2013 08:51:01 -0600, Brian Hanks wrote:
The exact error message was "WARNING: problems were encountered during transaction test: broken dependencies kmod-VirtualBox-3.12.5-200.fc19.x86_64-4.3.6-1.fc19.1.x86_64 requires kernel-3.12.5-200.fc19.x86_64 Continue with upgrade at your own risk."
Exactly. Taking away that F19 kernel (by replacing it with a F20 kernel) will break the dependency.
In response I removed kmod-VirtualBox, akmod-VirtualBox, and VirtualBox.
So, there are no repos that offer updates for those three packages? Or is fedup unable to handle 3rd party repos?
Other than that, please don't add my name to the mail's subject line in such a misleading/ambiguous way. Thank you.
-
Brian Hanks -
Chris Murphy -
Michael Schwendt -
Rahul Sundaram