Comment 4 for bug 735369

On Saturday 02 April 2011 02:23:21 Clint Byrum wrote:
> Kern, does this mean that there is an explicit fix in the code of 5.2.0
> that will make this problem go away on Qt 4.6.2 ?

There have been a very large number of changes to bat from 5.0.x to 5.2.0,
including new features, bug fixes, and particularly seg fault fixes. I am
sorry, I don't remember the specifics, and since I did not explicitly
reproduce the reported bug, I am not sure there is an explicit fix, but I
think so.

>
> While I do think we should put 5.2.0 in backports when it arrives, if
> the fix is simple it might be worth patching 5.0.1 so it works in lucid.

There were a lot of changes, and I believe we have a significant number in the
Director too, so any backporting might not be easy. You are free to try
backporting but it is not something that I am personally going to do.

>
> This one is really hard to confirm as I don't have any files to restore
> in my test bacula. Is there a shorter test case?

I don't know as I haven't explicitly reproduced the reported bug.

>
> I'm going to mark this as Incomplete, pending a shorter test case and/or
> answers from Kern. If its too hard to test, and/or too hard to fix in
> lucid, it might just have to be a "Won't Fix".

OK. I am not sure what your procedure is -- it might be good to note "fixed
in 5.2.x" providing that is really the case.
* Changed in: bacula (Ubuntu)
> Status: Incomplete => Confirmed