Have also attempted to back level and patch version 3.2.27 but that fails as-well :(
-- Thanks, Phil ----- Original Message ----- > Really striking out on this so help from the experts would be very > much appreciated :) > -- > Thanks, Phil > > ----- Original Message ----- > > On Mon, 2012-01-30 at 16:39 +0000, Phil Daws wrote: > > > I finally have a complete patch set that applies cleanly but when > > > I > > > try and build a brand new vserver I get the following error: > > > > > > Traceback (most recent call last): > > > File "/usr/bin/yum", line 29, in <module> > > > yummain.user_main(sys.argv[1:], exit_code=True) > > > File "/usr/share/yum-cli/yummain.py", line 276, in user_main > > > errcode = main(args) > > > File "/usr/share/yum-cli/yummain.py", line 129, in main > > > result, resultmsgs = base.doCommands() > > > File "/usr/share/yum-cli/cli.py", line 434, in doCommands > > > self._getTs(needTsRemove) > > > File "/usr/lib/python2.6/site-packages/yum/depsolve.py", line > > > 99, > > > in _getTs > > > self._getTsInfo(remove_only) > > > File "/usr/lib/python2.6/site-packages/yum/depsolve.py", line > > > 111, in _getTsInfo > > > self._tsInfo.setDatabases(self.rpmdb, pkgSack) > > > File "/usr/lib/python2.6/site-packages/yum/__init__.py", line > > > 890, in <lambda> > > > rpmdb = property(fget=lambda self: self._getRpmDB(), > > > File "/usr/lib/python2.6/site-packages/yum/__init__.py", line > > > 544, in _getRpmDB > > > persistdir=self.conf.persistdir) > > > File "/usr/lib/python2.6/site-packages/yum/rpmsack.py", line > > > 218, > > > in __init__ > > > version_path = os.path.normpath(cachedir + '/version') > > > TypeError: unsupported operand type(s) for +: 'NoneType' and > > > 'str' > > > > > > Is there anybody who wishes to try and help resolve this with me > > > please ? Would love to get it working on CentOS 6. > > > > I don't know a thing about python or yum but I'm guessing something > > in > > yummain.py is trying to concatenate strings and the type definition > > of > > one of them has accidentally gone out of scope or gone missing in > > the > > patch process perhaps? - John > > > > >Received on Thu Feb 2 13:23:10 2012