2015-08-23 23:50 GMT+01:00 Simon McVittie <s...@debian.org>: > On Mon, 17 Aug 2015 at 09:57:16 +0100, Manuel A. Fernandez Montecelo wrote: >> Today it cannot even start to compile because of conflics of deps to install: >> >> The following packages have unmet dependencies: >> libopenexr6v5 : Conflicts: libopenexr6 but 1.6.1-8 is to be installed. >> libilmbase6v5 : Conflicts: libilmbase6 but 1.0.1-6.1 is to be installed. >> libcairomm-1.0-1v5 : Conflicts: libcairomm-1.0-1 but 1.10.0-1.1+b1 is >> to be installed. > > I think this was caused by a mis-build of imagemagick on amd64[1] which > has now been fixed by a binNMU. Please try again; I can reproduce the > original build failure in sbuild today. > > I think this might be the last sourceful upload needed by the imagemagick > sub-transition within the larger libstdc++ mess. > > S > > [1] The mirror used by my sbuild chroot hadn't seen libopenexr6v5 yet, > causing it to be built against libopenexr6 on amd64 only. > I for one welcome our new "throw away maintainer-built binaries" > overlords.
Thanks for the update. I get this error now at 98% (and there seem to be a non-fatal error before): ERROR: Plugin doesn't implement interface: Python ERROR: /tmp/buildd/k3d-0.8.0.3/k3dsdk/scripting.cpp line 55: assertion `engine' failed ERROR: Error executing script [ /tmp/buildd/k3d-0.8.0.3/obj-x86_64-linux-gnu/share/k3d/guide/content/plugins.py ] So it will need a bit more investigation and possibly to speak with upstream about it -- I think that the fix will need a few days (at least) to arrive. Cheers. -- Manuel A. Fernandez Montecelo <manuel.montez...@gmail.com>
