Comment 7 for bug 1349634

Hi, many thanks for looking into this. You guys are the best :)

Unfortunately I'm caught up with over works at the moment and won't be able to test the solution implemented in the master branch.

To answer some of your questions:

>> Might not have worked for you because the job didn't actually get deleted before the update because there was a bug with the delete command?
That might have been the case, but there was no error message whatsoever when deleting or updating as you can see in the output in the bug's description.

A theory I had was that the jobs generated under different versions of the software would result in an 'unclean' state where the jobs are not deleted properly which causes the new version of JJB to think that it is still present.
Did we delete function get updated in any way?

>> If you were to upgrade to 0.8.0 and test again, does the problem persist?
Yes it persisted, that was one of the tests I did a few months ago.

>> If so, can you provide info on what package you are using or how you are downgrading/upgrading.
Like I mentioned, I won't be able to do that before next week unfortunately.