So in Debian, all the packages in testing are now built against libav11 AFAICT. I (as a user) hope we can still get libav11 for Utopic.
In case this helps with your decision, these are the packages in sid which are not built against libav11 (yet?): - bino (unrelated to libav, some gettext related version mismatch) - gnash (probably unrelated, FTBFS on armel because armel has std::future issues, and FTBFS on mips for whatever reason) - gstreamer0.10-ffmpeg (FTBFS since libav9) - jitsi (unrelated, complains about invalid -d command line option for apt … ?!) - mrpt (there was no attempt to build against libav11 for any main arch yet, since there seem to be unrelated build issues on some arches. Building on alpha architecture at ports.debian.org against libav11 succeeded recently.) - taoframework (language bindings that need updating for libav9+. Upstream probably cared about ffmpeg only and is dead now anyway.) - visp (probably unrelated, test suite failure on powerpc) - zoneminder (FTBFS since libav10 at least, still using CODEC_ID_*) I'm not sure if Ubuntu carries any additional packages that would fail to build against libav11. Also not sure about the current Ubuntu state of the packages I mentioned. Maybe some of them need to be dropped from the archive. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1360026 Title: Libav11 for Utopic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1360026/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
