Bug#733362: NMU for gstreamer0.10, FTBFS due to changes in bison3
Manuel A. Fernandez Montecelo
manuel.montezelo at gmail.com
Tue Jul 29 21:03:23 UTC 2014
Control: tags -1 + pending
Hi,
I am preparing a NMU to fix the bugs above (see headers), with the fix
proposed by Tobias Hansen picking a patch from upstream, and with
immediate upload as per guidelines in [1] as soon as I get it to work
-- since they are FTBFS and severity serious, open for many months and
didn't receive any update from the maintainers.
There is gstreamer1.0 since a few months ago in unstable, and perhaps
is the one intended that packages use from now on, but many packages
still build-depend on this one.
Apart from the obvious problem of FTBFS for the architectures in which
it was built in the past, this is a problem for ports being added
recently (OpenRISC/or1k, ppc64el, ...) since they don't even have
older versions to rely on, and many packages depend on them, so it's
blocking a good portion of the archive to compile cleanly.
[1] http://www.debian.org/doc/manuals/developers-reference/pkgs.html#nmu
Cheers.
--
Manuel A. Fernandez Montecelo <manuel.montezelo at gmail.com>
More information about the pkg-gstreamer-maintainers
mailing list