* Kan-Ru Chen <kos...@debian.org>, 2011-09-14, 11:29:
[Please always Cc me]
[Done]
${shlibs:Depends} should be set by debhelper to the minimum version
required by this package upon version information from the library at
build time. If you are using a feature that is only available after
libvte9 1:0.28.1-2 but the dependency says 'libvte9 (>= 1:0.24.0)'
then it is a bug of libvte9 package.
That is, more or less, what's happening, so I'll move the bug to
libvte9. In case that takes a long time to fix should I manually
override the dependency?
Yes you can, just put the right version in Depends.
This is an excellent recipe to make the Release Team hate you, though.
However this means when building with older version of libvte one has
to manually adjust the Depends field as well.
Wait, you don't want to build your package against *older* versions. And
if you even can do that, then your build-depends is broken.
What is troublesome in such case is building against a *newer* version,
with potentially different SONAME. That's why you should never put
shared libraries you're linking against explicitly in Depends. If
anything, use Breaks for this purpose.
That said, #641123 really looks like a serious bug in vte.
--
Jakub Wilk
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110914104403.gb1...@jwilk.net
