As noted in bug #361509 motion does not compile correctly with the new linux-headers. A fix is in the svn-tree.
Created attachment 282395 [details] motion-9999.ebuild motion live ebuild, works for me with linux-2.6.39.3 and v4l enabled.
Created attachment 288617 [details] motion-9999.ebuild Updated ebuild in order to use new initd script. Also in removes stray $hack variable.
Created attachment 291137 [details, diff] motion-3.2.12-v4l-headers.patch
Created attachment 291139 [details] motion-3.2.12-r1.ebuild This is a quick patch to enable building the existing Motion 3.2.12 in Portage. It seems to work fine for me, on a 3.0 kernel. There's a patch to fix some of the headers in Motion, place this in the "files" directory under Motion's directory in Portage. Then, overwrite the existing 3.2.12-r1.ebuild file with this changed ebuild file (do a "diff" first, to see what changed). Then, do "ebuild digest" to digest the changes, then Motion should build just fine.
Works perfect! Thanks :-)
+*motion-3.2.12-r2 (10 Dec 2011) + + 10 Dec 2011; Samuli Suominen <ssuominen@gentoo.org> +motion-3.2.12-r2.ebuild, + +files/motion-3.2.12-workaround-v4l1_deprecation.patch: + Since motion doesn't separate v4l1 and v4l2 support, use the + libv4l1-videodev.h include from libv4l to allow succesful compilation of both + backends. This should be only temporary workaround since upstream has + separated the backends in version control. See bug 376225. this should do for now and things will only get better once upstream gets new version out.
*** Bug 463402 has been marked as a duplicate of this bug. ***
reopening this, since it's been another year+ with no motion release, we should really consider adding snapshot in tree now
How about adding the motion-9999 ebuild to the tree?
motion-9999 works great, can it be added to the tree?
(In reply to A. Person from comment #10) > motion-9999 works great, can it be added to the tree? imho, a snapshot version would be preferred, live version is vulnerable
It looks like the fix might make it into the main branch: http://sourceforge.net/mailarchive/message.php?msg_id=31699956
I'm closing this bug since an ebuild of version 4.0.1 of motion was already added to the git repository to address these security issues. We'll stick to maintaining official project releases rather than a live ebuild. As long as we keep up-to-date with the project releases and patches, legacy bugs shouldn't be much of a concern in the future.