List for cgit developers and users
 help / color / mirror / Atom feed
* git-fsck complains about cgit repo
@ 2018-08-15 13:32 konstantin
  2018-08-15 14:08 ` john
  0 siblings, 1 reply; 2+ messages in thread
From: konstantin @ 2018-08-15 13:32 UTC (permalink / raw)


Hi, all:

Since cgit is mirrored to git.kernel.org, which gets routine fsck 
treatment, I started getting the following error reports:

  error: bad config line 5 in blob .gitmodules
  error in blob 51dd1eff1edc663674df9ab85d2786a40f7ae3a5: gitmodulesParse: could not parse gitmodules blob

I can easily reproduce this:

user at chatter:/tmp$ rpm -q git
git-2.17.1-3.fc28.x86_64
user at chatter:/tmp$ git clone --mirror https://git.zx2c4.com/cgit
Cloning into bare repository 'cgit.git'...
remote: Counting objects: 7043, done.
remote: Compressing objects: 100% (2679/2679), done.
remote: Total 7043 (delta 4933), reused 6211 (delta 4347)
Receiving objects: 100% (7043/7043), 8.71 MiB | 1.89 MiB/s, done.
Resolving deltas: 100% (4933/4933), done.
user at chatter:/tmp$ cd cgit.git/
user at chatter:/tmp/cgit.git$ git fsck
Checking object directories: 100% (256/256), done.
error: bad config line 5 in blob .gitmodules
error in blob 51dd1eff1edc663674df9ab85d2786a40f7ae3a5: gitmodulesParse: could not parse gitmodules blob
Checking objects: 100% (7043/7043), done.
user at chatter:/tmp/cgit.git$ 

Is that something that can be fixed, or should I just ignore this error?

-K
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: not available
URL: <http://lists.zx2c4.com/pipermail/cgit/attachments/20180815/d29be375/attachment.asc>


^ permalink raw reply	[flat|nested] 2+ messages in thread

* git-fsck complains about cgit repo
  2018-08-15 13:32 git-fsck complains about cgit repo konstantin
@ 2018-08-15 14:08 ` john
  0 siblings, 0 replies; 2+ messages in thread
From: john @ 2018-08-15 14:08 UTC (permalink / raw)


On Wed, Aug 15, 2018 at 09:32:18AM -0400, Konstantin Ryabitsev wrote:
> Since cgit is mirrored to git.kernel.org, which gets routine fsck 
> treatment, I started getting the following error reports:
> 
>   error: bad config line 5 in blob .gitmodules
>   error in blob 51dd1eff1edc663674df9ab85d2786a40f7ae3a5: gitmodulesParse: could not parse gitmodules blob
> 
> I can easily reproduce this:
> 
> user at chatter:/tmp$ rpm -q git
> git-2.17.1-3.fc28.x86_64
> user at chatter:/tmp$ git clone --mirror https://git.zx2c4.com/cgit
> Cloning into bare repository 'cgit.git'...
> remote: Counting objects: 7043, done.
> remote: Compressing objects: 100% (2679/2679), done.
> remote: Total 7043 (delta 4933), reused 6211 (delta 4347)
> Receiving objects: 100% (7043/7043), 8.71 MiB | 1.89 MiB/s, done.
> Resolving deltas: 100% (4933/4933), done.
> user at chatter:/tmp$ cd cgit.git/
> user at chatter:/tmp/cgit.git$ git fsck
> Checking object directories: 100% (256/256), done.
> error: bad config line 5 in blob .gitmodules
> error in blob 51dd1eff1edc663674df9ab85d2786a40f7ae3a5: gitmodulesParse: could not parse gitmodules blob
> Checking objects: 100% (7043/7043), done.
> user at chatter:/tmp/cgit.git$ 
> 
> Is that something that can be fixed, or should I just ignore this error?

I think this is historic because CGit had a submodule before
git-submodule was invented (in fact, looking at the history I think
git-submodule was derived from CGit's earlier implementation).

The format of .gitmodules in the original CGit implementation was
simpler than git-submodule uses and that is the source of the complaint.

If you can ignore it just for that blob that would be best, since I hope
we don't introduce invalid .gitsubmodule entries in the future.


Regards,
John


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2018-08-15 14:08 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-08-15 13:32 git-fsck complains about cgit repo konstantin
2018-08-15 14:08 ` john

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).