On 20.01.2014 22:51, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the freeimage package:
>
> #735847: freeimage: builds wrong tiff, broken 32 bit
>
> It has been closed by Scott Howard .
>
great, using system tiff is t
On 20.01.2014 01:46, Scott Howard wrote:
>
> Before uploading that patch and closing this bug, I'd like to look at
> "long is 32 bit on 32 bit arches. it needs to be int64_t or long long.
> This occurs several times in the file." LibTIFF4/tiffconf.h is
> generated at build time, so it should be OK
On 20.01.2014 01:46, Scott Howard wrote:
>
> Checking over the package, I don't think it's a problem of not
> updating the patch. The previous version of the package and patches
> didn't touch anything related to TIFF and used freeimage's included
> libtiff. The current version also doesn't touche
attached patch from upstream cvs seem to fix the tag issue, thought I'm
not so sure about if its save concerning buffer overflows.
http://freeimage.cvs.sourceforge.net/viewvc/freeimage/FreeImage/Source/Metadata/XTIFF.cpp?r1=1.23&r2=1.24&view=patch
http://sourceforge.net/p/freeimage/discussion/3611
Package: freeimage
Version: 3.15.4
Severity: serious
the recent update to .4 updates the internal tiff to libtiff4 but does
not update the debian patch
debian/patches/disable_embedded_libraries.patch appropriately.
This leads to some internals using the libtiff internals instead of the
libtiff4
Th
see
https://bugs.launchpad.net/ubuntu/+source/python-scientific/+bug/1041302
for another issue which is fixed by a rebuild
signature.asc
Description: OpenPGP digital signature
Package: python-scientific
Version: 2.8-3
Severity: serious
I'm not sure why but python-scientific requires a rebuild to work correctly.
Apparently there was a uncoordinated abi/abi break somewhere in its dependences
(possibly netcdf or numpy):
apt-get install python-scientific python-netcdf
pyt
7 matches
Mail list logo
