Hi All
I was in the process of upgrading fc20 to fc21 using fedup
more than 2600 files were downloaded but after the process ended there was an error that the file dotconf something was not able to be downloaded in addition to some other errors in the log file I will try to attach
of course I have not seen the reboot order to start the new installations but all the downloaded files are still in the cache
Any suggestions ?
fedup1.txt

you do have a known good backup ?
right ?

Fedora 22 was released
http://forums.fedoraforum.org/showthread.php?t=304620

I wonder if the two events are related ... Or is that just me being cynical.

Any use of update tools is liable to grief. I don't regularly use fedup (I test it every so often), but I'm always prepared to have to do a full (clean) install if it all falls in a heap. Waste of bandwidth, but that's life.
I find having a separate /home partition helps - but the backup is still required.

I have some files stored somewhere else anyway I use the box for testing

I have no idea what is package "dotconf".
If you do not need it, remove package in fc20, then update will not download it's update.

You know, remove it anyway, you can install it later.

the third party repos in fedora have been causing upgrade problems since fedora 2 upgrade

now rpmfusion is helpping
BUT
a clean new install of 20 and you ONLY use the update ( NO!!! thirdparty repos)
a fully updated install "should" upgrade 21 fine


Koji
rpmfusion-free
rpmfusion-nonfree
SUSE-OBS/fedora

If 'dotconf' is a package that Fedup does not recognize-IOW is not from a standardrepo-fedup will fail on that. Uninstall the package and try fedup again. It should run through the file checking procedure and once the foreign packages are no longer at issue, it should proceed.

I would skip 21 for 22.

Having recently (as in this week) done a fedup from f20 to F22, it worked fine(-ish) even with rpmfusion and google-chrome repos in the list.
Moaned about missing keys - but that included the keys for the fedora F22 repos as well as rpmfusion. Go figure.

It worked at the end for me also fc20 to 21

Apparently the missing key issue with F22 is only seen with fedup from F20->F22, so hopefully you won't see it if/when you update to F22.

Yes I did

Tried 20->21 and ran into the same problem:

setting up system for upgrade
Traceback (most recent call last):
File "/usr/bin/fedup-cli", line 286, in <module>
main(args)
File "/usr/bin/fedup-cli", line 223, in main
prep_boot(kernel, initrd)
File "/usr/lib/python2.7/site-packages/fedup/sysprep.py", line 181, in prep_boot
modify_bootloader(kernel, initrd)
File "/usr/lib/python2.7/site-packages/fedup/sysprep.py", line 131, in modify_bootloader
boot.add_entry(kernel, initrd, banner=_("System Upgrade"))
File "/usr/lib/python2.7/site-packages/fedup/boot.py", line 43, in add_entry
return check_output(cmd, stderr=PIPE)
File "/usr/lib64/python2.7/subprocess.py", line 568, in check_output
process = Popen(stdout=PIPE, *popenargs, **kwargs)
File "/usr/lib64/python2.7/subprocess.py", line 711, in __init__
errread, errwrite)
File "/usr/lib64/python2.7/subprocess.py", line 1327, in _execute_child
raise child_exception
OSError: [Errno 2] No such file or directory


Any suggestions?

Regards,

Bill Lee