- edited description
F23 : Attempting to install kmix causes confict
F23 system (workstation/gnome) with kde4-fedora installed after the oxygen-icon-theme issue was fixed on 2016-03-08. System is updated.
When attempting to install kmix, I run into a conflict between kf5-kactivities and kactivities: http://pastebin.ca/3403634
Comments (10)
-
reporter -
reporter Rebuilt the kmix RPM from F21 and the process went very smoothly, only had to install a few devel packages for the build, and the installation went off without a hitch.
-
reporter - changed status to closed
While conflict remains, package is easily enough build from F21 source RPM. Closing issue.
-
reporter - attached kmix-debuginfo-4.14.3-1.fc23.x86_64.rpm
- attached kmix-4.14.3-1.fc23.x86_64.rpm
- attached kmix-4.14.3-1.fc23.src.rpm
-
repo owner - changed title to F23 : Attempting to install kmix causes confict
-
repo owner Sorry for the lack of response, I was off from work for 2 weeks and had very little time to do anything with repo.
Even that it is now closed, I will have a look and see if that is an issue, as I would like to provide as much as we can within the repo.
I'm sure I have seen F23 with kmix working fine, but can't find that VM now, so need to create new one for testing.
Will keep updating here.
Regards, Piotr
-
repo owner I can't replicate the issue, kmix seems to be working fine and installable without any issues.
[root@localhost ~]# dnf list installed kactivities kmix Last metadata expiration check: 0:15:56 ago on Tue Apr 5 14:29:31 2016. Installed Packages kactivities-libs.x86_64 3:4.13.3-12.fc23 @peem-kde4-fedora kf5-kactivities.x86_64 5.19.0-1.fc23 @updates
kf5-kactivities-libs.x86_64 5.19.0-1.fc23 @updates
kmix.x86_64 15.12.3-1.fc23 @updates -
repo owner Jon,
would you care to test it now ? I suspect it may be issue with either version that were available back when you submitted the issue here, and it may be fine now.
Regards, Piotr
-
repo owner - changed status to on hold
Waiting for confirmation from reporter
-
reporter Hi Piotr, I'm still getting the same error in a VirtualBox VM I built this morning.
- Log in to comment