Your message dated Fri, 29 Jul 2011 19:01:54 +0200
with message-id <[email protected]>
and subject line Fixed in 0.5.27
has caused the Debian Bug report #572452,
regarding git-buildpackage: git-import-org --fast-import does not look up
realname of current user
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
572452: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=572452
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: git-buildpackage
Version: 0.4.65~3.gbp3ceaa3
Severity: minor
Hi,
I thought to try --fast-import, since I had some problems with normal
import adding files that were ignored by upstreams .gitignore (and thus
didn't show up in git status when I cleaned the tree before importing).
Anyway, after importing using --fast-import, I noticed that it had
created the upstream import commit using just my username as author
name, instead of my full name (from /etc/passwd). Looking at the code,
it seems that GitRepository.get_author_info() tries to emulate git's
behaviour, but apparently neglects to do a /etc/passwd / NSS lookup when
it uses the current username as a name.
It seems this is a matter of doing
name = pwd.getpwnam(name)[4].split(',')[0]
after getting the value of $USER, with some error handling of course.
However, isn't there some way to let git do all this stuff instead of
recreating git's name guessing algorithms in gbp? That would of course
be a lot better and more predictable...
Gr.
Matthijs
--- End Message ---
--- Begin Message ---
Version: git-buildpackage/0.5.27
Hi,
the code got removedin 0.5.27.
Cheers,
-- Guido
--- End Message ---
