Bug#700898: commons-daemon: FTBFS because it whitelists architectures

[tony mancill]

On 02/18/2013 02:09 PM, Thorsten Glaser wrote:
> Source: commons-daemon
> Version: 1.0.10-3
> Severity: important
> Justification: FTBFS
> 
> Hi,
> 
> your package needs positive porting to architectures.
> Please do not make it Architecture: any in this case,
> list the architectures or port it to all of them, both
> Debian and Debian-Ports ones.
> 
> .oO(This pattern is getting common… maybe I should write a Wiki page)
> 
> Thanks,
> //mirabilos

Hi Thorsten,

According to the buildd logs [1], the package builds on every
architecture except for hurd-i386.  Instead of white-listing
architectures, doesn't it make more sense to patch around the PATH_MAX
issue on hurd-i386?  That seems to be the reason for the FTBFS, not the
use of Arch: any

If this isn't what you're referring to, please let me know.

Thank you,
tony

[1] https://buildd.debian.org/status/package.php?p=commons-daemon

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 900 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-java-maintainers/attachments/20130218/76c020bf/attachment.pgp>