Bug#374664: lablgtk2: FTBFS: Unsatisfiable Build-Depends on obsolete xlibs
Goswin von Brederlow wrote:
> Samuel Mimram <samuel.mimram@ens-lyon.org> writes:
>> Daniel Schepler wrote:
>>> Package: lablgtk2
>>> Version: 2.6.0-5
>>> Severity: serious
>>>
>>> From my pbuilder build log:
>>>
>>> ...
>>> Installing the build-deps
>>> -> Attempting to parse the build-deps : pbuilder-satisfydepends,v 1.28 2006/05/30 23:45:45 dancer Exp $
>>> -> Considering debhelper (>> 3.0.0)
>>> -> Trying debhelper
>>> -> Considering ocaml (>= 3.09.2)
>>> -> Trying ocaml
>>> -> Considering libncurses5-dev
>>> -> Trying libncurses5-dev
>>> -> Considering xlibs | xlib6g
>>> -> Trying xlibs
>>> -> Cannot install xlibs; apt errors follow:
>>> Reading package lists... Done
>>> Building dependency tree... Done
>>> Package xlibs is not available, but is referred to by another package.
>>> This may mean that the package is missing, has been obsoleted, or
>>> is only available from another source
>>> E: Package xlibs has no installation candidate
>>> -> Trying xlib6g
>>> -> Cannot install xlib6g; apt errors follow:
>>> Reading package lists... Done
>>> Building dependency tree... Done
>>> E: Couldn't find package xlib6g
>>> W: Unable to locate package xlib6g
>>> E: Could not satisfy build-dependency.
>>> E: pbuilder-satisfydepends failed.
>> The dependency on xlibs is apparently unnecessary, it builds fine with
>> pbuilder without it. I don't know why it was pulled in. Julien, do you?
>>
>> I'll upload a corrected version soon.
>
> I assume that it uses some of the X headers, data structures or types
> directly. In that case one should depend on the package containing
> those definitions. What happens now is that they are also pulled in
> indirectly by some gtk package so the build succeeds.
>
> You should check the code for any direct use of X definitions and then
> include the respective package in Build-Depends. But only a code audit
> will tell you that (and many people don't bother to get Build-Depends
> that correct).
Well, I checked that it did build correctly without the the build-dep on
xlibs | xlib6g before sending the mail. Moreover, notice that it did
build-depend on *xlibs*, not xlibs-dev. I cannot understand why this
should have been necessary. It's been there for quite a long time
(possibly even before I started working on the package).
Finally, this package is a binding for GTK2, so it's not so surprising
that most the dependencies are pulled in by libgtk2.0-dev. I quickly did
a grep for #includes and did not see anything directly related to X.
Cheers,
Samuel.
Reply to: