While trying to debug another problem, I found that the /usr/bin/urlgrabber --debug or -d flag doesn't work. For example:
# urlgrabber -d ftp://download.fedora.redhat.com/pub/fedora/linux/core/updates/6/x86_64/radvd-1.0-1.fc6.x86_64.rpm kwargs: {} URL: ftp://download.fedora.redhat.com/pub/fedora/linux/core/updates/6/x86_64/radvd-1.0-1.fc6.x86_64.rpm FILE: None Traceback (most recent call last): File "/usr/bin/urlgrabber.orig", line 124, in ? main() File "/usr/bin/urlgrabber.orig", line 120, in main filename = urlgrab(url,filename=file,**kwargs) File "/usr/lib/python2.4/site-packages/urlgrabber/grabber.py", line 595, in urlgrab return default_grabber.urlgrab(url, filename, **kwargs) File "/usr/lib/python2.4/site-packages/urlgrabber/grabber.py", line 927, in urlgrab return self._retry(opts, retryfunc, url, filename) File "/usr/lib/python2.4/site-packages/urlgrabber/grabber.py", line 842, in _retry if DEBUG: DEBUG.info('attempt %i/%s: %s', AttributeError: 'int' object has no attribute 'info' It looks like this is because the /usr/bin/urlgrabber script does this: urlgrabber.grabber.DEBUG = DEBUG which makes urlgrabber.grabber.DEBUG an int instead of the object type expected by the logging code. Removing this line from /usr/bin/urlgrabber makes the error go away, and produces debug output again, but I'm not sure why the line was there in the first place, and what the consequences are of removing it. A minor issue, but I thought I'd report it while I'm at it. Thanks, Herbert. _______________________________________________ Yum-devel mailing list [email protected] https://lists.dulug.duke.edu/mailman/listinfo/yum-devel
