Description of problem: Current F17 compose process contains this exception in the critpath creation process: Traceback (most recent call last): File "./scripts/critpath.py", line 184, in <module> pkgs = expand_critpath(my, critpath_groups) File "./scripts/critpath.py", line 88, in expand_critpath group = my.comps.return_group(name[1:]) File "/usr/lib/python2.6/site-packages/yum/__init__.py", line 906, in <lambda> comps = property(fget=lambda self: self._getGroups(), File "/usr/lib/python2.6/site-packages/yum/__init__.py", line 793, in _getGroups if not repo.ready(): File "/usr/lib/python2.6/site-packages/yum/yumRepo.py", line 340, in ready return self.repoXML is not None File "/usr/lib/python2.6/site-packages/yum/yumRepo.py", line 1462, in <lambda> repoXML = property(fget=lambda self: self._getRepoXML(), File "/usr/lib/python2.6/site-packages/yum/yumRepo.py", line 1458, in _getRepoXML raise Errors.RepoError, msg yum.Errors.RepoError: Cannot retrieve repository metadata (repomd.xml) for repository: critpath-repo-i386. Please verify its path and try again http://kojipkgs.fedoraproject.org/mash/branched-20120220/logs/critpath.log Reported against mash as per nirik's recommendation.
So now I know more. The traceback indicates that critpath.txt is not created. That means that none of the links mentioned here [1] works. Since we need to know which packages are in critpath to be able to consider release blockers I'm marking this as F17 Beta blocker. [1] http://fedoraproject.org/wiki/Critical_path_package#Where_can_I_find_the_critical_path.3F
This is not in mash - it's not actually in any packages we ship. It's a bug in the compose scripts, as a result of: http://lists.fedoraproject.org/pipermail/announce/2012-February/003040.html In any case, fixed.
Bill, it doesn't seem to be fixed. I've opened a rel-eng ticket to follow up on that issue: https://fedorahosted.org/rel-eng/ticket/5095
Hooray for multiple bugs with the same symtpoms. Fixed.