FS#10793 - Motion testing is not compiled with ffmpeg

Attached to Project: Arch Linux
Opened by Venky (venky80) - Monday, 30 June 2008, 23:37 GMT
Last edited by Paul Mattal (paul) - Tuesday, 01 July 2008, 16:52 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To Paul Mattal (paul)
Architecture All
Severity High
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:


Additional info:
* package version(s)
3.2.10.1-1
* config and/or log files etc.


Steps to reproduce:
This task depends upon

Closed by  Paul Mattal (paul)
Tuesday, 01 July 2008, 16:52 GMT
Reason for closing:  None
Additional comments about closing:  motion is no longer in testing, motion in extra should be fixed, and new builds of motion in testing against newer ffmpegs will be built once a patch is found
Comment by Paul Mattal (paul) - Tuesday, 01 July 2008, 15:20 GMT
Confirmed. I'll try another build. I didn't change anything, so I'm not sure why it builds fine against the old ffmpeg and seems to ignore the new one.
Comment by Paul Mattal (paul) - Tuesday, 01 July 2008, 16:48 GMT
Looks like it can't find the header files in their new locations, /usr/include/libavformat, etc.

I imagine motion will have to be patched to do this. I have not yet discovered such a patch, but will look further into finding/writing one.
Comment by Paul Mattal (paul) - Tuesday, 01 July 2008, 16:51 GMT
Since I have removed motion from testing, and compiled the new version properly in extra against the ffmpeg in extra, I'm going to close this bug. When we figure out how motion gets patched to move forward with new ffmpegs, then there'll be a new package in testing built against the new ffmpeg.

Loading...