While cloning, "remote: warning: ignoring extra bitmap file"

I hardly ever clone from my own remote. Usually just clone from local. However, this error is curious. All seems well. But, what is this bitmap file? Is there an explanation?

$ git clone https://github.com/pete4abw/lrzip-next
Cloning into ‘lrzip-next’…
remote: warning: ignoring extra bitmap file: /data/repositories/0/nw/08/eb/43/336318900/network.git/objects/pack/pack-c3e3e5435bf995559c9aadbafd402935525b3c54.pack
remote: Enumerating objects: 5383, done.
remote: Counting objects: 100% (1123/1123), done.
remote: Compressing objects: 100% (716/716), done.
remote: Total 5383 (delta 768), reused 710 (delta 391), pack-reused 4260
Receiving objects: 100% (5383/5383), 3.17 MiB | 12.69 MiB/s, done.
Resolving deltas: 100% (3566/3566), done.

It’s not about an image file but Git internals and as this is only a warning, you can probably ignore it. To learn more about reachability bitmaps, have a look here:

1 Like

Thank you. The word probably is not entirely comforting. But this does explain what might be going on. I’ll leave this issue open for a little while to see if there are other comments, then close. Thank you.

The fact that it’s a warning and not an error as well as that the file is merely ignored sounds to me like something that is of no concern. I don’t know the internals and what can cause such extra files, however.

If the remote is your own git server, then maybe there’s a repack command or something along this line to get rid of unnecessary files. It seems like some leftover file to me that the git client stumbles over.

I can trigger this using the above repository which is github hosted even when asking to skip submodules (and it doesn’t trigger for the submodule).

If it were my repository, I’d file a ticket:

If I’m compiling a program for production, and I see a warning error, gcc -Wsomething file.c, you can be sure I would correct it. Things like a missing cast or pointer conversion, or using integers of different sizes may work most of the time, but would you chance it? And if the warning is not understood it makes it more the worrisome. I know you’re probably right, but I think this should be cleaned up. Agree with @jsoref .