[Buildd-tools-devel] Bug#478524: Problem with autobuild of libtommath/0.39-2

[Joe Nahmias]

Hi Riku,

On Wed, May 07, 2008 at 02:48:53PM +0300, Riku Voipio wrote:
> On Tue, May 06, 2008 at 07:41:10PM +0000, Joe Nahmias wrote:
> > On Mon, May 05, 2008 at 11:57:55PM +0300, Riku Voipio wrote:
> > > Lets not complicate this matter with the age-long build/build-arch
> > > discussion. libtommath needs add the build-dependencies enough to
> > > to get through debian/rules build for the time being.
> 
> > Maybe I'm missing something [...]
> 
> Yes. You missed the part where I requested not complicate the issue.
> dpkg-buildpackage/sbuild will be made better eventually. Will happen
> faster if someone actually shows a patch that uses build-arch and
> demonstrates that it will break building of <1% packages. Currently
> it seems people prefer to just talk about it and hypothise about problems
> that could potentially materialize in some parallax universe rather than
> provide patches and testresults of full archive rebuilds.

I agree, it's not complicated -- fix your buildd software (or
environment, if you pefer) to install B-D-I if you're going to use the
build target.  It's not a bug in my package if you use faulty
software/environment in your buildd, that doesn't follow policy's
requirements for building debian packages, and then the build fails
because you didn't follow the instructions.  Nobody is forcing you to
install only B-D and not B-D-I and then use dpkg-buildpackage which uses
the build target.

Furthermore, I have an idea that avoids the whole complicated build-arch
issue entirely, which you have not addressed or responded to.  I'd be
happy to provide a patch (comment out line 364 in dpkg-buildpackage) but
I don't have the resources to do a full archive rebuild to test it.  Can
you or anyone else reading this help me out with that?

> So for now, no furious handwaving towards the policy/dpkg/sbuild etc
> is going to help your package a) getting built b) getting to
> testing/lenny.

It's already in testing/lenny, albeit only for one arch.  I could build
the package for each arch manually -- and with proper environment and
software it would work just fine; but, I'll probably end up copying the
B-D-I into B-D to avoid the hassle.  I just hope you realize that the
true problem/bug is in the current buildd b0rkage that has become the
status quo -- not in anything I did in the packaging.

--Joe