Bug 743011 - [abrt] fedpkg-0.5.9.2-2.fc14: config.py:247:_read:ParsingError: File contains parsing errors: /home/remote/eblake/.gitconfig
Summary: [abrt] fedpkg-0.5.9.2-2.fc14: config.py:247:_read:ParsingError: File contains...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: GitPython
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: David Cantrell
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:2830ffa7
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-03 15:15 UTC by Eric Blake
Modified: 2013-01-10 06:40 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-02 23:29:43 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (2.10 KB, text/plain)
2011-10-03 15:15 UTC, Eric Blake 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Eric Blake 2011-10-03 15:15:06 UTC 
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 2154 bytes
cmdline: /usr/bin/python /usr/bin/fedpkg pull
component: fedora-packager
executable: /usr/bin/fedpkg
kernel: 2.6.35.14-96.fc14.x86_64
package: fedpkg-0.5.9.2-2.fc14
reason: config.py:247:_read:ParsingError: File contains parsing errors: /home/remote/eblake/.gitconfig
release: Fedora release 14 (Laughlin)
time: 1317654788
uid: 14986

How to reproduce
-----
1. Apparently, fedpkg doesn't like the contents of my ~/.gitconfig, even though git manages just fine
2.
3.
Comment 1 Eric Blake 2011-10-03 15:15:09 UTC 
Created attachment 526082 [details]
File: backtrace
Comment 2 Jeff Ortel 2011-11-01 16:16:49 UTC 
I experienced this as well doing 'fedpkg build'.  The problem seems to be leading spaces on property names.  After removing the indentation, fedpkg worked.

Eg:

[user]
    name = Jeff Ortel
    email = jortel

change to:

[user]
name = Jeff Ortel
email = jortel
Comment 3 Jesse Keating 2011-11-01 17:20:36 UTC 
I believe that's actually a bug in GitPython that may be fixed by the newer build I'm putting out.
Comment 4 Jesse Keating 2012-03-02 23:29:43 UTC 
Does seem to be fixed with the latest GitPython available.
Note You need to log in before you can comment on or make changes to this bug.