Quoting Jakub Wilk (jwilk@debian.org):
> Package: python-fontforge
> Version: 0.0.20110222-2
> Severity: important
> User: debian-python@lists.debian.org
> Usertags: python2.7
>
> python-fontforge has only unversioned dependency on libfontforge1.
> This is of course insufficent to ensure that python-fontforge and
> libfontforge1 can be only installed together if they were build
> against the same version of Python. (Please note that different
> version of Python are not binary-compatible!)
>
> Please consider using "Depends: ..., libfontforge1 (=
> ${binary:Version})".
Hello Jakub,
Thanks for reporting this.
I fixed this one as it was easy and obvious. I can' do much for the
other bug you commented on (#575753), I'm sorry for that but it goes
beyond my skills in PythonLand (that are close to zero).
>
> BTW, libgdraw4 has similar problem, although only because it's
> gratuitously linked with libpython2.X:
> | dpkg-shlibdeps: warning: dependency on libpython2.6.so.1.0 could be avoided if "debian/libgdraw4/usr/lib/libgdraw.so.4.0.10" were not uselessly linked against it (they use none of its symbols).
Hmmm, that probablycomes from upstream's build process, I guess, as we
don't explicitely declare the dependency.
Attachment:
signature.asc
Description: Digital signature