Bug 343113

Summary:	Tell the user why Git/Bazaar support cannot be enabled [was: Can't enable Git Support]
Product:	[Applications] kdevelop	Reporter:	ali.sherif10
Component:	general	Assignee:	kdevelop-bugs-null
Status:	CONFIRMED ---
Severity:	normal	CC:	cfeck, sabbiralam.cse
Priority:	NOR	Keywords:	junior-jobs
Version First Reported In:	4.7.0
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description ali.sherif10 2015-01-21 12:22:08 UTC

At Settings -> Configure KDevelop... -> Plugins, if I select Git Support then click Apply,  Git Support returns unselected.
I noticed the same applies, if I select Bazaar Support.

Reproducible: Always

Steps to Reproduce:
1. Open Settings -> Configure KDevelop....
2. Go to  Plugins.
3. Select Git Support.
4. Click Apply.

Actual Results:  
Git Support returns unselected.

Expected Results:  
Git Support remains selected.

Notes:
1. I use 64-bit OpenSUSE 13.2 KDE.
2. After I had clicked Report Bug... -> Launch Bug Report Wizard, I found that the selected platform is "Other".

Comment 1 Kevin Funk 2015-01-21 12:23:50 UTC

Do you have the 'git' executable installed?

Comment 2 ali.sherif10 2015-01-21 12:29:49 UTC

No, but after installing it, I could enable Git Support successfully.

Comment 3 Kevin Funk 2015-01-21 13:19:30 UTC

I'll let this bug report open though. We need to tell the user *why* the Git plugin couldn't be enabled.

Comment 4 ali.sherif10 2015-01-21 13:24:15 UTC

Thanks for your help.

Comment 5 Md. Sabbir Alam 2015-02-04 17:05:50 UTC

Hello,
Is this bug is available to take and create patch. If this is available will anybody help me to get starte ? I am new in here. 
Thank you.
Regards,
Md. Sabbir Alam

Comment 6 Christoph Feck 2015-02-14 23:08:16 UTC

This bug is still available. If you need help, you should ask on the mailing lists, explain what you tried so far, and where you got stuck.

Comment 7 Justin Zobel 2021-03-09 22:47:58 UTC

Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.