On Mon, Dec 30, 2013 at 8:08 PM, Brian Hanks bha...@bhanks.net wrote:
Interestingly, I found this on the Fedora FedUp Wiki page:
Will packages in third party repositories be upgraded?
Yes, if they are set up like regular yum repositories and do not hard code
the repository path.
On Sun, 29 Dec 2013 22:47:07 -0700, Chris Murphy wrote:
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.
On Dec 30, 2013, at 5:49 AM, Brian Hanks bha...@bhanks.net wrote:
On Sun, 29 Dec 2013 22:47:07 -0700, Chris Murphy wrote:
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
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
On Mon, 30 Dec 2013 19:47:30 +0100, Michael Schwendt wrote:
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.
My
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/30/2013 3:08 PM, Brian Hanks wrote:
After reading this, I checked my RPMFusion repos and found that
none are hard-coded. All are using the $releasever variable, and
all resolve to valid repos with the proper packages available. My
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
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
On Sun, Dec 29, 2013 at 9:58 AM, Rahul Sundaram wrote:
Which version of fedup? Make sure you have the latest
https://fedoraproject.org/wiki/FedUp#Why_does_my_upgrade_to_Fedora_20_fail_.28immediately_reboot_to_my_old_Fedora.29.3F
I read this before I made my first attempt and I validated
On Dec 29, 2013, at 7:51 AM, Brian Hanks bha...@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
On Sat, 28 Dec 2013 15:57:11 -0600, Brian Hanks wrote:
1. Fedup Upgrade of two different HP laptops each currently with Fedora
19 and simple partitioning (ext4 only). I've attempted this upgrade
multiple times on each machine. It fails every time with a VirtualBox
dependency error.
11 matches
Mail list logo
