Hello, I've noticed an problem on my git when I tried to checkout staging and then git pull -r.
--snip-- james@jameslilydev2:~/lilypond-git$ git status # On branch master nothing to commit (working directory clean) james@jameslilydev2:~/lilypond-git$ git checkout staging error: failed to read object d3eee73c6d278425bcf694c7bf221dc334bd2a5f at offset 434935 from .git/objects/pack/pack-0b0c25e2ea4c8652fd7fea0ea862c9d733110161.pack Switched to branch 'staging' Your branch is behind 'origin/staging' by 9 commits, and can be fast-forwarded. james@jameslilydev2:~/lilypond-git$ git pull -r First, rewinding head to replay your work on top of it... error: failed to read delta base object d3eee73c6d278425bcf694c7bf221dc334bd2a5f at offset 434935 from .git/objects/pack/pack-0b0c25e2ea4c8652fd7fea0ea862c9d733110161.pack Fast-forwarded staging to f1defa51a982cf769172cfcdd6b2612608ba2746. james@jameslilydev2:~/lilypond-git$ gitk james@jameslilydev2:~/lilypond-git$ lily-git.tcl james@jameslilydev2:~/lilypond-git$ git branch master * staging test-staging james@jameslilydev2:~/lilypond-git$ git pull -r Current branch staging is up to date. --snip-- As you can see if I keep doing a git pull -r the error 'goes away'. This is my patchy VM but I get no physical device (disk read errors) either on the VM or the underlying host. As Master and Staging are both on the same commit and because read errors are always worrying (especially to someone who works in the Storage Industry), Perhaps this is overkill, but there isn't anything urgent on, and I have backups of this VM - if anyone wants me to do 'stuff' on this install - I'm going to blow my complete VM away, reinstall LilyDev and download $LILYPOND_GIT from scratch. This will take an hour or so on my connection, so Patchy merge won't run until I get up tomorrow morning. James _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel