Subversion plugin missing in kdevplatform7-libs (Saucy)

Asked by Velnias

I've installed kdevplatform7-libs 1.5.1-0ubuntu1 and now my Kdevelop is missing SVN support, because the SVN plugin was disabled.

I found a hint in /usr/share/doc/kdevplatform7-libs/changelog.Debian.gz:

* Disable compilation of SVN plugin due to license
    incompatability: patches/excludeSvnPluginFromCompilation.diff
* Remove libsvn-dev build dependency: only needed for SVN plugin.

Do I need to recompile kdevplatform myself (which I don't want to do) or will we get back SVN support in Ubuntu?

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu kdevplatform Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said :
#1

i suggest you report a bug. Saucy is nowhere near ready and will have lots of bugs and feature holes. Saucy is due out in October. If you want an OS that works I suggest you reinstall with Precise. If you are happy to put up with bugs and want to report bugs to get the release ready for release then by all means use Saucy but don't expect a smooth ride

Revision history for this message
Velnias (velnias) said :
#2

First I was thinking about reporting it as bug, but the bug report page recommended to ask first here.

Else I have just pinning for a few developer packages on Saucy to get versions early enough to avoid "surprises" in my own project.

And I cannot imagine Ubuntu follows the same restrictive policy like Debian in at least such a feature like SVN integration.

Revision history for this message
Robert Grasböck (l-mail-3) said :
#3

When can we expect a new version with subversion plugin fixed?

Revision history for this message
Velnias (velnias) said :
#4

If it should be a problem to re-enable it, some can look at my PPA where I backported the package to Precise and fixed it. The only change has been to enable the plugin again.

https://launchpad.net/~velnias/+archive/sandbox/+packages

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#5

If you alert the developers, yes.

This is what pre-release is for. They are for Ubuntu users who want to help get the OS ready for release and can work around issue themselves til things get working.

They are NOT for the casual user, if you need an OS that works then I suggest a clean install of Precise, which is not only stable but is also LTS and supported long after Saucy is EOL.

Revision history for this message
Velnias (velnias) said :
#6

@actionparsnip: are the developers are alerted yet?

Revision history for this message
Robert Grasböck (l-mail-3) said :
#7

@actionparsnip: I use KDevelop 4.5.1 because some new features not available in 4.4.0 and stability.
The missing Subversion plugin is really bad, because I use it for my daily business.

@Velnias: you package works fine and helped me a lot. I can perfect live with that solution ;)

Revision history for this message
Velnias (velnias) said :
#8

@robert: Thanks, it is really only a rebuild with that feature re-enabled. Fortunately the code itself wasn't removed from the soure package.

It is a mystery for me what the debian developers has ridden to decide to remove the SVN plugin from build.
I had searched for a discussion or similar to understand their decision, but found nothing.

A note about devel-packages: I use precise for stability, but I inject a lot of packages from saucy, because I'm a developer too and want to get my work working without problems even on future releases too.

So, I pick the newest packages of packages relating my development from saucy, built it. Finally the launchpad builds show me if I was right :-D Additionally I use the openSUSE OBS too, and there I build against factory too.

Therefore the reason for using kdevplatform7 from saucy was EXACTLY the same like of @Robert.

Can you help with this problem?

Provide an answer of your own, or ask Velnias for more information if necessary.

To post a message you must log in.