Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: Transaction Check Error: file /usr/share/config/katesyntaxhighlightingrc from install of kate-4.9.90-1.fc19.i686 conflicts with file from package kdelibs3-3.5.10-39.fc18.i686
ick, guess I'll try to rework the packaging of each so that can share a common katesyntaxhighlightingrc
an alternative that's potentially less messy would be to patch kdelibs3 kate code to not assume a katesyntaxhighlightingrc is present with values: [General] Version=14 CachedVersion=0 (ie, default those values in code instead), except, it turns out that kate-4.9.90/part/syntax/katesyntaxdocument.cpp: if (generalConfig.readEntry ("Version",0) > generalConfig.readEntry ("CachedVersion",0)) kate-4.9.90/part/syntax/katesyntaxdocument.cpp: generalConfig.writeEntry ("CachedVersion", generalConfig.readEntry ("Version",0)); contains references too, and seems to default these to 0 instead. :-/
Currently (up to 4.9), this file is only shipped by kdelibs3. In 4.10, kate seems to ship it (again). The kdelibs3 version has these contents: [General] Version=14 CachedVersion=0 The kate 4 version, on the other hand, defines some default item styles: https://projects.kde.org/projects/kde/kde-baseapps/kate/repository/revisions/master/entry/part/data/katesyntaxhighlightingrc I think the kdelibs3 version can just be removed, Quanta and KTIGCC (the apps using the kdelibs3 KatePart I tested this with) seem to work fine without it.
The fact that this legacy file is changing settings also affecting the current code sounds like all the more of a reason to remove it. Now of course the real question is: What exactly is this for? My guess: to make sure the cache gets regenerated when you upgrade the KatePart to a version with an incompatible cache ABI. If that's true, that's not likely to happen with kdelibs3 anymore, and with kate 4, it seems not to be needed anymore or upstream would set that version. But it'd be good to know for sure.
kdelibs3-3.5.10-40.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/kdelibs3-3.5.10-40.fc18
Package kdelibs3-3.5.10-40.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing kdelibs3-3.5.10-40.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-19773/kdelibs3-3.5.10-40.fc18 then log in and leave karma (feedback).
Package kdelibs3-3.5.10-42.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing kdelibs3-3.5.10-42.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-19773/kdelibs3-3.5.10-42.fc18 then log in and leave karma (feedback).
kdelibs3-3.5.10-42.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
kdelibs3-3.5.10-42.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/kdelibs3-3.5.10-42.fc17
kdelibs3-3.5.10-42.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.