Description of problem: just run the example: fedup-cli --network 18 Version-Release number of selected component: fedup-0.7-1.fc17 Additional info: libreport version: 2.0.16 abrt_version: 2.0.16 cmdline: /usr/bin/python /usr/bin/fedup-cli --network 18 kernel: 3.6.5-1.fc17.x86_64 backtrace: :fedup-cli:179:parse_args:TypeError: argument of type 'NoneType' is not iterable : :Traceback (most recent call last): : File "/usr/bin/fedup-cli", line 253, in <module> : args = parse_args() : File "/usr/bin/fedup-cli", line 179, in parse_args : if '://' in args.instrepo: :TypeError: argument of type 'NoneType' is not iterable : :Local variables in innermost frame: :p: ArgumentParser(prog='fedup-cli', usage='%(prog)s SOURCE [options]', description='Prepare system for upgrade.', version=None, formatter_class=<class 'argparse.HelpFormatter'>, conflict_handler='error', add_help=True) :net: <argparse._ArgumentGroup object at 0x18d2d50> :args: Namespace(bootloader=True, cacheonly=False, clean_metadata=False, debuglog=None, device=None, expire_cache=False, instrepo=None, iso=None, loglevel=30, network='18', reboot=False, repos=[], skipkernel=False, skippkgs=False) :req: <argparse._ArgumentGroup object at 0x18d2c10>
Created attachment 637865 [details] File: environ
Created attachment 637866 [details] File: smolt_data
Created attachment 637867 [details] File: core_backtrace
Yeah, the error message isn't incredibly friendly but it's saying that the command isn't properly formed. At the moment, --instrepo is required for fedup to run and it needs to point to a repo with a kernel and upgrade.img in the .treeinfo. I have a side repo like that set up for testing: http://tflink.fedorapeople.org/fedup/f18-upgrade/<arch> Make sure that you replace <arch> with the arch you're using (i386, x86_64)
*** Bug 873083 has been marked as a duplicate of this bug. ***
Should be fixed (or, at least, the error message should be clearer) by commit 79e9f88: https://github.com/wgwoods/fedup/commit/79e9f88
Presumably once the upgrade bits are included in f18 trees there will be no need to specify a repo./?
(In reply to comment #7) > Presumably once the upgrade bits are included in f18 trees > there will be no need to specify a repo./? That is my understanding of the plan, yes. The current requirement for --instrepo is temporary until fedup is completely integrated in to the F18 build process.
Seems like this is fixed in 0.7.1, so...