Package: git-buildpackage
Version: 0.4.52
Severity: normal
File: /usr/bin/git-dch

When I try to populate debian/changelog with git-dch, it bails out with:

Traceback (most recent call last):
  File "/usr/bin/git-dch", line 382, in <module>
    sys.exit(main(sys.argv))
  File "/usr/bin/git-dch", line 354, in main
    commit_msg, (commit_author, commit_email) = parse_commit(repo, 
first_commit, options)
  File "/usr/bin/git-dch", line 204, in parse_commit
    author, email = get_author(commit)
TypeError: 'NoneType' object is not iterable

Steps to reproduce:

$ git clone git://git.debian.org/git/pkg-perl/apps/padre.git
$ cd padre
$ touch debian/foo
$ git add debian/foo
$ git commit debian/foo -m 'added foo'
$ git-dch

The last release is properly tagged as debian/0.33-1. Same effect if I try
"git-dch --git-log=debian/0.33-1..HEAD"

I have tracked the problem to a "pretty = oneline" setting in ~/.gitconfig
([format] section). If I comment this setting out, git-dch does the right
thing.


Thanks,
    dam

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable'), (450, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.29-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=bg_BG.UTF-8, LC_CTYPE=bg_BG.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages git-buildpackage depends on:
ii  devscripts                   2.10.48     scripts to make the life of a Debi
ii  git-core                     1:1.6.2.4-1 fast, scalable, distributed revisi
ii  python                       2.5.4-2     An interactive high-level object-o
ii  python-dateutil              1.4.1-3     powerful extensions to the standar
ii  python-support               1.0.2       automated rebuilding support for P

Versions of packages git-buildpackage recommends:
ii  pristine-tar                  1.00       regenerate pristine tarballs

Versions of packages git-buildpackage suggests:
ii  git-load-dirs                 1.1.6+nmu2 Import upstream archives into git

-- no debconf information



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to