Yum install typeerror iterable argument required

Copy link. Can you give me some suggestions? Thank you! There was error saying-TypeError: argument of type 'NoneType' is not iterable. Follow more details at - dvf Umesh2Patel mentioned this issue Jun 20, DId you found the solution? This worked for me aswell. The optional "hidden" argument will also list groups marked as not being "user visible". If you pass the -v option, to enable verbose mode, then the groupids are displayed.

It is worth pointing out that packages can be in more than one group, so " group install X Y " followed by " group remove Y " does not do give you the same result as " group install X ". The " group info " is used to give the description and package list of a group and which type those packages are marked as.

Is used to enter the ' yum shell ', when a file name is specified the contents of that file is executed in yum shell mode. Is used to list packages providing the specified dependencies, at most one package is listed per dependency. Is used to install a set of local rpm files. If required the enabled repositories will be used to resolve dependencies.

Note that the install command will do a local install, if given a file name. This option is maintained for legacy reasons only. Is used to update the system by specifying local rpm files. Only the specified rpm files of which an older version is already installed will be installed, the remaining specified packages will be ignored.

Note that the update command will do a local update, if given a file name. Will reinstall the identically versioned package as is currently installed. This option does not work for " installonly " packages, like kernels. Will try and downgrade a package from the version currently installed to the previously highest version or the specified version. The depsolver does not necessarily work, but if you specify all the packages it should work and thus all the simple cases work.

Also, this does not work for " installonly " packages, like kernels. The downgrade option operates on groups, files, provides, filelists, and rpm files, like the " install " command. Produces a list of all dependencies and what packages provide those dependencies for the given packages.

As of 3. Produces a list of configured repositories. The default is to list all enabled repositories. If you pass -v for verbose mode, more information is listed. If the first argument is ' enabled ', ' disabled ' or ' all ' then the command lists those types of repositories. You can pass repo id or name arguments, or wildcards which to match against both of those. However, if the id or name matches exactly, then the repo is listed even if you are listing enabled repositories and it is disabled.

For non-verbose mode, the last column also displays the number of packages in the repo and if there are any user specified excludes the number of packages excluded. One last special feature of repolist , is that if you are in non-verbose mode then yum ignores any repo errors and output the information it can get Eg. Produces a "version" of the rpmdb , and of the enabled repositories if "all" is given as the first argument. You can also specify version groups in the version-groups config file.

If you specify -v for verbose mode, more information is listed. Note that this rpmdb version is now also used significantly within yum especially in the yum history. The version command now shows "groups" of packages as a separate version, and so takes sub-commands: " version grouplist " - List the defined version groups.

The list can be passed the keyword "all" to list all the transactions. The packages-list command takes a package with wildcards, as in Specifying package names. While the rollback command will undo all transactions upto the point of the specified transaction.

For example, if you have 3 transactions, where package A; B and C where installed respectively. Then " undo 1 " will try to remove pacakge A, " redo 1 " will try to install package A if it is not still installed , and " rollback 1 " will try to remove packages B and C. Please be sure to follow the download instructions for your platform and use tgsetup.

If this does not work for you, use -f instead of -i :. Please note that this is not supported and several things may go wrong, which you need to fix manually. In order to get TurboGears running, you need to have the eggs properly installed.

There are two options for doing this:. A non-root installation preserves all of your existing Python setup, but is more complex. If you have concerns that your system might not like different versions of the libraries, this is the safe route to take. Please see the TurboGears Uninstallation page for information on how to install packages. Safety in numbers: crowdsourcing data on nefarious IP addresses. Featured on Meta. New post summary designs on greatest hits now, everywhere else eventually.

Related Hot Network Questions. Question feed. Stack Overflow works best with JavaScript enabled. Accept all cookies Customize settings.