[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: mplayer crash seriously with newer libogg



i'll explain..

the kernel are bad.. my kernel are x86 only 3.2.0 from wheeze

so i upgraded mplayer rebuild agains new libogg and goes bad.. then i upgrade mplayer sources and rebuild agains libogg (and several others new) and work fine

i send the report with and old due i very busy and the report script are very tedious 

On Sat, Mar 23, 2013 at 4:11 PM, Adam D. Barratt <adam@adam-barratt.org.uk> wrote:
On Sat, 2013-03-23 at 21:23 +0100, Dominik George wrote:
> Hi,

You need to mail the submitter if you expect replies / information from
them.

> this could either be fixed with a Breaks against older mplayer versions,
> but I recognize this is not preferred if the bug only affects incomplete
> upgrades to wheezy.
>
> If this were release critical, teh release team could set it
> wheezy-ignore, but I am lowering the severity to important because you
> seem to be a special case. First, you state that this only happens for
> *incomplete* upgrades and I assume this does not meet the criteria "most
> users".

Partial upgrades from stable to stable+1 are required to work (CC to
-release as I'm not entirely sure if this is explicitly documented,
despite having been the case for as long as I can remember). The reason
I'm not re-upgrading it straight away is:

> Second, your system strikes me odd:
>
> > Debian Release: testing/unstable
> >   APT prefers unstable
> >   APT policy: (900, 'unstable')
> > Architecture: amd64 (x86_64)
> > Shell:  /bin/sh linked to /bin/bash
> > Kernel: Linux 2.6.15-k8-3
>
> This system cannot even be squeeze, as squeeze has Linux 2.6.18.

No, squeeze has 2.6.26; lenny had 2.6.18. There's no requirement to use
Debian's kernel packages though. However, squeeze's libc6 won't install
on anything less than 2.6.18, so there does seem to be something
slightly strange.

Regards,

Adam




--
Lenz McKAY Gerardo (PICCORO)
http://qglochekone.blogspot.com

Reply to: