yes, this is due to a binary incompatibility between libjpeg8-dev and libjpeg62-dev, see bug 692268, marking as duplicate.
yes, this is due to a binary incompatibility between libjpeg8-dev and libjpeg62-dev, see bug 692268, marking as duplicate.