* What exactly did you do (or not do) that was effective (or
* What was the outcome of this action?
Marking the package with the plus sign resulted in an error
messages that two dependencies of darktable:amd64 are not
satisfied. They are
These packages, without the :amd64 suffix, are installed on
my system, and dpkg -s reports
I suspect that something may be wrong with the dependencies.
* What outcome did you expect instead?
I expected the darktable:amd64 package to be installed.
I reported this problem against darktable as bug 785163, but the
darktable maintainers suggest that the problem actually lies in the
dependencies. In searching documentation online, I found the
following statement about Architecture: all packages
Pre-multiarch, architecture-dependent packages may depend on
Architecture: all packages and assume that the transitive dependencies
will be resolved using packages of the same architecture or other
packages that are Architecture: all. To avoid breaking this
assumption, Architecture: all packages will, at least initially, be
treated as equivalent to packages of the native architecture for all
dependency resolution.1 This means that for an Architecture: all
package to satisfy the dependencies of a foreign-architecture package,
it must be marked Multi-Arch: foreign or Multi-Arch: allowed.
According to the documentation I can find,
might be suitable for your package.
I have confirmed that if this line is added to your debian/control
file, the package installs, and (when other dependencies are similarly
updated), aptitude installs darktable:amd64 without complaint.
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_US.utf8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
libjs-prototype depends on no packages.
Versions of packages libjs-prototype recommends:
This issue is still reproducible and seems to require updates in more
In an up-to-date sid i386 + foreign amd64 chroot:
# apt-get install darktable:amd64
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
darktable:amd64 : Depends: libjs-prototype:amd64 but it is not installable
Depends: libjs-scriptaculous:amd64 but it is not installable
E: Unable to correct problems, you have held broken packages.