On 03/24/2012 11:45 PM, Darrell Anderson wrote:
Checking ownership of the existing
files, it is tdesvn that provides the conflicting files. How should we handle this? Only one package should provide the files. I'll check for existing bug reports and if I can't find one I'll file it.
<snip>
I don't know whether this will help but a quick check on the web shows the problem is a packaging issue:
http://www.google.com/search?q=kdesdk+kdesvn&ie=utf-8&oe=utf-8&a...
Darrell
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Oh,
The interesting part is tdesvn provides:
/opt/trinity/share/services/ksvn+file.protocol /opt/trinity/share/services/ksvn+http.protocol /opt/trinity/share/services/ksvn+https.protocol /opt/trinity/share/services/ksvn+ssh.protocol /opt/trinity/share/services/ksvn.protocol /opt/trinity/share/services/svn+file.protocol /opt/trinity/share/services/svn+http.protocol /opt/trinity/share/services/svn+https.protocol /opt/trinity/share/services/svn+ssh.protocol /opt/trinity/share/services/svn.protocol
while tdesdk provides:
/opt/trinity/share/services/svn+file.protocol /opt/trinity/share/services/svn+http.protocol /opt/trinity/share/services/svn+https.protocol /opt/trinity/share/services/svn+ssh.protocol /opt/trinity/share/services/svn.protocol
I wonder if we can just do a name change for either tdesvn or tdesdk to something like:
/opt/trinity/share/services/sdksvn+file.protocol /opt/trinity/share/services/sdksvn+http.protocol /opt/trinity/share/services/sdksvn+https.protocol /opt/trinity/share/services/sdksvn+ssh.protocol /opt/trinity/share/services/sdksvn.protocol