On Sat, Dec 28, 2013 at 01:11:20PM +0100, Aurelien Jarno wrote:
> Package: libgluegen2-build-java
> Version: 2.1.3-1
> Severity: serious
> Tags: upstream patch
> Justification: makes other packages FTBFS
> 
> libgluegen2-build-java provides a mechanism in <glibc-compat-symbols.h>
> to lower memcpy symbols version. This doesn't take care of at least
> ia64 and s390x among the official Debian architectures, but at least
> arm64, ppc64, sh4, sparc64, and x32 are also affected among unofficial
> architectures. This causes other packages to FTBFS, see for example:
> https://buildd.debian.org/status/fetch.php?pkg=libjogl2-java&arch=ia64&ver=2.1.3-1&stamp=1387422174
> https://buildd.debian.org/status/fetch.php?pkg=libjogl2-java&arch=s390x&ver=2.1.3-1&stamp=1388229627
> 
> As this mechanism doesn't really make sense in a distribution context
> (the dependencies are handled by the package manager), I would suggest
> to simply disable it. This is the purpose of the patch below:

I have the feeling that the patch is there so that they get the
old behavior from memcpy() and that the newer version (2.14) goes
over the buffer in a different direction and breaks something.

Instead of trying to get the old version of memcpy() again they
should instead fix their code and for instance use memmove()
instead of memcpy().

PS: Staticly linking should not be preferred.


Kurt

__
This is the maintainer address of Debian's Java team
<http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers>. 
Please use
debian-j...@lists.debian.org for discussions and questions.

Reply via email to