Package: sane-utils
Version: 1.0.22-7.1
Severity: minor

Multi-arch has come far enough that it is now possible to install wine:i386
on an otherwise amd64 system. However, wine:i386 Depends on libwine-sane:i386,
which Depends on libsane:i386, which Recommends sane-utils.

Because sane-utils is not marked as multi-arch, the dependency from
libsane:i386 can only be satisfied by sane-utils:i386, so aptitude tries to
install that. However, sane-utils:amd64 and sane-utils:i386 are not
co-installable, so they conflict, and aptitude has to work out that it must
break the recommendation.

If sane-utils was "Multi-arch: Foreign" (which seems appropriate, since the
only interfaces it contains are command-line and network-based), then the
dependency from libsane:i386 could be satisfied by sane-utils:amd64.

(I have only tried wine/1.4-0.3 from experimental, but I suspect that
the same is true for wine/1.2.3-0.3 in unstable).

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing-proposed-updates
  APT policy: (500, 'testing-proposed-updates'), (500, 'unstable'), (500, 
'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages sane-utils depends on:
ii  adduser                3.113+nmu3
ii  debconf [debconf-2.0]  1.5.43
ii  libavahi-client3       0.6.31-1
ii  libavahi-common3       0.6.31-1
ii  libc6                  2.13-32
ii  libieee1284-3          0.2.11-10
ii  libsane                1.0.22-7.1
ii  libusb-0.1-4           2:0.1.12-21
ii  update-inetd           4.43

sane-utils recommends no packages.

Versions of packages sane-utils suggests:
pn  avahi-daemon  0.6.31-1
pn  unpaper       <none>

-- debconf information:
  sane-utils/saned_run: false
  sane-utils/saned_scanner_group: true



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to