Bug#653061: libgs9 exports symbols conflicting with the same symbols in libjpeg8

Sample stack trace: #0 0x7fffef66486b in ?? () from /usr/lib/libgs.so.9 #1 0x7fffeea3a997 in jinit_memory_mgr (cinfo=0x7ffea380) at jmemmgr.c:1059 #2 0x7fffeea1b32e in jpeg_CreateDecompress (cinfo=0x7ffea380, version=, structsize=656) at jdapimin.c:59 #3 0x7fff

Processed: Re: libjpeg8: Please provide variant compiled with #define D_MAX_BLOCKS_IN_MCU 64

Processing commands for cont...@bugs.debian.org: > reassign 582522 ghostscript 8.64~dfsg-2 Bug #582522 [src:libjpeg8] libjpeg8: Please provide variant compiled with #define D_MAX_BLOCKS_IN_MCU 64 Bug reassigned from package 'src:libjpeg8' to 'ghostscript'. Bug No longer marked as found in version

Re: libjpeg8: Please provide variant compiled with #define D_MAX_BLOCKS_IN_MCU 64

reassign 582522 ghostscript 8.64~dfsg-2 quit Jonathan Nieder wrote: > Bill Allombert wrote: >> Honestly, unless you provide evidence that PS files that include invalid >> jpeg-encoded data are still in use, I am not going to include two new >> packages >> to support non-standard compliant data i

Bug#653061: libgs9 exports symbols conflicting with the same symbols in libjpeg8

On Fri, Dec 23, 2011 at 03:46:59PM -0600, Jonathan Nieder wrote: > Hi, > > Jean Brefort wrote: > > > Three symbols are concerned: > > jpeg_mem_init, jpeg_mem_term and jpeg_mem_available. > > > > Building an executable using the two libraries might crash. This happens > > for me > > with gnumeric

Bug#653061: libgs9 exports symbols conflicting with the same symbols in libjpeg8

Hi, Jean Brefort wrote: > Three symbols are concerned: > jpeg_mem_init, jpeg_mem_term and jpeg_mem_available. > > Building an executable using the two libraries might crash. This happens for > me > with gnumeric (from git) when goffice is built with eps support and when I try > to add a jpeg ima

foo2zjs_20111202dfsg0-1_amd64.changes ACCEPTED into unstable

Accepted: foo2zjs_20111202dfsg0-1.debian.tar.gz to main/f/foo2zjs/foo2zjs_20111202dfsg0-1.debian.tar.gz foo2zjs_20111202dfsg0-1.dsc to main/f/foo2zjs/foo2zjs_20111202dfsg0-1.dsc foo2zjs_20111202dfsg0-1_all.deb to main/f/foo2zjs/foo2zjs_20111202dfsg0-1_all.deb foo2zjs_20111202dfsg0.orig.tar

Processing of foo2zjs_20111202dfsg0-1_amd64.changes

foo2zjs_20111202dfsg0-1_amd64.changes uploaded successfully to localhost along with the files: foo2zjs_20111202dfsg0-1.dsc foo2zjs_20111202dfsg0.orig.tar.bz2 foo2zjs_20111202dfsg0-1.debian.tar.gz printer-driver-foo2zjs_20111202dfsg0-1_amd64.deb foo2zjs_20111202dfsg0-1_all.deb Greetings,

Processing of foo2zjs_20111202dfsg0-1_amd64.changes

foo2zjs_20111202dfsg0-1_amd64.changes uploaded successfully to ftp-master.debian.org along with the files: foo2zjs_20111202dfsg0-1.dsc foo2zjs_20111202dfsg0.orig.tar.bz2 foo2zjs_20111202dfsg0-1.debian.tar.gz printer-driver-foo2zjs_20111202dfsg0-1_amd64.deb foo2zjs_20111202dfsg0-1_all.deb

Bug#653062: hplip: p-makeuri does not resolve FQDN => could add only local printer

Package: hplip Version: 3.11.10-1 Severity: important Will report upstream but this bug shouldbe known by debian $ hp-makeuri HPD4636B.lan. error: Device not found $hp-makeuri HPD4636B HP Linux Imaging and Printing System (ver. 3.11.10) Device URI Creation Utility ver. 5.0 Copyright (c) 2001-9

Processed: Forwarded

Processing commands for cont...@bugs.debian.org: > forwarded 653062 https://bugs.launchpad.net/ubuntu/+bug/908097 Bug #653062 [hplip] hplip: p-makeuri does not resolve FQDN => could add only local printer Set Bug forwarded-to-address to 'https://bugs.launchpad.net/ubuntu/+bug/908097'. > tags 6530

Bug#653061: libgs9 exports symbols conflicting with the same symbols in libjpeg8

Package: libgs9 Version: 9.04~dfsg-3 Severity: important Three symbols are concerned: jpeg_mem_init, jpeg_mem_term and jpeg_mem_available. Building an executable using the two libraries might crash. This happens for me with gnumeric (from git) when goffice is built with eps support and when I try