Bug#640393: NM solid backend will move into pnm with network-manager 0.9

[Michael Biebl <biebl@debian.org>]

Source: kdebase-workspace
Version: 4:4.6.5-2
Severity: important
User: pkg-utopia-maintainers@lists.alioth.debian.org
Usertags: nm-0.9

Hi,

as part of the ongoing GNOME 3 transition, I plan to upload
network-manager 0.9 to unstable soon.
It is currently available from experimental.

kdebase-workspace will FTBFS agains network-manager 0.9 as the NM solid
backend will no longer build.
The solid backend for network-manager 0.9 is provided by
plasma-widget-networkmanagement 0.9. So basically what is left to be done in
kdebase-workspace is to disable NM support as soon as network-manager
0.9 is uploaded to unstable.

Cheers,
Michael



-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 3.0.0-1-486
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages kdebase-workspace depends on:
ii  freespacenotifier      4:4.6.5-2
ii  kde-window-manager     4:4.6.5-2
ii  kdebase-workspace-bin  4:4.6.5-2
ii  klipper                4:4.6.5-2
ii  ksysguard              4:4.6.5-2
ii  systemsettings         4:4.6.5-2

Versions of packages kdebase-workspace recommends:
ii  kdm          <none>   
ii  kinfocenter  4:4.6.5-2

kdebase-workspace suggests no packages.

-- no debconf information