Bug 708251

Summary: git repo-config is deprecated in favor of git-config
Product: [Fedora] Fedora Reporter: Elbin Pallimalil <elbin.p>
Component: qgitAssignee: Dan HorĂ¡k <dan>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: dan
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: qgit-2.3-4.fc15 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-09 00:01:28 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Warning message. none

Description Elbin Pallimalil 2011-05-27 02:48:58 UTC
Created attachment 501229 [details]
Warning message.

Description of problem:
The attached warning is always shown on opening a repository.

Version-Release number of selected component (if applicable):
2.3


How reproducible:
Always.


Steps to Reproduce:
1.Open a repository from qgit.
  
Actual results:
Warning messsage displayed.

Expected results:
No warning message.


Additional info:

Comment 1 Fedora Update System 2011-05-27 09:38:13 UTC
qgit-2.3-4.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/qgit-2.3-4.fc15

Comment 2 Fedora Update System 2011-05-27 20:29:44 UTC
Package qgit-2.3-4.fc15:
* should fix your issue,
* was pushed to the Fedora 15 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing qgit-2.3-4.fc15'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/qgit-2.3-4.fc15
then log in and leave karma (feedback).

Comment 3 Fedora Update System 2011-06-09 00:01:23 UTC
qgit-2.3-4.fc15 has been pushed to the Fedora 15 stable repository.  If problems still persist, please make note of it in this bug report.