Package: git-buildpackage Version: 0.5.16 Severity: normal Currently, git-import-dsc will properly set the date on the commits on the Debian branch (using the changelog). However, for the upstream tarball, it doesn't do anything.
The result is that you have history with upstream commits in the future, relative to the Debian commits (which come *LATER* in history). This is ugly as all heck, and completely insane. git-import-dsc needs to set the commit dates of the upstream branch too! I suppose it should use the orig tarball date (or, with multiple tarballs, the latest date of the set) for the "new upstream" commit. In the worst case, it should use the changelog date (as the Debian commit will do). Right now, I have to manually fix all upstream commit dates when creating the initial repository. -- System Information: Debian Release: 6.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32.28 (SMP w/8 CPU cores) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages git-buildpackage depends on: ii devscripts 2.10.69 scripts to make the life of a Debi ii git [git-core] 1:1.7.2.3-2.2 fast, scalable, distributed revisi ii git-core 1:1.7.2.3-2.2 fast, scalable, distributed revisi ii python 2.6.6-3+squeeze4 interactive high-level object-orie ii python-dateutil 1.4.1-3 powerful extensions to the standar ii python-support 1.0.10 automated rebuilding support for P Versions of packages git-buildpackage recommends: ii cowbuilder 0.62+nmu2 pbuilder running on cowdancer ii pristine-tar 1.11 regenerate pristine tarballs Versions of packages git-buildpackage suggests: ii git-load-dirs 1.1.8 Import upstream archives into git ii python-notify 0.1.1-2+b2 Python bindings for libnotify -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
