Possible problem installing kdeplasma-applets-plasma-nm

mcloaked · 2013-10-15 20:08:07

When doing pacman -Syu kdeplasma-applets-plasma-nm for the new kde network management package does anyone have any problem installing it? I installed the first released version a few days back which could be installed in parallel with the old kdeplasma-applets-networkmanagement package which was fine, and then once installed the original package could then be removed. However the new version of kdeplasma-applets-plasma-nm (0.9.3.0-2 -> 0.9.3.1-1) now has the same filenames as the original old package and there may be filename conflicts during install.

Does anyone know the best way to install the new package (0.9.3.1-1) on a system where the first version (0.9.3.0-2) was not yet installed?

Last edited by mcloaked (2013-10-15 20:09:19)

cfr · 2013-10-16 01:31:04

Can you not uninstall the old package before installing the new one to avoid the conflicts?

mcloaked · 2013-10-16 07:44:29

I thought the same but then wondered how the network would behave once the old package was uninstalled but before the new one was in! I would have thought that the new package would have required removal as a requirement so that pacman would remove the old and install the new in one single operation but that seems not to be the case. Anyway maybe someone will report if there is a problem when they try to do it!

arojas · 2013-10-16 07:56:43

Both plasma applets are just GUI interfaces for nerworkmanager. As long as you have networkmanager installed and running, your network should be fine (you just won't be able to configure it)

mcloaked · 2013-10-16 08:51:25

OK so I guess that the following three commands in sequence should work fine - but I do wonder if a note to the effect would be worth as an announcement?

pacman -Syu
pacman -R kdeplasma-applets-networkmanagement
pacman -S kdeplasma-applets-plasma-nm

Otherwise if trying an install on its own leads to:

pacman -Syu kdeplasma-applets-plasma-nm
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for inter-conflicts...

Packages (3): libmm-qt-0.5.1-1  libnm-qt-0.9.0.1-1  kdeplasma-applets-plasma-nm-0.9.3.1-1

Total Download Size:    1.20 MiB
Total Installed Size:   5.62 MiB

:: Proceed with installation? [Y/n] y
:: Retrieving packages ...
 libmm-qt-0.5.1-1-x86_64                            98.9 KiB  1163K/s 00:00 [###########################################] 100%
 libnm-qt-0.9.0.1-1-x86_64                         417.3 KiB  1128K/s 00:00 [###########################################] 100%
 kdeplasma-applets-plasma-nm-0.9.3.1-1-x86_64      712.4 KiB  1103K/s 00:01 [###########################################] 100%
(3/3) checking keys in keyring                                              [###########################################] 100%
(3/3) checking package integrity                                            [###########################################] 100%
(3/3) loading package files                                                 [###########################################] 100%
(3/3) checking for file conflicts                                           [###########################################] 100%
error: failed to commit transaction (conflicting files)
kdeplasma-applets-plasma-nm: /usr/lib/kde4/kded_networkmanagement.so exists in filesystem
kdeplasma-applets-plasma-nm: /usr/share/apps/networkmanagement/networkmanagement.notifyrc exists in filesystem
kdeplasma-applets-plasma-nm: /usr/share/icons/oxygen/32x32/devices/network-defaultroute.png exists in filesystem
kdeplasma-applets-plasma-nm: /usr/share/kde4/services/kded/networkmanagement.desktop exists in filesystem
kdeplasma-applets-plasma-nm: /usr/share/kde4/services/plasma-applet-networkmanagement.desktop exists in filesystem
Errors occurred, no packages were upgraded.

which is clearly not desirable!

mcloaked · 2013-10-16 16:54:26

kdeplasma-applets-plasma-nm-0.9.3.1-2 is released - hopefully this new version fixes the issue.

cfr · 2013-10-16 23:00:34

mcloaked wrote:

OK so I guess that the following three commands in sequence should work fine - but I do wonder if a note to the effect would be worth as an announcement?

I'm assuming it is an oversight. So if anybody had realised the need for such an announcement, there would have been no need as the package would have been corrected. What I was suggesting was a work around and not the way it should work. What the package should do is use the relevant fields of the pkgbuild to tell pacman that the new version replaces the old one and conflicts with it. Then pacman would know what to do automatically and it would just ask you to confirm.

mcloaked · 2013-10-17 09:21:14

cfr wrote:

mcloaked wrote:
OK so I guess that the following three commands in sequence should work fine - but I do wonder if a note to the effect would be worth as an announcement?
I'm assuming it is an oversight. So if anybody had realised the need for such an announcement, there would have been no need as the package would have been corrected. What I was suggesting was a work around and not the way it should work. What the package should do is use the relevant fields of the pkgbuild to tell pacman that the new version replaces the old one and conflicts with it. Then pacman would know what to do automatically and it would just ask you to confirm.

Agree entirely. There are also other issues with this new package - for example see https://bugs.kde.org/show_bug.cgi?id=326134

Last edited by mcloaked (2013-10-17 15:52:14)

cfr · 2013-10-17 21:08:42

Right but those are upstream bugs. Has anybody reported the Arch packaging bug?

ilpianista · 2013-10-21 10:36:24

cfr wrote:

Right but those are upstream bugs. Has anybody reported the Arch packaging bug?

I didn't add the replace() rule as that option will not allow people to use the old kdeplasma-applets-networkmanagement plasmoid from AUR. I don't want to force anyone to switch.

cfr · 2013-10-21 20:22:36

scarpino wrote:

cfr wrote:
Right but those are upstream bugs. Has anybody reported the Arch packaging bug?
I didn't add the replace() rule as that option will not allow people to use the old kdeplasma-applets-networkmanagement plasmoid from AUR. I don't want to force anyone to switch.

Sorry. I didn't realise the old version was in AUR. However, shouldn't the conflicts field have prevented the situation discussed in this thread (without the replaces field)? I checked and the pkgbuild seems to use the conflicts field so either I'm just horribly confused or there's something odd...

ilpianista · 2013-10-21 21:14:41

cfr wrote:

However, shouldn't the conflicts field have prevented the situation discussed in this thread (without the replaces field)? I checked and the pkgbuild seems to use the conflicts field so either I'm just horribly confused or there's something odd...

-2 uses conflicts() while -1 didn't. That's because you got the error message.

cfr · 2013-10-21 22:02:40

OK. That makes a lot more sense. Thanks for clearing that up. [I never got the error message myself but I understand what you mean.]

ChALkeR · 2013-11-07 23:04:10

mcloaked wrote:

Agree entirely. There are also other issues with this new package - for example see https://bugs.kde.org/show_bug.cgi?id=326134

Actually, that is not a bug, that's a configuration issue.

The cause of the problem was the fact that before version 0.9.3.1 the new applet had a different kded module name from the old one, and they could be installed simultaneously in Archlinux. In such case most probably the old module was disabled, and the new module was enabled.
Starting from version 0.9.3.1 the new module was renamed to match the old module name, resulting in it getting disabled by the same setting that previously disabled the old module.
Without the kded module running, the SecretAgent didn't work.

Probably a warning has to be added in the Archlinux package. The solution is:
$ qdbus org.kde.kded /kded org.kde.kded.setModuleAutoloading networkmanagement 1
$ qdbus org.kde.kded /kded org.kde.kded.loadModule networkmanagement

Arch Linux

#1 2013-10-15 20:08:07

Possible problem installing kdeplasma-applets-plasma-nm

#2 2013-10-16 01:31:04

Re: Possible problem installing kdeplasma-applets-plasma-nm

#3 2013-10-16 07:44:29

Re: Possible problem installing kdeplasma-applets-plasma-nm

#4 2013-10-16 07:56:43

Re: Possible problem installing kdeplasma-applets-plasma-nm

#5 2013-10-16 08:51:25

Re: Possible problem installing kdeplasma-applets-plasma-nm

#6 2013-10-16 16:54:26

Re: Possible problem installing kdeplasma-applets-plasma-nm

#7 2013-10-16 23:00:34

Re: Possible problem installing kdeplasma-applets-plasma-nm

#8 2013-10-17 09:21:14

Re: Possible problem installing kdeplasma-applets-plasma-nm

#9 2013-10-17 21:08:42

Re: Possible problem installing kdeplasma-applets-plasma-nm

#10 2013-10-21 10:36:24

Re: Possible problem installing kdeplasma-applets-plasma-nm

#11 2013-10-21 20:22:36

Re: Possible problem installing kdeplasma-applets-plasma-nm

#12 2013-10-21 21:14:41

Re: Possible problem installing kdeplasma-applets-plasma-nm

#13 2013-10-21 22:02:40

Re: Possible problem installing kdeplasma-applets-plasma-nm

#14 2013-11-07 23:04:10

Re: Possible problem installing kdeplasma-applets-plasma-nm

Board footer