Package: debfoster
Version: 2.7-1.2
Followup-For: Bug #539340

I didn't notice any actual report of debfoster behaviour with multiarch
so far, so thought it might be useful (for maintainers, but mainly for
querybtsers/googlers, to report it:

fiori# arch
x86_64
fiori# debfoster

libcanberra-gtk-module is keeping the following 1 packages installed:
  libcanberra-gtk0
Keep libcanberra-gtk-module? [Ynpsiuqx?], [H]elp: P
Keep gtk2-engines-pixbuf? [Ynpsiuqx?], [H]elp: P
Keep libgail-common? [Ynpsiuqx?], [H]elp: P
Keep libqt4-test? [Ynpsiuqx?], [H]elp: P
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Package 'gtk2-engines-pixbuf' is not installed, so not removed. Did you mean 
'gtk2-engines-pixbuf:i386'?
Package 'libgail-common' is not installed, so not removed. Did you mean 
'libgail-common:i386'?
Package 'libcanberra-gtk-module' is not installed, so not removed. Did you mean 
'libcanberra-gtk-module:i386'?
Package 'libcanberra-gtk0' is not installed, so not removed. Did you mean 
'libcanberra-gtk0:i386'?
Package 'libqt4-test' is not installed, so not removed. Did you mean 
'libqt4-test:i386'?
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
fiori# COLUMNS=200 dpkg -l | grep libcanberra-gtk-module
ii  libcanberra-gtk-module:i386                  0.28-6                      
i386                        translates GTK+ widgets signals to event sounds
fiori# 

HTH

Alexis 

-- System Information:
Debian Release: 7.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages debfoster depends on:
ii  libc6     2.13-38
ii  libgc1c2  1:7.1-9.1

Versions of packages debfoster recommends:
ii  apt  0.9.7.8

debfoster suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to