traceback with 20021011 current snapshot

"Barry K. Nathan" <[email protected]>
Newsgroups gmane.network.up2date.current.devel
Message-ID <[email protected]>
This is a 100% reproducible traceback when rebuilding my
"redhat-linux-i386-6.2" channel. It includes all of the original RH
6.2 packages and all of the errata.

FWIW, it's perfectly OK with me if Current drops RH 6.2 support -- I plan
to get the 6.2 machines under my administrative control upgraded to 7.3
anyway. Nonetheless, I thought you might want to know about this bug.

If you need any more info, feel free to ask -- as I said, this is 100%
reproducible.

Traceback (innermost last):
  File "/usr/sbin/cadmin", line 325, in ?
    main()
  File "/usr/sbin/cadmin", line 174, in main
    newchan.close()
  File "/usr/share/current/channel.py", line 263, in close
    self._writeGetObsoletesFile()
  File "/usr/share/current/channel.py", line 238, in _writeGetObsoletesFile
    str = xmlrpclib.dumps(olist, methodresponse=1)
  File "/usr/lib/python1.5/site-packages/xmlrpclib.py", line 505, in dumps
    data = m.dumps(params)
  File "/usr/lib/python1.5/site-packages/xmlrpclib.py", line 264, in dumps
    self.__dump(v)
  File "/usr/lib/python1.5/site-packages/xmlrpclib.py", line 277, in __dump
    f(self, value)
  File "/usr/lib/python1.5/site-packages/xmlrpclib.py", line 307, in dump_array
    self.__dump(v)
  File "/usr/lib/python1.5/site-packages/xmlrpclib.py", line 277, in __dump
    f(self, value)
  File "/usr/lib/python1.5/site-packages/xmlrpclib.py", line 307, in dump_array
    self.__dump(v)
  File "/usr/lib/python1.5/site-packages/xmlrpclib.py", line 275, in __dump
    raise TypeError, "cannot marshal %s objects" % type(value)
TypeError: cannot marshal <type 'None'> objects
Exception exceptions.TypeError: <exceptions.TypeError instance at 81f3958> in <method Channel.__del__ of Channel instance at 819d238> ignored

-Barry K. Nathan <[email protected]>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.