On Tue, Oct 25, 2005 at 04:43:18PM +0200, Andreas Henriksson wrote: > I build-depend on any variant of libgd2 and all dependencies are automatically > calculated/added (thus the package ends up with a dependency on the variant of > libgd that was installed to satisfy the build-dependency). > I'll look into manually adding the correct libgd dependencies before the > next upload.
Hm, yes... your: Build-Depends: ..., libgd2-dev | libgd2-xpm-dev | libgd2-noxpm-dev | libgd-dev, ... seems to result in: Depends: ..., libgd2-xpm (>= 2.0.33), ... When I have a look at the dvipng source, they don't do anything manually about their dependencies (at least as far as I can see) and their: Build-Depends: ..., libgd2-noxpm-dev, ... results in: Depends: ..., libgd2-noxpm (>= 2.0.33) | libgd2-xpm (>= 2.0.33), ... I don't know why is this. However, when I just install libgd2-noxpm-dev on my system and build bandwidthd from source, I get: Depends: ..., libgd2-noxpm (>= 2.0.33) | libgd2-xpm (>= 2.0.33), ... So, either depending on libgd2-noxpm-dev only or just even installing libgd2-noxpm-dev on your build machine should fix the issue :) regards Mario -- Whenever you design a better fool-proof software, the genetic pool will always design a better fool.
signature.asc
Description: Digital signature
