Bug#506009: maq: gzopen64 implicitly converted to pointer

2009-04-14 Thread Andreas Tille
Hi, the log of this bug says: Date: Tue, 18 Nov 2008 12:45:01 +0900 ... I will wait one week or two in case Upstream prepares a corrected update, and if not I will rework debian/rules. Well, we have now waited more than one or two monthes - IMHO we should upload now. Did I missed

Bug#506009: maq: gzopen64 implicitly converted to pointer

2008-11-17 Thread dann frazier
Package: maq Version: 0.7.1-1 Severity: serious Usertags: implicit-pointer-conversion Our automated buildd log filter[1] detected a problem that is likely to cause your package to segfault on architectures where the size of a pointer is greater than the size of an integer, such as ia64 and amd64.

Bug#506009: maq: gzopen64 implicitly converted to pointer

2008-11-17 Thread peter green
tags 506009 +patch thanks the issue seems to be caused by upstream defining _FILE_OFFSET_BITS=64 but not _LARGEFILE64_SOURCE causing the zlib header to misbehave. Defining _LARGEFILE64_SOURCE as well fixes it. This can be done by adding the following to debian/rules #needed to make the zlib

Bug#506009: [Debian-med-packaging] Bug#506009: maq: gzopen64 implicitly converted to pointer

2008-11-17 Thread Charles Plessy
Le Tue, Nov 18, 2008 at 02:55:32AM +, peter green a écrit : tags 506009 +patch thanks the issue seems to be caused by upstream defining _FILE_OFFSET_BITS=64 but not _LARGEFILE64_SOURCE causing the zlib header to misbehave. Defining _LARGEFILE64_SOURCE as well fixes it. Dear Peter,