Package: libsigc++-2.0-dev
Version: 2.2.11-2
Severity: grave
Your package depends on libsigc++-2.0- (= 2.2.11-2) which is not
available. The following message from the build log gives a hint:
,
| dpkg-gencontrol: warning: Depends field of package libsigc++-2.0-dev: unknown
substitution
Am 15.02.2014 22:46, schrieb Sven Joachim:
Package: libsigc++-2.0-dev
Version: 2.2.11-2
Severity: grave
Your package depends on libsigc++-2.0- (= 2.2.11-2) which is not
available. The following message from the build log gives a hint:
,
| dpkg-gencontrol: warning: Depends field of
2014-02-15 23:01 GMT+01:00 Michael Biebl bi...@debian.org:
Am 15.02.2014 22:46, schrieb Sven Joachim:
Package: libsigc++-2.0-dev
Version: 2.2.11-2
Severity: grave
Your package depends on libsigc++-2.0- (= 2.2.11-2) which is not
available. The following message from the build log gives a
Am 15.02.2014 23:23, schrieb Bálint Réczey:
2014-02-15 23:01 GMT+01:00 Michael Biebl bi...@debian.org:
The symbols file looks broken as well:
libsigc-2.0.so.0 libsigc++-2.0-0c2a (= 2.0.2)
Why was the version hard-coded here instead of using #MINVER#?
I wanted to stay as close as possible to
2014-02-15 23:31 GMT+01:00 Michael Biebl bi...@debian.org:
Am 15.02.2014 23:23, schrieb Bálint Réczey:
2014-02-15 23:01 GMT+01:00 Michael Biebl bi...@debian.org:
The symbols file looks broken as well:
libsigc-2.0.so.0 libsigc++-2.0-0c2a (= 2.0.2)
Why was the version hard-coded here instead
5 matches
Mail list logo
