Re: Packages getting marked not-for-us
On Tue, Aug 05, 2008 at 12:21:52PM -0500, John Goerzen wrote:
> This seems to happen to me most often on the s390 build daemon, and has
> happened with at least 3 to 5 different packages now. (Current example
> is hpodder). In fact, I don't think I've ever seen it happen elsewhere.
> It seems to happen when build-deps don't get satisfied, or where there
> is some problem installing the build-deps.
This is quite common with the s390 buildd - it tends to happen when it
appears that the package may not be useful on s390 (eg, due to apparing
to require hardware not available on s390), apparently based on the
"You grabbed my hand and we fell into it, like a daydream - or a fever."