Your message dated Wed, 29 Oct 2014 14:40:56 +0100
with message-id
<CAE2SPAZUyXgDBa+NhO+XUq+sVwVJTk=vyydmyrvy-dwwm9n...@mail.gmail.com>
and subject line Done
has caused the Debian Bug report #767156,
regarding imagemagick: FTBFS: B-D on inkscape problematic
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 ow...@bugs.debian.org
immediately.)
--
767156: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767156
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: imagemagick
Version: 8:6.8.9.9-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
imagemagick declares a build dependency on inkscape, which in turn
depends on libmagick*-6.q16-*. This B-D is a problem even when
inkscape is already available:
imagemagick build-depends on:
- inkscape
inkscape depends on:
- libmagick++-6.q16-5 (>= 8:6.8.9.6)
libmagick++-6.q16-5 depends on:
- libmagickcore-6.q16-2 (>= 8:6.8.9.6)
libmagickcore-6.q16-2 depends on missing:
- imagemagick-common (= 8:6.8.9.6-4)
It looks like the autobuilders could only find imagemagick-common
8:6.8.9.9-1. Perhaps the relevant infrastructure (on incoming.d.o?)
should be configured to keep architecture-independent packages in sync
with architecture-dependent packages from the same source. However,
this circularity would still require manual intervention when
boostrapping.
I'd suggest moving inkscape to Build-Depends-Indep, so that it will
still show up in the delegates.xml on user systems.
Could you please take a look?
Thanks!
--- End Message ---
--- Begin Message ---
Version: 8:6.8.9.9-2
Closed with newer imagemagick version
--- End Message ---
