Re: motion: problem finding codec
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:
>>>>
>>>> [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.2.2-dmo3
>>>> [UPGRADE] libavcodec54:amd64 7:0.11.1-dmo5 -> 7:1.0-dmo1
>>>> [UPGRADE] libavdevice54:amd64 7:0.11.1-dmo5 -> 7:1.0-dmo1
>>>> [UPGRADE] libavformat54:amd64 7:0.11.1-dmo5 -> 7:1.0-dmo1
>>>> [UPGRADE] libavutil51:amd64 7:0.11.1-dmo5 -> 7:1.0-dmo1
>>>>
>>>> Could this have broken motion?
>>>
>>> You said something "out of the blue" stopped motion working, when in
>>> fact it was an upgrade.
As you should have noticed, that is not my original post. The phrase you
are have repeated in the above quote was before the OP in time and I
have explained how it occurred. Starting right after the original post,
I have explained the sequence of events as I traced back my steps and
knew more. What else do you want me to do, go back in time and fix the
initial report? Sigh!
>
> Debian doesn't accept bug reports for third party software.
Your reasoning for this statement appears to be that you somehow have
evidence that the bug is in fact not in any debian package at all. What
made you to make the conclusion?
As far as I am concerned, at least for me it is premature to decide (as
I see, a premature statement can incite quite strong reactions from some
here, re. "out of the blue"). It is also likely that the bug is in fact
in the debian package, motion, that has been triggered by the third party.
So, thanks for your suggestions and sorry for any trouble.
--
Please reply to this list only. I read this list on its corresponding
newsgroup on gmane.org. Replies sent to my email address are just
filtered to a folder in my mailbox and get periodically deleted without
ever having been read.
Reply to: