Fedup 18 -> 19 went fine for me, but I noticed a few warnings came up during the process. Is there any command one could or should run after fedup to clean up yum records?
[I grep-ped for error in fedup.log but didn't find anything except RPMs with error/Error in their names.]
On 07/06/13 15:50, Timothy Murphy wrote:
Fedup 18 -> 19 went fine for me, but I noticed a few warnings came up during the process. Is there any command one could or should run after fedup to clean up yum records?
What do you mean "clean up yum records"?
What were the warnings? What error messages are you seeing now?
Ed Greshko wrote:
On 07/06/13 15:50, Timothy Murphy wrote:
Fedup 18 -> 19 went fine for me, but I noticed a few warnings came up during the process. Is there any command one could or should run after fedup to clean up yum records?
What do you mean "clean up yum records"?
I don't know. The errors/warnings occured during fedup, so I assume they concerned yum in some way.
What were the warnings? What error messages are you seeing now?
I'm not seeing any warning or error messages now. I've very little idea what the warnings said, as they passed by quickly while downloading 3,079 RPMs. I think they implied that some file they were looking for did not exist.
I did look in /var/log/fedup.log but saw nothing relevant there (though if there was I could easily have missed it).
Incidentally, I've used fedup twice now, F-17->F-18 and F-18->F-19, and based on this sample of 2 I'd give it 150 out of 100. I was suspicious of it because the old Fedora upgrade (I forget its name) caused me endless trouble.
My only suggestion would be, as others have suggested, to give an estimate of the time the various parts will take. In my case, the part after re-boot took the longest, 4 to 5 hours.
On 06.07.2013 16:02, Timothy Murphy wrote:
Ed Greshko wrote:
On 07/06/13 15:50, Timothy Murphy wrote:
Fedup 18 -> 19 went fine for me, but I noticed a few warnings came up during the process. Is there any command one could or should run after fedup to clean up yum records?
What do you mean "clean up yum records"?
I don't know. The errors/warnings occured during fedup, so I assume they concerned yum in some way.
This warnings might be related to new config files in /etc directory. During system upgrade, a lot of new config files are placed in /etc but if there is a version of file modified by admin, yum places file form rpm as file with rpmnew extension and this behavior is reported to the user.
Mateusz Marzantowicz
Am 06.07.2013 16:02, schrieb Timothy Murphy:
Incidentally, I've used fedup twice now, F-17->F-18 and F-18->F-19, and based on this sample of 2 I'd give it 150 out of 100. I was suspicious of it because the old Fedora upgrade (I forget its name) caused me endless trouble.
My only suggestion would be, as others have suggested, to give an estimate of the time the various parts will take. In my case, the part after re-boot took the longest, 4 to 5 hours
sounds liek you have a ton of packages installed and the more files the longer takes SElinux relabel, the upgrade itself and dependency problems get also more likely
on my full featured workstation 1338 with KDE, a ton of severs and ZendStudio as wellas VMware the OS take 5.9 GB stripped down
package-cleanup --leaves package-cleanup --orphans
"package-cleanup --leaves --all" shows additional packages not required by other ones but should be used *careful*
-
Ed Greshko -
Mateusz Marzantowicz -
Reindl Harald -
Timothy Murphy