On Thu, 29 Nov 2012 05:49:30 -0500 (EST)
Kamil Paral <kparal(a)redhat.com> wrote:
I think it doesn't really matter whether you use plymouth or
not.
FedUp downloads a custom kernel+initrd to handle the upgrade. The
error in your bugzilla seem like a broken dependencies issue. That
might really be an upstream broken repository, or it is a problem
with your local cache.
It was a cache problem,
fixed.
tested with --instrepo=fedora (as distinct from http://...)
Now got to downloading boot images.
Failed on following (snipped)
[ 93.240] (II) fedup.yum:download_packages() beginning package
download...
[ 629.478] (DD) fedup.yum:treeinfo() fetching .treeinfo from repo
'fedora'
[ 667.080] (DD) fedup.yum:treeinfo() .treeinfo saved
at /var/tmp/fedora-upgrade/.treeinfo
[ 667.081] (DD) fedup.yum:grab_and_check() grabbing i386 kernel
[ 667.081] (II) fedup.yum:grab_and_check() downloading
images/pxeboot/vmlinuz to /boot/upgrade/vmlinuz
[ 669.176] (DD) fedup.yum:checkfile() checking
images/pxeboot/vmlinuz
[ 669.244] (II) fedup:<module>() Downloading failed. Exception:
Traceback (most recent call last):
File "/bin/fedup-cli", line 285, in <module>
main(args)
File "/bin/fedup-cli", line 237, in main
kernel, initrd = f.download_boot_images() # TODO: arch
File "/usr/lib/python2.7/site-packages/fedup/download.py", line
256, in download_boot_images
raise YumBaseError(_("invalid data in .treeinfo: %s") % str(e))
YumBaseError: invalid data in .treeinfo: No option 'upgrade' in
section: 'images-i386'
[ 669.273] (II) fedup:<module>() /bin/fedup-cli exiting at Thu Nov
29 11:14:00 2012
Regards,
Frank