On Friday 30 September 2005 16:58, Jeff Pitman wrote: > Anyway, I just wanted to throw out an email to see if anyone has hit > this yet. ?I'll dig deeper into depsolve.py, resolveDeps() and see > what RPM is thinking in it's TS. I might have to probe deeper into > the pkgSack to see if it's getting corrupted, caching gone awry, or > something. It might be rpm-python's issue. It's coming right out of self.ts.check() and there seems to be no other manipulation. Could be pkgsack, rpm-python, and/or my stupid mistakes in packaging. Most likely a combination with the 3rd being the biggest factor. -- -jeff
