no group information downloaded

[SitWatchCloudRise]

Hi,
Thanks for the excellent work for the building the tool. However, the local repository mirror has no information about packages of the group. for example:

~]# yum groupinfo -v "Virtualization Platform"
Loading "fastestmirror" plugin
Loading "langpacks" plugin
Adding en_AU.UTF-8 to language list
Config time: 0.008
Yum version: 3.4.3
Setting up Package Sacks
Loading mirror speeds from cached hostfile
 * epel: fedora.uberglobalmirror.com
pkgsack time: 0.009
group time: 0.064

Group: Virtualization Platform
 Group-Id: virtualization-platform
rpmdb time: 0.000
 Description: Provides an interface for accessing and controlling virtualized guests and containers.

the debug shows that actual reposync command is as follows:
reposync --config=/tmp/y10k/yum.conf --repoid=centos-7-x86_64-os --norepopath --downloadcomps --download-metadata --arch=x86_64 --download_path=/data/yum/head/centos/7/os/x86_64

Could you please point out for me how could we fix?
Regards,

[cavaliercoder]

Thanks for reporting this. I've been working on this problem actually, but didn't realise it effected others also.

I'm having some trouble decomposing how group files work in various version of Yum. Downloading the group info is easy, but publishing it in the mirror is weird.

I'll keep the issue updated as I progress.

[dgoo2308]

any progress?

it looks like ..-c7-x86_64-comps.xml.gz is created in a directory above repodata, and is not present in the repomd.xml.

I got it working by:

1. a deleting the repodata directory
2. rerun the create repo with:

createrepo --database --checkts --cachedir=/mirror/reposync/tmp/cache/repo/centos7-os --workers=8 --profile --verbose --groupfile /mirror/centos/7/os/x86_64/comps.xml /mirror/centos/7/os/x86_64

note :

1. no --update
2. --groupfile /mirror/centos/7/os/x86_64/comps.xml

result:

the ..-c7-x86_64-comps.xml.gz is created in repodata and is cataloged in repomd.xml.

[SitWatchCloudRise]

so far, I use a script to run "createrepo --update ...." for each repo every time after the synchronization.
It is not perfect solution. I am still waiting for the update, or, maybe I will have a try when we are not that busy.