[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#691140: marked as done (graphicsmagick: libmagickcore-dev uses out of date libtiff4-dev)

Your message dated Fri, 26 Jul 2013 20:10:17 +0100
with message-id <51F2C999.50809@p10link.net>
and subject line re: xastir: FTBFS: build-dependency not installable: libgeotiff-dev/libgraphicsmagick1-dev
has caused the Debian Bug report #666589,
regarding graphicsmagick: libmagickcore-dev uses out of date libtiff4-dev
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
666589: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666589
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: graphicsmagick
Severity: serious
Justification: makes unrelated software on the system break

Dear Maintainer,

Attempts to install libmagickcore-dev result in removal of
libgeotiff-dev and vice versa
Libgeotiff-dev uses libtiff5-dev and libmagickcore-dev uses
libtiff4-dev, and the situation prevents concurrent installation of
these two packages, required for compilation of a fully functional
xastir package. Xastir in unstable has no geotiff support due to this
situation.



-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1,
'experimental') Architecture: i386 (i686)

Kernel: Linux 3.2.0-3-rt-686-pae (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

--- End Message ---
--- Begin Message --- 
The build deps for sid's version of xastir are now satisfiable in both
jessie and sid and I was able to build the package successfully in both
(though I only tested in non-minimal environments). Closing these bugs.

--- End Message ---
Reply to: