On Tue, May 23, 2006 at 12:12:13PM -0700, Steve Langasek wrote: > reopen 366275 > retitle 366275 don't take b-d recommendations from random submitters without > checking them! > submitter 366275 ! > severity 366275 important > quit > > * Add xprint-utils to build-depends. Thanks anonymous someone. > (closes: #366275) > > This was a wrong fix. The xprint-utils package does not contain any .pc > files, so it cannot possibly be relevant for the build failure shown; and > xprint-utils is not yet built on all architectures, which means that this > build-dep is now causing xbase-clients to FTBFS on release architectures > where it previously had no such problem. > > The proper package to build-depend on is libxprintutil-dev. The > xprint-utils package you now build-depend on does *not* pull in > libxprintutil-dev as a dependency, which means the status of xbase-clients > wrt xprintutils.pc has *not* changed. Since both xbase-clients 1:7.0.1-1 > and 1:7.0.1-2 built fine on the autobuilders (build-depends allowing!), this > bug does not exist, and the original submitter, in addition to having > stupidly misconfigured his email, has also stupidly misconfigured his build > environment. > > Don't commit random and untested changes to debian/control on the say-so of > anonymous bug-submitting idiots! > > The proper fix here is to pass --disable-xprint to the configure script for > xbdebizzy, so that the package neither fails to build nor builds with > different dependencies in the presence of libxp-dev.
This is odd. When I did a build in pbuilder, the build did indeed fail and then when I added xprint-utils to the build-depends, the build succeeded. This wasn't untested by any means and I didn't just put it in there for the hell of it. I don't know what changed, but at this point I really don't care enough to investigate. Anyway, I'll apply your fix. - David Nusinow -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]