To reproduce, create or open a project. It does not even have to use subversion. Upstream bug is https://bugs.kde.org/show_bug.cgi?id=284061 This is a problem for gentoo users, because subversion is enforced (see bug #347547). Maybe kdevelop should depend on <subversion-1.7.0 until upstream bug is fixed? Reproducible: Always
as is discussed in bug #387183 kdevelop and kdevplatform does not really depend on subversion so it can be removed thus solving the problem.
Thanks for looking into this. I agree that the subversion dependency of kdevplatform should be removed, but also maybe kdevelop should block svn-1.7 as a heads up for users who explicitly want to have svn support in kdevelop. Anyway, the upstream bug is making some progress and it looks like it will be resolved soon.
The dependency on subversion is gone... the rest needs a bit of thinking. Tony, should we place a blocker !>=subversion-1.7.0 here?
(In reply to comment #3) > Tony, should we place a blocker !>=subversion-1.7.0 here? That seems an acceptable workaround; I have no plans to stabilise 1.7.X at this point in time. (The build system needs more love, and there is word of cross-compilation issues)
OK the blocker is committed. Keeping the bug open to keep track of the issue.
Instead of blocking it what you can do is just disable the subversion plugin from the KDevelop Preferences.
According to Daniel Salas I think that block kdevelop is very radical. Furthermore, in my opinion this check (blocking subversion 1.7) should be associated to the kdevplatform subversion USE flag instead of the kadevelop package. I have no bug after merging subversion-1.7.1 + kdevplatform-1.2.3[-subversion] + kdevelop-4.2.3
Sorry, this block of >=svn-1.7 is too severe in my opinion. Please think of another solution. I have my SVN repos on the same machine as I develop with. Now I must either uninstall my IDE, or I can't commit changes. I also can't move back to svn 1.6.x as there was an architecture change when upgrading to 1.7.
(In reply to comment #8) > Sorry, this block of >=svn-1.7 is too severe in my opinion. Please think of > another solution. > > I have my SVN repos on the same machine as I develop with. Now I must either > uninstall my IDE, or I can't commit changes. > > I also can't move back to svn 1.6.x as there was an architecture change when > upgrading to 1.7. My solution waiting a cleaner solution : * emerge dev-util/kdevplatform without subversion : # USE="-subversione emerge dev-util/kdevplatform * remove the subversion check # equery w kdevelop => give /usr/portage/dev-util/kdevelop/kdevelop-4.2.3.ebuild for me * remove the line containing "!>=dev-vcs/subversion-1.7.0" # ebuild /usr/portage/dev-util/kdevelop/kdevelop-4.2.3.ebuild manifest * build & install kdevelop # ebuild /usr/portage/dev-util/kdevelop/kdevelop-4.2.3.ebuild merge enjoy!
EDIT: little fix.. My solution waiting a cleaner solution : * emerge dev-util/kdevplatform without subversion : # USE="-subversion" emerge dev-util/kdevplatform * remove the subversion check # equery w kdevelop => give /usr/portage/dev-util/kdevelop/kdevelop-4.2.3.ebuild for me * remove the line containing "!>=dev-vcs/subversion-1.7.0" # ebuild /usr/portage/dev-util/kdevelop/kdevelop-4.2.3.ebuild manifest * build & install kdevelop # ebuild /usr/portage/dev-util/kdevelop/kdevelop-4.2.3.ebuild merge enjoy!
The blocker is moved from kdevelop to kdevplatform-1.2.2 and -1.2.3. Please try kdevplatform-1.2.3-r1, it should be fixed there.
