Bug 876157 - Downloading failed: invalid data in .treeinfo: No option 'upgrade' in section: 'images-x86_64'
Summary: Downloading failed: invalid data in .treeinfo: No option 'upgrade' in section...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: fedup
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Will Woods
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F18Beta, F18BetaBlocker
TreeView+ depends on / blocked
 
Reported: 2012-11-13 13:23 UTC by Jan Sedlák
Modified: 2012-11-13 17:40 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-11-13 15:01:42 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
fedup debug log (531.31 KB, text/x-log)
2012-11-13 13:23 UTC, Jan Sedlák
no flags Details

Description Jan Sedlák 2012-11-13 13:23:35 UTC
Created attachment 644094 [details]
fedup debug log

Description of problem:
I tried running fedup using instructions from wiki ("sudo fedup-cli --network 18 --debuglog fedupdebug.log --instrepo=http://tflink.fedorapeople.org/fedup/f18-upgrade/x86_64") and with fedup from github and it failed with error "Downloading failed: invalid data in .treeinfo: No option 'upgrade' in section: 'images-x86_64'". See attached fedup log.

Comment 1 Josef Skladanka 2012-11-13 14:28:46 UTC
I'm hitting the same error.

Comment 2 Will Woods 2012-11-13 15:01:42 UTC
This requires images built with a newer lorax, e.g.:

  https://github.com/wgwoods/lorax

Patches have been sent to lorax upstream. In the meantime, you'll need to fix your repo and/or ask tflink to edit his .treeinfo so it has "upgrade = $PATH/upgrade.img" instead.

Feel free to reopen if that doesn't fix it.

Comment 3 Tim Flink 2012-11-13 17:40:39 UTC
I've hacked the described change into the test repo and it appears to work from my initial testing. I'm currently working on testing the lorax changes for fedup and will update the initramfs in the test repo once there are changes in git.


Note You need to log in before you can comment on or make changes to this bug.