On 10/30/2012 10:05 PM, Chris Bannister wrote:
> On Tue, Oct 30, 2012 at 09:12:45PM -0400, H.S. wrote:
>> On 10/21/2012 08:12 AM, Chris Bannister wrote:
>>> On Sat, Oct 20, 2012 at 10:12:45PM -0400, H.S. wrote:
Here is what appears to have changed since my last night's upgrade:
On Tue, Oct 30, 2012 at 09:12:45PM -0400, H.S. wrote:
> On 10/21/2012 08:12 AM, Chris Bannister wrote:
> > On Sat, Oct 20, 2012 at 10:12:45PM -0400, H.S. wrote:
> >>
> >> Here is what appears to have changed since my last night's upgrade:
> >>
> >> [UPGRADE] ffmpeg:amd64 7:0.11.1-dmo5 -> 7:1.0-dmo1
On 10/21/2012 08:12 AM, Chris Bannister wrote:
> On Sat, Oct 20, 2012 at 10:12:45PM -0400, H.S. wrote:
>>
>> Here is what appears to have changed since my last night's upgrade:
>>
>> [UPGRADE] ffmpeg:amd64 7:0.11.1-dmo5 -> 7:1.0-dmo1
>> [UPGRADE] gstreamer0.10-ffmpeg:amd64 0.10.13-5 -> 1:0.10.13-dm
On Sat, Oct 20, 2012 at 10:12:45PM -0400, H.S. wrote:
>
> Here is what appears to have changed since my last night's upgrade:
>
> [UPGRADE] ffmpeg:amd64 7:0.11.1-dmo5 -> 7:1.0-dmo1
> [UPGRADE] gstreamer0.10-ffmpeg:amd64 0.10.13-5 -> 1:0.10.13-dmo1
> [UPGRADE] libxine2-ffmpeg:amd64 1.2.2-4 -> 1:1.
On 10/20/2012 10:09 PM, H.S. wrote:
>>From my yesterday's logs, here is what I was getting when the camera worked:
> Oct 18 09:40:28 red motion: [0] Processing thread 0 - config file
> /etc/motion/motion.conf
> Oct 18 09:40:28 red motion: [0] Motion 3.2.12 Started
> Oct 18 09:40:28 red motion: [0]
>From my yesterday's logs, here is what I was getting when the camera worked:
Oct 18 09:40:28 red motion: [0] Processing thread 0 - config file
/etc/motion/motion.conf
Oct 18 09:40:28 red motion: [0] Motion 3.2.12 Started
Oct 18 09:40:28 red motion: [0] ffmpeg LIBAVCODEC_BUILD 3482368
LIBAVFORMAT_B
6 matches
Mail list logo