Bug#802365: sooperlooper: FTBFS: sigc++-2.0 requires -std=c++11

[IOhannes m zmölnig (Debian/GNU)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

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.

thanks for your thoughts.

fgmasdr
IOhannes
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJWKKIAAAoJELZQGcR/ejb4dkQP/jdwjvOTQ6DUoURZ+SvlN6of
VvYSJ+aAmTTMRLAw1BkYcJ9Ugyvw0QryqpJu+0XbbqIwvPO+URSDjroId3fPariu
o+EJ85793xBAdw/c5XtGjnsMKQAGhxEZ63BvAFP7DKWdFZlEG9i+6XRZAUYWR8vU
U8UO7A2IGHKeDl6DjKS/vxaotSLOxMJAoKI1RQg6r3O+CYr+nMW3nBlqxOmhzFW3
Fi9t4V94PutfgRLzdRj6SvvvJoeMMPJJb5EYNPU8TURTUK0lneu2yplYe9yIgSkG
UqVp0Y0w3jXWEAhxCWO1owEzIebFo2jR2X63rLkL9Ams8P/XSWktgS7MZNEaIVnV
F6EPOF1RH80ZrPgVrzQCmibFhJ4XmjQGleBBbjs6UPl2dNkpTgLbUtwvX4kPMNKk
MKcecxaI1M6QMTeMKl+XIuW2bUPG+wGedXfkqDxRY6lkTOwGkitQOb+/A688yDpt
tjS1+DjGS4phj//VgbQSBUhUuDC9Gn6r4lVxuTBD+tTFFNPdqPKjKKJ7o2S6zhmn
CwNhEAedl2NBxVouGKc9nQ3GPf5+4kkPIaSTfVlGM66c+OwTwiLWVk3F8fN9xsm6
Zk0xpUg5p8u701v7I1fQZxwfaI2ry87Un9piaXrYAT5OJ3OETUibCeP6r/yG/9wU
vO4azEeOWjyIdxukzOyV
=QvPN
-----END PGP SIGNATURE-----