Christopher Martin <[EMAIL PROTECTED]> writes:
> Hello,
>
> I'm curious as to why okle_0.4-4 is listed as:
>
> kde/okle_0.4-4: Dep-Wait by buildd_m68k-zeus [optional:out-of-date]
> Dependencies: ogle-mmx
> Previous state was Building until 2004 Apr 25 22:07:22
>
> Assuming that I'm reading this entry correctly (from
> buildd.debian.org/stats/m68k-all.txt - this stuff is all pretty new to
> me), it's waiting for ogle-mmx. But, of course, this will never exist on
> m68k, which is why okle's dependencies are as follows:
>
> ogle-mmx | ogle | ogle-altivec
>
> ...so it's quite capable of installing on m68k, which has the generic ogle
> package available. Other non-mmx/altivec architectures have successfully
> built okle. (The build dependencies are ordered ogle | ogle-mmx |
> ogle-altivec, since I learned the hard way that buildd doesn't like these
> "OR" statements when it comes to build-deps.)
It does like them. it just chooses to always require the first so
builds always use the same packages.
> So if someone could either fix okle's build status, or else explain the
> real problem, I'd be very grateful.
Needs fix. Dep-Waiting on a non-existing (never existing) package is
allways a bug.
MfG
Goswin
