Hi Am 22.10.2015 um 10:44 schrieb IOhannes m zmölnig (Debian/GNU): > dear libsigc++ maintainers, > > On 2015-10-22 10:24, Jaromír Mikeš wrote: >>>> i also just noticed that libsigc++-2.0_2.6.1-3 (uploaded to >>>> unstable *yesterday*) now includes the "-std=c++11" flag in >>>> their pkg-config CFLAGS, exactly to prevent build failures like >>>> ours. so we can probably drop 05-C++11.patch again. >> I just updated pbuilder environment ( I am doing often ) and now it >> is fine and build. :/ Should we tighten build deps to >> libsigc++-2.0_2.6.1-3 ? > > while fixing the bug mentioned in the subject, we noticed that you > already provide a fix on your side. thanks. > > now we wonder (in the light of making backports easy) whether we > should use versioned build-deps on libsigc++ to get your fix, or > whether you would recommend to not to (e.g. because only a few > selected versions of libsigc++ are depending on C++11, and that > version will drop out of testing soon, so no Debian release (and > hopefully the same is true for derivatives) will contain the > problematic versions.
The "fix" in libsigc++2.0 is more a hack then a real fix. It was added since the change in libsigc++2.0/glibmm2.4/gtkmm3.0 would have made ~90 packages RC buggy. It's not a proper fix and not one I want to keep in stretch. So, if you've already fixed your package to build with the newer libsigc++2.0 by switching to -std=c++11, please keep that change. In most of the cases it should be as simply as passing that via CFLAGS in debian/rules. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
_______________________________________________ pkg-multimedia-maintainers mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
