Hi,

Has anyone ever seen a yum/depsolve-related error like this before in their *plague-0.5.0* build environment, and then tried *killing* the job that had caused it?   This was problem three of three which I had mentioned in my previous posts.   And it too had surfaced last week while we started stress-testing our buildsystem.   Actually, the error you see below in itself was *not* the problem (we knew how to fix that) -- rather, it was the fact that we were *unable* to kill the job (plague-client kill 204) that was responsible for causing the error.  
====== THE ERROR ======
204 (fuse-sshfs): Starting tag 'fuse-sshfs-1_6-4_ocrhel4' on target 'oc-rhel4-pre'
204 (fuse-sshfs): Requesting depsolve...
204 (fuse-sshfs): Starting depsolve for arches: ['x86_64', 'i386', 'i686'].
Exception in thread PackageJob: 204/fuse-sshfs:
Traceback (most recent call last):
  File "/usr/lib64/python2.3/threading.py", line 436, in __bootstrap
    self.run()
  File "/usr/share/plague/server/PackageJob.py", line 86, in run
    self._pkg_job.process()
  File "/usr/share/plague/server/PackageJob.py", line 753, in process
    if func():
  File "/usr/share/plague/server/PackageJob.py", line 618, in _stage_depsolve
    if self._arch_deps_solved(arch) == False:
  File "/usr/share/plague/server/PackageJob.py", line 562, in _arch_deps_solved
    except yum.Errors.PackageSackError, exc:
AttributeError: 'module' object has no attribute 'PackageSackError'

====== OUR FIX ======
We updated line 680 in the *die* method of the */usr/share/plague/server/PackageJob.py * module.   Here's the patch:


Again, can someone please review the fix..  We just want to make sure that it won't come back to *haunt* us later on / or possibly even be *masking* another problem.   Thank you.

-Joe