fedora-packager-0.4.2.3-1.fc13.noarch

$ fedpkg -v build --scratch
Creating module object from /home/roland/redhat/stg/glibc
Traceback (most recent call last):
File "/usr/bin/fedpkg", line 903, in
args.command(args)
File "/usr/bin/fedpkg", line 297, in build
mymodule.init_koji(args.user, kojiconfig)
File "/usr/lib/python2.6/site-packages/pyfedpkg/init.py", line 980, in init_koji
defaults['serverca'])
File "/usr/lib/python2.6/site-packages/koji/init.py", line 1458, in ssl_login
sinfo = self.callMethod('sslLogin', proxyuser)
File "/usr/lib/python2.6/site-packages/koji/init.py", line 1503, in callMethod
return self._callMethod(name, args, opts)
File "/usr/lib/python2.6/site-packages/koji/init.py", line 1528, in _callMethod
return proxy.getattr(name)(*args)
File "/usr/lib64/python2.6/xmlrpclib.py", line 1199, in call
return self.__send(self.__name, args)
File "/usr/lib64/python2.6/xmlrpclib.py", line 1489, in __request
verbose=self.__verbose
File "/usr/lib64/python2.6/xmlrpclib.py", line 1235, in request
self.send_content(h, request_body)
File "/usr/lib64/python2.6/xmlrpclib.py", line 1349, in send_content
connection.endheaders()
File "/usr/lib64/python2.6/httplib.py", line 892, in endheaders
self._send_output()
File "/usr/lib64/python2.6/httplib.py", line 764, in _send_output
self.send(msg)
File "/usr/lib64/python2.6/httplib.py", line 723, in send
self.connect()
File "/usr/lib/python2.6/site-packages/koji/ssl/SSLCommon.py", line 108, in connect
self.sock.connect((self.host, self.port))
File "", line 1, in connect
socket.error: [Errno 110] Connection timed out
$

The stg koji server is apparently down, which is a problem. But also fedpkg -v doesn't even tell me what the equivalent koji command it's running is, which would be nice. (I'm used to "make -n build" in the old system.) And for a server or network problem, it really should not be spitting a backtrace and triggerring an abrtd record.