Re: Accepted ara 1.0.13 (source all i386)
On Friday 19 May 2006 21:22, Julien Cristau wrote:
> On Fri, May 19, 2006 at 21:02:04 +0300, George Danchev wrote:
> > I have two questions:
> >
> > 1) Why some autobuilders (mips, mispel) keep picking up ara and try to
> > build arch dependant parts which are not intended to be built by them.
> > Seem only s390 got it right showing "Not-For-Us" [1].
> >
> > [1] http://buildd.debian.org/pkg.cgi?pkg=ara
>
> Every package is built by every arch if its not in not-for-us or in
> packages-arch-specific, and it can only be added there manually, so
> until then it's still in wanna-build for that arch.
We echo a message from debian/rules which explains the situation ( "There are
no native code compilers on arch $ARCH so this package arch-dependant part
should not build on it."). Seems that some buildd admins saw that and added
ara to not-for-us or package-arch-specific, but do I need to contact
arch@buildd.debian.org for the rest to be added also ? I do not see any hints
in Developers Reference for such cases.
> > 2) Do we need to reschedule the build for:
> >
> > The following packages have unmet dependencies:
> > liblablgtk2-ocaml-dev: Depends: liblablgtk2-ocaml (= 2.6.0-3) but it is
> > not going to be installed
> > Depends: ocaml-3.09.1 but it is not installable
> > E: Broken packages
> > apt-get failed.
>
> That will happen eventually, buildd admins will take care of such
> failures.
Ok, good.
--
pub 4096R/0E4BD0AB 2003-03-18 <people.fccf.net/danchev/key pgp.mit.edu>
fingerprint 1AE7 7C66 0A26 5BFF DF22 5D55 1C57 0C89 0E4B D0AB
Reply to: