Package: libconsole-bridge0.2v5 Followup-For: Bug #811498 Hey Jochen:
Thanks for the report. You are right, I broke the new update. My intention was not to change package and library name since upstream did not change the API/ABI (I'm working with them to keep a sane semantic versioning scheme). I did that for the package but not for the library, sorry for that. I believe that we can workaround on this problem by creating a symlink from libconsole_bridge.so.0.3 to a new libconsole_bridge.so.0.2. This way we can respect the upstream release as-it but keep the dependencies stable in debian which depends on the 0.2 lib. Jochen, do you see any problem with this? or do you have a better idea to solve the situation keeping in mind that there is no ABI/API change in the new 0.3.0 version? Thanks. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.13.0-74-generic (SMP w/8 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages libconsole-bridge0.2v5 depends on: ii libc6 2.19-22 ii libgcc1 1:5.2.1-22 ii libstdc++6 5.2.1-22 libconsole-bridge0.2v5 recommends no packages. libconsole-bridge0.2v5 suggests no packages. -- no debconf information -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
