up vote 4 down vote favorite

I am using Centos 7.1 The yum groupinstall commands are failing. As root I did a 

yum group list

command. This returned various output with the following: "There is no installed groups file."

Is it possible for yum groupinstall to work without a groups file? I think my systems administrator won't allow me to install such a file. If it is mandatory for yum groupinstall, how do I install a groups file?

share|improve this question
  • yum grouplist -v to the standard CentOS repositories returns the available groups for me. This yields the "no installed" message, though, if I only connect to my local repository. – JRFerguson Dec 2 '15 at 19:34
  • I ran yum grouplist -v. It didn't seem to show available groups. Is the "...no installed..." message a reference to something that needs to be fixed on the repo server? The logs for the yum commands don't pick up anything (even with debug level set at 10). Is a local repository a non-Internet repo server? Based on further investigation I think there is some .gz file of an XML file that I need to update (either on the repo server or the client server that I am running the yum command on). – Kiran Dec 3 '15 at 0:07
up vote 2 down vote

Groups in yum are defined by the repositories themselves.

If yum group list does not list any groups, it means none of the enabled yum repositories have groups defined.

Groups in yum are generally defined in a /...-comps.xml file (or similar, where ... is a random string) within the repodata directory of the repo.

If the repo was created manually, they may have forgotten to include a group file (or at least, forgot to use the one that comes with CentOS).

createrepo -g ${GROUPS_FILE} .

Will create a repo in the current directory, using the file defined by ${GROUPS_FILE}.

If the repo already exists and you simply want to add the groups file to it, you can use --update.

createrepo -g ${GROUPS_FILE} --update .

createrepo will copy the groups file into the repodata directory, so you don't have to worry about the original copy.

share|improve this answer
up vote 1 down vote

You can work around this by copying the repodata from the original ISO/DVD to your new repo location under the same directory.

share|improve this answer
up vote 0 down vote

Try running

yum groups mark convert

Could be related to this bug

share|improve this answer
  • Thank you very much, however, I do have questions. Will this break anything or cause issues? I'm not the only person using the Linux server. Is there any back out plan to reverse what this does in case there is a problem? – Kiran Dec 3 '15 at 0:16
  • As per the bug info, the issue may be fixed in 7.3. I think you should work with your sys admin and test on a test host before trying this on prod host, where it could effect others. AFAIK running above command should not cause any issue. However your issue might not be related to that message. Can you post yum repolist and yum groupinstall command outputs? – VenkatC Dec 3 '15 at 1:03
  • This will simply flag groups as installed if you have all their packages installed. It still looks up the defined groups. You can also redefine groups on your local-machine using yum group mark packages, but again that only flags installed packages as part of a group. – Centimane May 31 '17 at 14:22

Your Answer

 

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.