#829324 iproute2: malformed git repository (missingSpaceBeforeDate: invalid author/committer line - missing space before date)

Package:
iproute2
Source:
iproute2
Description:
networking and traffic control tools
Submitter:
Daniel Kahn Gillmor
Date:
2017-12-30 03:57:06 UTC
Severity:
normal
#829324#5
Date:
2016-07-02 14:51:26 UTC
From:
To:
Hi there!

It looks like there is an error in the git repository for debian
packaging for iproute2:

0 dkg@alice:~/src/iproute2$ debcheckout iproute2
declared git repository at git://git.debian.org/git/collab-maint/pkg-iproute.git
git clone git://git.debian.org/git/collab-maint/pkg-iproute.git iproute2 ...
Cloning into 'iproute2'...
remote: Counting objects: 13601, done.
remote: Compressing objects: 100% (4151/4151), done.
error: object 4964fb2c5f519488d6270459e773ac1d4d1bf44a: missingSpaceBeforeDate: invalid author/committer line - missing space before date
fatal: Error in object
fatal: index-pack failed
checkout failed (the command above returned a non-zero exit code)
128 dkg@alice:~/src/iproute2$


note that i have the following in ~/.gitconfig to detect errors in git
repositories:

[transfer]
    fsckobjects = true
[fetch]
    fsckobjects = true
[receive]
    fsckobjects = true


If it's possible, please clean up the git repo so that it doesn't have
this error.

Thanks,
#829324#10
Date:
2016-07-03 22:04:41 UTC
From:
To:
Hi,

Daniel Kahn Gillmor wrote (02 Jul 2016 14:51:26 GMT) :

FWIW, I've just stumbled upon the same problem (trying to help with
#783276) when cloning the upstream repo:
https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git

Cheers,
--
intrigeri
#829324#17
Date:
2017-12-29 20:41:52 UTC
From:
To:
Control: tags -1 wontfix
it

Thanks for the report, but running git fsck these all look like errors
in the upstream repository tags, so they should be fixed there. It
smells like it was the result of a migration from whatever was used
before git.

Incidentally, any idea if these problems can actually be fixed without
breaking the history of the repository? Any suggestion on what do to?
Perhaps these tags should be deleted and recreated? A bit of a hassle
to sync, but doable.

Looks like they had a similar problem in collectd:

https://github.com/collectd/collectd/issues/2115

Stephen, FYI: this is easily reproducible by running "git fsck" in the
upstream repository.
#829324#24
Date:
2017-12-30 03:53:46 UTC
From:
To:
On Fri, 29 Dec 2017 21:41:52 +0100 Luca Boccassi <bluca@debian.org> wrote:

Mostly this is because older versions of git did things in messy way
and were less picky. kernel repo has same issue.