Stabilization should be postponed until after bug #665930 is resolved. Until the motion configure script is fixed, there's no way for the motion ebuild to properly handle situations where multiple MySQL client libraries exist on the system.
Can we assume that 4.0.1-r1 suffers from the same issue? If so, then this must not block ffmpeg-4 stabilisation.
Yes, 4.0.1-r1 suffers from the same issue, and depends on ffmpeg as well. Furthermore, bug #665930 deals with MySQL dependency resolution and not ffmpeg, so I don't think this bug should block ffmpeg-4 stabilization.
Why was the bug #665930 dependency removed?
(In reply to William Breathitt Gray from comment #3)
> so I don't think this bug should block ffmpeg-4 stabilization.
^ because ffmpeg-4 stabilisation depends on motion-4.1.1-r1 stabilisation.
x86 stable, closing