Hi,
I'm the admin of the nic.funet.fi fedora and epel mirrors. Some user tweeted a while ago that our Epel mirror served something in .xml instead of compressed .xml claiming that it broke yum. On a closer look my mirror seems to be in sync with the master mirror. There could be some delay since I currently source the mirror via mirrorservice.uk since heanet.ie had once repodata issues. Anyway, at least now my mirror is same as the master, on Friday it was one version back and I increased checks from three to five times a day. Even then I tried yum against it and had no problems. Maybe there was some transient problem with the repodata being rsynced while it was changing or something.
Today I notice that there's one .bz2 file and another plain .xml file. Other sites seem to have those too. Is that intentional or some side effect of something and is there need to do something about it?
Cheers,
Harri Salminen
nic.funet.fi coordinator
rsync -v rsync://dl.fedoraproject.org/fedora-epel/7/x86_64/repodata/ ---------------------------- Fedora Master Mirror Servers ---------------------------- If you are using bare rsync to sync content, please stop and take a look at https://pagure.io/quick-fedora-mirror.
See http://fedoraproject.org/wiki/Infrastructure/Mirroring for further instructions. ----------------------------
receiving file list ... done drwxr-xr-x 8192 2018/09/02 07:32:53 . -rw-r--r-- 961675 2018/09/02 07:32:53 14a9489b7285b69f776b1ede0d0c53dc3fdfdb39c3a85b43253fa4fc1ef9d554-updateinfo.xml.bz2 -rw-r--r-- 2330384 2018/09/02 07:31:11 499f51df0ae8be5716b4eea8e4a085d853e313f35d1eb5f5191ee3493e7d7efe-other.xml.gz -rw-r--r-- 373535 2018/09/02 07:24:20 5307666922f0cd10058b04791f3f596cfcaab48df6fdd6cf847f349bd455e0bd-comps-Everything.x86_64.xml -rw-r--r-- 1487 2018/09/02 07:31:23 779bdc0a669009edc77b846310290c1a8631507c0e9b20eb55ba223c165250a1-prestodelta.xml.gz -rw-r--r-- 10721841 2018/09/02 07:31:11 7abb01e399c21f1aa97b86c831bfa285901f2e092b4b90da1b90d3c388ca7309-filelists.xml.gz -rw-r--r-- 3735366 2018/09/02 07:31:11 8488d0b90acd5bc933f169e3922acfc91a56db5b3b2f57f5dca5e267093bda6f-primary.xml.gz -rw-r--r-- 89658 2018/09/02 07:31:11 c05b9b116fbeb56969f8572766a459cf23c8887335f16611b097073726a45f77-comps-Everything.x86_64.xml.gz -rw-r--r-- 3306 2018/09/02 07:32:53 repomd.xml
On 09/03/2018 06:59 AM, Harri Salminen wrote:
Hi,
I'm the admin of the nic.funet.fi fedora and epel mirrors. Some user tweeted a while ago that our Epel mirror served something in .xml instead of compressed .xml claiming that it broke yum. On a closer look my mirror seems to be in sync with the master mirror. There could be some delay since I currently source the mirror via mirrorservice.uk since heanet.ie had once repodata issues. Anyway, at least now my mirror is same as the master, on Friday it was one version back and I increased checks from three to five times a day. Even then I tried yum against it and had no problems. Maybe there was some transient problem with the repodata being rsynced while it was changing or something.
For epel, there is a uncompressed xml file: the comps file. It's also provided as a gzipped file. The repodata setup started out with some specific files, then has been slowly added to over the years in such a way that new files are added, but old formats are never changed so very old yum versions can get the data they need and newer ones can get more.
if it was the comps file they saw, thats normal.
Today I notice that there's one .bz2 file and another plain .xml file. Other sites seem to have those too. Is that intentional or some side effect of something and is there need to do something about it?
It's just that its been added to over the years, some of the newer files are bz2, some of the older ones are gz, etc. In order to fix that up, it would need to break all existing yum versions, which is... not desireable.
kevin
mirror-admin@lists.fedoraproject.org
-
Harri Salminen -
Kevin Fenzi