Hi all,
The repository metadata file for CentOS 6.2 (repomd.xml) contains a sha256 hash for the non-gzipped comps.xml file (<hash>-c6-x86_64-comps.xml), but the file is missing from the repository. According to repomd.xml, this file should exist:
http://mirror.linux.duke.edu/pub/centos/6.2/os/x86_64/repodata/3a27232698a26...
The corresponding file exists in the CentOS 6.1's repo (there's 8 files in the repodata directory for 6.1, but only 7 for 6.2). A simple "zcat badeded316fc87571779d92c5cde816fdc357646b84cb191c4611e05c981ffa1-c6-x86_64-comps.xml.gz
3a27232698a261aa4022fd270797a3006aa8b8a346cbd6a31fae1466c724d098-c6-x86_64-comps.xml"
on the master mirror would fix the problem, but someone may want to look into the root cause... I'd look myself but have no idea how the build system works and doubt the logs would be publicly available (happy to be educated/pointed in the right direction thou).
-- Dave
On Tue, Dec 20, 2011 at 9:47 PM, David Robinson zxvdr.au@gmail.com wrote:
Hi all,
The repository metadata file for CentOS 6.2 (repomd.xml) contains a sha256 hash for the non-gzipped comps.xml file (<hash>-c6-x86_64-comps.xml), but the file is missing from the repository. According to repomd.xml, this file should exist:
http://mirror.linux.duke.edu/pub/centos/6.2/os/x86_64/repodata/3a27232698a26...
The corresponding file exists in the CentOS 6.1's repo (there's 8 files in the repodata directory for 6.1, but only 7 for 6.2). A simple "zcat badeded316fc87571779d92c5cde816fdc357646b84cb191c4611e05c981ffa1-c6-x86_64-comps.xml.gz
3a27232698a261aa4022fd270797a3006aa8b8a346cbd6a31fae1466c724d098-c6-x86_64-comps.xml"
on the master mirror would fix the problem, but someone may want to look into the root cause... I'd look myself but have no idea how the build system works and doubt the logs would be publicly available (happy to be educated/pointed in the right direction thou).
The missing file (which I can confirm) is on the QA tree. So somehow it was lost in mirroring ??
Akemi
On 12/20/2011 11:47 PM, David Robinson wrote:
Hi all,
The repository metadata file for CentOS 6.2 (repomd.xml) contains a sha256 hash for the non-gzipped comps.xml file (<hash>-c6-x86_64-comps.xml), but the file is missing from the repository. According to repomd.xml, this file should exist:
http://mirror.linux.duke.edu/pub/centos/6.2/os/x86_64/repodata/3a27232698a26...
The corresponding file exists in the CentOS 6.1's repo (there's 8 files in the repodata directory for 6.1, but only 7 for 6.2). A simple "zcat badeded316fc87571779d92c5cde816fdc357646b84cb191c4611e05c981ffa1-c6-x86_64-comps.xml.gz
3a27232698a261aa4022fd270797a3006aa8b8a346cbd6a31fae1466c724d098-c6-x86_64-comps.xml"
on the master mirror would fix the problem, but someone may want to look into the root cause... I'd look myself but have no idea how the build system works and doubt the logs would be publicly available (happy to be educated/pointed in the right direction thou).
This file is on the master mirror and in the QA tree. It was not on one of the other mirrors due to an rsync error, which made it show up in a hit or miss way throughout the mirror infrastructure.
The faulty mirror has been corrected and is now updated.
This should sync out and be everywhere shortly.
Thanks, Johnny Hughes
On Wed, Dec 21, 2011 at 9:47 PM, Johnny Hughes johnny@centos.org wrote:
On 12/20/2011 11:47 PM, David Robinson wrote:
Hi all,
The repository metadata file for CentOS 6.2 (repomd.xml) contains a sha256 hash for the non-gzipped comps.xml file (<hash>-c6-x86_64-comps.xml), but the file is missing from the repository. According to repomd.xml, this file should exist:
http://mirror.linux.duke.edu/pub/centos/6.2/os/x86_64/repodata/3a27232698a26...
The corresponding file exists in the CentOS 6.1's repo (there's 8 files in the repodata directory for 6.1, but only 7 for 6.2). A simple "zcat badeded316fc87571779d92c5cde816fdc357646b84cb191c4611e05c981ffa1-c6-x86_64-comps.xml.gz
3a27232698a261aa4022fd270797a3006aa8b8a346cbd6a31fae1466c724d098-c6-x86_64-comps.xml"
on the master mirror would fix the problem, but someone may want to look into the root cause... I'd look myself but have no idea how the build system works and doubt the logs would be publicly available (happy to be educated/pointed in the right direction thou).
This file is on the master mirror and in the QA tree. It was not on one of the other mirrors due to an rsync error, which made it show up in a hit or miss way throughout the mirror infrastructure.
The faulty mirror has been corrected and is now updated.
This should sync out and be everywhere shortly.
Awesome, thanks!
-- Dave
-
Akemi Yagi -
David Robinson -
Johnny Hughes