This is an old bug dating back to rev 1.6.1 of mjpegtools but the damn thing is still broken. The fix is to add a extra parameter to images2mpg. my question is why has this problem not been fixed yet.
Please, reopen with the actual errors you get, emerge -pv mjpegtools and emerge --info output. "The damned thing is still broken" fails as bug description.
hold your horses...I'm doing a full backtrace. searching for what just went haywire. I've found that it actually is images2mpg that has the error it has to do with the -S 420mpeg2 option not being defined. I also found that this is a digikam bug. not a mjpegtools one... I just had a panic. I have found the fix...but my question is sill valid. why is a bug dating back to 2006 still present in digikam. I've fixed it now. I was just creating the diff to send.
Well, lets mark this as INVALID then and move to Bug 208133. :) Thanks.