Re: No PHP4 on arm keeps packages out of testing.
> There's nothing special about php4 in the way packages are handled for
> testing. The rule is "for each package on each architecture, can it be
> installed? if not, none of the packages go in. if they all can, they
> all go in."
But php4 doesn't say it doesn't support arm. So actually php4/arm was
missing but not noticed.
> For libming, when the testing scripts look at
> php4-ming_0.2a.cvs20020110-1_arm.deb, they notice that it's completely
> useless and unusable and will just confuse anyone who selects it in
> dselect on arm.
Still it could be installed for all other architectures.
> The solution is to ensure such packages aren't built. You can either fix
> arm or php4 (or both) so that they work together and the package isn't
> useless (and keep doing this on any other architectures where php4 might
> break), or you can stop your package from building on such architectures
> and declare them unsupported (most packages do this automatically by
> having the things the need listed in Build-Depends:).
The libming Build-Depends: do list php4-dev; php4-dev isn't available
in the pool for arm either, still it was somehow available during build.
So should i add "php4" to the build depends, although it actually is not
required for building?
Greetings,
Erich
Reply to: