On Thu, Mar 22, 2012 at 1:30 AM, John David Anglin <dave.ang...@bell.net> wrote: > On 20-Mar-12, at 9:54 PM, Andres Mejia wrote: > >> This issue is common if you're using the libav-extra libraries. It's >> likely a broken symlink from your *.so files. > > > I don't think so. Updating libgcrypt11 to 1.5.0-3 fixes the build. > Somehow, > it eliminates the dependency.
I'm not sure if I understand your message. Does this mean that there is nothing to do in libav and we can close this bug? -- regards, Reinhard -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
