kde-plasma-networkmanagement-0.9-0.25 coming to kde-testing

[Rex Dieter]

OK, this is a notable one, so here's the scoop. :)

kde-plasma-networkmanagement-0.9-0.25
1. Obsoletes: knetworkmanager
2. enables the requisite networkmanagement kded module by default
3. includes a script to enable the the nm plasma applet in your systray
(on your next login).

This was done because:
1.  upstream doesn't have much interested in the monolithic knm client
anymore (ie, no support, no bug fixes, yada yada)
2.  knm doesn't work (well) with kde-4.5 anyway, see
https://bugzilla.redhat.com/show_bug.cgi?id=604798
for more details.

-- Rex

[Michael J Gruber]

Rex Dieter venit, vidit, dixit 27.09.2010 18:51:
> OK, this is a notable one, so here's the scoop. :)
>
> kde-plasma-networkmanagement-0.9-0.25
> Obsoletes: knetworkmanager
> enables the requisite networkmanagement kded module by default
> includes a script to enable the the nm plasma applet in your systray
>
> (on your next login).

Starting from a F13 which has the plasmoid already, I get funny yum
messages which sound as if k-p-nm would get "installed", not "updated".
But, in fact it gets updated and the old knm removed as intended, see
below. I don't know whether that's a yum/rpm issue or a spec file thing.

Michael

[root@localhost ~]# rpm -qa k*network*

kde-plasma-networkmanagement-0.9-0.22.20100830.fc13.kde45.x86_64

kdenetwork-4.5.1-0.1.fc13.x86_64
knetworkmanager-libs-0.9-0.22.20100830.fc13.kde45.x86_64
knetworkmanager-vpnc-0.9-0.22.20100830.fc13.kde45.x86_64
knetworkmanager-openvpn-0.9-0.22.20100830.fc13.kde45.x86_64
kdenetwork-libs-4.5.1-0.1.fc13.x86_64
knetworkmanager-0.9-0.22.20100830.fc13.kde45.x86_64

[root@localhost ~]# yum --enablerepo=kde --enablerepo=kde-testing update
*network*

Loaded plugins: presto, refresh-packagekit
Setting up Update Process
Resolving Dependencies
--> Running transaction check
---> Package kde-plasma-networkmanagement.x86_64
1:0.9-0.25.20100920.fc13 set to be installed
[though I have it at -0.23 - why not "updated"?]
---> Package knetworkmanager-libs.x86_64 1:0.9-0.25.20100920.fc13 set to
be updated
---> Package knetworkmanager-openvpn.x86_64 1:0.9-0.25.20100920.fc13 set
to be updated
---> Package knetworkmanager-vpnc.x86_64 1:0.9-0.25.20100920.fc13 set to
be updated
--> Finished Dependency Resolution

Dependencies Resolved

=============================================================================================================================================================
 Package                                         Arch
   Version                                      Repository
        Size
=============================================================================================================================================================
Installing:
 kde-plasma-networkmanagement                    x86_64
   1:0.9-0.25.20100920.fc13                     kde-testing
       102 k
     replacing  knetworkmanager.x86_64 1:0.9-0.22.20100830.fc13.kde45
Updating:
 knetworkmanager-libs                            x86_64
   1:0.9-0.25.20100920.fc13                     kde-testing
       644 k
 knetworkmanager-openvpn                         x86_64
   1:0.9-0.25.20100920.fc13                     kde-testing
        34 k
 knetworkmanager-vpnc                            x86_64
   1:0.9-0.25.20100920.fc13                     kde-testing
        26 k

...

Installed:
  kde-plasma-networkmanagement.x86_64 1:0.9-0.25.20100920.fc13

[wtf - do I have 2 of them now?]

Updated:
  knetworkmanager-libs.x86_64 1:0.9-0.25.20100920.fc13
      knetworkmanager-openvpn.x86_64 1:0.9-0.25.20100920.fc13

knetworkmanager-vpnc.x86_64 1:0.9-0.25.20100920.fc13

Replaced:
  knetworkmanager.x86_64 1:0.9-0.22.20100830.fc13.kde45

Complete!

[root@localhost ~]# rpm -qa k*network*

kdenetwork-4.5.1-0.1.fc13.x86_64
kde-plasma-networkmanagement-0.9-0.25.20100920.fc13.x86_64
knetworkmanager-vpnc-0.9-0.25.20100920.fc13.x86_64
knetworkmanager-libs-0.9-0.25.20100920.fc13.x86_64
knetworkmanager-openvpn-0.9-0.25.20100920.fc13.x86_64
kdenetwork-libs-4.5.1-0.1.fc13.x86_64

[OK, everything in apple^Wpenguin pie order]

[Kevin Kofler]

Michael J Gruber wrote:
> Starting from a F13 which has the plasmoid already, I get funny yum
> messages which sound as if k-p-nm would get "installed", not "updated".
> But, in fact it gets updated and the old knm removed as intended, see
> below. I don't know whether that's a yum/rpm issue or a spec file thing.

That's how yum handles obsoletions. It should probably say something 
different if you already had the package, but it doesn't.

Kevin Kofler

[Clemens Eisserer]

Looks fine :) (for now ^^)

2010/9/27 Rex Dieter :
> OK, this is a notable one, so here's the scoop. :)
>
> kde-plasma-networkmanagement-0.9-0.25
> Obsoletes: knetworkmanager
> enables the requisite networkmanagement kded module by default
> includes a script to enable the the nm plasma applet in your systray
>
> (on your next login).
>
> This was done because:
> upstream doesn't have much interested in the monolithic knm client
>
> anymore (ie, no support, no bug fixes, yada yada)
> 2.  knm doesn't work (well) with kde-4.5 anyway, see
> https://bugzilla.redhat.com/show_bug.cgi?id=604798
> for more details.
>
> -- Rex
> _______________________________________________
> kde mailing list
> [e-mail]
> https://admin.fedoraproject.org/mailman/listinfo/kde
> New to KDE4? - get help from http://userbase.kde.org