Am Montag, den 25.03.2013, 10:24 +0100 schrieb Reinhard Tartler: > Besides having libavcodec54 being replaced with libavcodec-extra-54 > (the latter is binary compatible with the former, but provides more > functionality, hence the "-extra-"), what exact problems do you > experience?
Does anyone have in idea why this happens? We had a similar issue in #702377, but this was caused by faulty shlibs information in a previous libav revision. What has gone wrong in the current one? -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
