#5095 critpath.txt not created
Closed: Fixed None Opened 12 years ago by kparal.

This is about following bug:
https://bugzilla.redhat.com/show_bug.cgi?id=795478

{{{
Using URL file:///mnt/koji/mash/branched-20120227/development/17/$basearch/os
Expanding critical path for i386
expanding @core
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
}}}

Even though Bill said "fixed", it doesn't seem to be fixed:
http://kojipkgs.fedoraproject.org/mash/branched-20120227/logs/critpath.log


A tag needs updated in git, fixed.

Metadata Update from @kparal:
- Issue set to the milestone: Fedora 17 Alpha

7 years ago

Login to comment on this ticket.

Metadata