Re: problems with SSH key
>> > [dev@lilydev:lilypond-git]$ git fsck >> > Segmentation faultrectories: 45% (116/256) >> >> Ouch. I've never experienced such a thing with git. Maybe >> something is broken with your installation? Does removing and >> installing again help? > > Do you mean removing git itself? I'd like to be able to get back to > the work I just did, if at all possible. Yes, I meant removing git and re-installing it – git is quite a stable program, and up to now I have never seen a segfault. Fortunately, you could solve the problem, so please ignore me. Werner
Re: problems with SSH key
On Thu, Nov 14, 2019 at 9:58 PM David Nalesnik wrote: > > On Thu, Nov 14, 2019 at 9:49 PM Werner LEMBERG wrote: > > > > > > >> There is git-fsck . > > >> > > > > > > [dev@lilydev:lilypond-git]$ git fsck > > > Segmentation faultrectories: 45% (116/256) > > > > Ouch. I've never experienced such a thing with git. Maybe something > > is broken with your installation? Does removing and installing again > > help? > > > > > > Werner > > Do you mean removing git itself? I'd like to be able to get back to > the work I just did, if at all possible. > > I deleted the empty object that git commands complained about, and now > git fsck works. > > I get this output > : > [dev@lilydev:lilypond-git]$ git fsck > Checking object directories: 100% (256/256), done. > Checking objects: 100% (402883/402883), done. > error: HEAD: invalid sha1 pointer 76008183503d70d4b37a73f19e60c2438112a5a8 > error: refs/heads/dev/measure_spanner: invalid sha1 pointer > 76008183503d70d4b37a73f19e60c2438112a5a8 > Checking connectivity: 401781, done. > > (dev/measure_spanner is the name of my branch) > > By the way, git reflog gives me this: > > [dev@lilydev:lilypond-git]$ git reflog > fatal: bad object HEAD > > Any ideas how to fix this? > > Thanks, > David OK, I think I got things operational again, through Googling and blind faith... I manually checked the reflog for my branch: [dev@lilydev:lilypond-git]$ tail -n 2 .git/logs/refs/heads/dev/measure_spanner de92385d89cfbbe5f0aa95a907c5fb98496fcb28 e949231cdff5d174e76af47c49e0b2fd60e912eb Federico Bruni 1573594713 +0100reset: moving to HEAD^ e949231cdff5d174e76af47c49e0b2fd60e912eb ec0f38486e4aedcd28a89cca28464ef4f226b7bb David Nalesnik 1573595114 +0100commit: Add regression tests (Note: both commits above are authored by me; I was just a little late in updating my config.) I reset HEAD to point to the last commit on my branch: git update-ref HEAD ec0f38486e4aedcd28a89cca28464ef4f226b7bb git fsck then gave this: [dev@lilydev:lilypond-git]$ git fsck Checking object directories: 100% (256/256), done. Checking objects: 100% (402883/402883), done. error: refs/heads/dev/measure_spanner: invalid reflog entry 76008183503d70d4b37a73f19e60c2438112a5a8 error: HEAD: invalid reflog entry 76008183503d70d4b37a73f19e60c2438112a5a8 Checking connectivity: 401781, done. I then did: [dev@lilydev:lilypond-git]$ git reflog expire --stale-fix --all [dev@lilydev:lilypond-git]$ git fsck Checking object directories: 100% (256/256), done. Checking objects: 100% (402883/402883), done. Checking connectivity: 401781, done. ___ Something must have happened when I attempted to use git rebase -i to squash those two commits. That rebase is gone. Ugh. I hope this does the trick... Thanks, David
Re: problems with SSH key
On Thu, Nov 14, 2019 at 9:49 PM Werner LEMBERG wrote: > > > >> There is git-fsck . > >> > > > > [dev@lilydev:lilypond-git]$ git fsck > > Segmentation faultrectories: 45% (116/256) > > Ouch. I've never experienced such a thing with git. Maybe something > is broken with your installation? Does removing and installing again > help? > > > Werner Do you mean removing git itself? I'd like to be able to get back to the work I just did, if at all possible. I deleted the empty object that git commands complained about, and now git fsck works. I get this output : [dev@lilydev:lilypond-git]$ git fsck Checking object directories: 100% (256/256), done. Checking objects: 100% (402883/402883), done. error: HEAD: invalid sha1 pointer 76008183503d70d4b37a73f19e60c2438112a5a8 error: refs/heads/dev/measure_spanner: invalid sha1 pointer 76008183503d70d4b37a73f19e60c2438112a5a8 Checking connectivity: 401781, done. (dev/measure_spanner is the name of my branch) By the way, git reflog gives me this: [dev@lilydev:lilypond-git]$ git reflog fatal: bad object HEAD Any ideas how to fix this? Thanks, David
Re: problems with SSH key
>> There is git-fsck . >> > > [dev@lilydev:lilypond-git]$ git fsck > Segmentation faultrectories: 45% (116/256) Ouch. I've never experienced such a thing with git. Maybe something is broken with your installation? Does removing and installing again help? Werner
Re: problems with SSH key
Good god On Thu, Nov 14, 2019 at 6:36 PM David Kastrup wrote: > > There is git-fsck . > [dev@lilydev:lilypond-git]$ git fsck Segmentation faultrectories: 45% (116/256)
Re: problems with SSH key
David Nalesnik writes: > On Thu, Nov 14, 2019 at 10:21 AM Federico Bruni wrote: > >> >> >> Il giorno gio 14 nov 2019 alle 10:17, David Nalesnik >> ha scritto: >> > On Thu, Nov 14, 2019 at 9:34 AM David Nalesnik >> > wrote: >> >> >> >> On Thu, Nov 14, 2019 at 9:23 AM David Kastrup wrote: >> >> > >> >> > Rather sounds like a different problem like a dead >> >> server/connection. >> >> > Try again? >> >> >> >> Same result >> > >> > And in fact any git command I try yields these fatal errors. (I tried >> > to create a patch to back up my work, to no avail.) >> > >> >> git format-patch doesn't work either? >> >> Perhaps you need to upgrade the system? In particular the package >> ca-certificates >> > > Nor did git log. I will see about updates, but I imagine I need to clean > up the empty objects manually. There is git-fsck . -- David Kastrup
Re: problems with SSH key
On Thu, Nov 14, 2019 at 10:21 AM Federico Bruni wrote: > > > Il giorno gio 14 nov 2019 alle 10:17, David Nalesnik > ha scritto: > > On Thu, Nov 14, 2019 at 9:34 AM David Nalesnik > > wrote: > >> > >> On Thu, Nov 14, 2019 at 9:23 AM David Kastrup wrote: > >> > > >> > Rather sounds like a different problem like a dead > >> server/connection. > >> > Try again? > >> > >> Same result > > > > And in fact any git command I try yields these fatal errors. (I tried > > to create a patch to back up my work, to no avail.) > > > > git format-patch doesn't work either? > > Perhaps you need to upgrade the system? In particular the package > ca-certificates > Nor did git log. I will see about updates, but I imagine I need to clean up the empty objects manually. Thanks, David > > > >
Re: problems with SSH key
Il giorno gio 14 nov 2019 alle 10:17, David Nalesnik ha scritto: On Thu, Nov 14, 2019 at 9:34 AM David Nalesnik wrote: On Thu, Nov 14, 2019 at 9:23 AM David Kastrup wrote: > > Rather sounds like a different problem like a dead server/connection. > Try again? Same result And in fact any git command I try yields these fatal errors. (I tried to create a patch to back up my work, to no avail.) git format-patch doesn't work either? Perhaps you need to upgrade the system? In particular the package ca-certificates
Re: problems with SSH key
On Thu, Nov 14, 2019 at 10:19 AM David Nalesnik wrote: > > On Thu, Nov 14, 2019 at 10:17 AM David Nalesnik > wrote: > > > > On Thu, Nov 14, 2019 at 9:34 AM David Nalesnik > > wrote: > > > > > > On Thu, Nov 14, 2019 at 9:23 AM David Kastrup wrote: > > > > > > > > Rather sounds like a different problem like a dead server/connection. > > > > Try again? > > > > > > Same result > > > > And in fact any git command I try yields these fatal errors. (I tried > > to create a patch to back up my work, to no avail.) > > I think I will try the upvoted solution here later today: > https://stackoverflow.com/questions/11706215/how-to-fix-git-error-object-file-is-empty Unless you can think of a better idea!
Re: problems with SSH key
On Thu, Nov 14, 2019 at 10:17 AM David Nalesnik wrote: > > On Thu, Nov 14, 2019 at 9:34 AM David Nalesnik > wrote: > > > > On Thu, Nov 14, 2019 at 9:23 AM David Kastrup wrote: > > > > > > Rather sounds like a different problem like a dead server/connection. > > > Try again? > > > > Same result > > And in fact any git command I try yields these fatal errors. (I tried > to create a patch to back up my work, to no avail.) I think I will try the upvoted solution here later today: https://stackoverflow.com/questions/11706215/how-to-fix-git-error-object-file-is-empty
Re: problems with SSH key
On Thu, Nov 14, 2019 at 9:34 AM David Nalesnik wrote: > > On Thu, Nov 14, 2019 at 9:23 AM David Kastrup wrote: > > > > Rather sounds like a different problem like a dead server/connection. > > Try again? > > Same result And in fact any git command I try yields these fatal errors. (I tried to create a patch to back up my work, to no avail.)
Re: problems with SSH key
On Thu, Nov 14, 2019 at 9:23 AM David Kastrup wrote: > > David Nalesnik writes: > > > Hi all, > > > > I'm having difficulty getting my LilyDev machine to work with SSH. > > I've followed the steps in the Contributor's Guide. Below is what > > happens. I've included my config file, too. > > > > If anyone can help, I'd be very grateful. I've got a patch to submit > > but I've been struggling for days to reinstall LilyDev. > > > > Thanks, > > David > > > > BTW: ssh is not installed in the latest LilyDev release; perhaps a > > note is needed in the manual > > > > [dev@lilydev:lilypond-git]$ git pull --verbose > > The authenticity of host 'git.sv.gnu.org (209.51.188.201)' can't be > > established. > > ECDSA key fingerprint is SHA256:qRLLJ4w/GAeiDyYnbx4yWJbZXwGiYYxgNty7lAfUyuM. > > Are you sure you want to continue connecting (yes/no)? yes > > I read "yes" so this does not look like a problem with the key. Well, the Contributor's Guide description doesn't match what I got (an ECDSA instead of an RSA fingerprint), so my "yes" may have been wishful thinking? Here's the output the CG quotes: The authenticity of host 'git.sv.gnu.org (140.186.70.72)' can't be established. RSA key fingerprint is 80:5a:b0:0c:ec:93:66:29:49:7e:04:2b:fd:ba:2c:d5. Are you sure you want to continue connecting (yes/no)? > > > Warning: Permanently added 'git.sv.gnu.org,209.51.188.201' (ECDSA) to > > the list of known hosts. > > Again, this looks like the right reaction. Should work without this > prompt next time. > > > error: object file > > .git/objects/76/008183503d70d4b37a73f19e60c2438112a5a8 is empty > > error: object file > > .git/objects/76/008183503d70d4b37a73f19e60c2438112a5a8 is empty > > fatal: loose object 76008183503d70d4b37a73f19e60c2438112a5a8 (stored > > in .git/objects/76/008183503d70d4b37a73f19e60c2438112a5a8) is corrupt > > [dev@lilydev:lilypond-git]$ fatal: The remote end hung up unexpectedly > > Rather sounds like a different problem like a dead server/connection. > Try again? Same result
Re: problems with SSH key
David Nalesnik writes: > Hi all, > > I'm having difficulty getting my LilyDev machine to work with SSH. > I've followed the steps in the Contributor's Guide. Below is what > happens. I've included my config file, too. > > If anyone can help, I'd be very grateful. I've got a patch to submit > but I've been struggling for days to reinstall LilyDev. > > Thanks, > David > > BTW: ssh is not installed in the latest LilyDev release; perhaps a > note is needed in the manual > > [dev@lilydev:lilypond-git]$ git pull --verbose > The authenticity of host 'git.sv.gnu.org (209.51.188.201)' can't be > established. > ECDSA key fingerprint is SHA256:qRLLJ4w/GAeiDyYnbx4yWJbZXwGiYYxgNty7lAfUyuM. > Are you sure you want to continue connecting (yes/no)? yes I read "yes" so this does not look like a problem with the key. > Warning: Permanently added 'git.sv.gnu.org,209.51.188.201' (ECDSA) to > the list of known hosts. Again, this looks like the right reaction. Should work without this prompt next time. > error: object file > .git/objects/76/008183503d70d4b37a73f19e60c2438112a5a8 is empty > error: object file > .git/objects/76/008183503d70d4b37a73f19e60c2438112a5a8 is empty > fatal: loose object 76008183503d70d4b37a73f19e60c2438112a5a8 (stored > in .git/objects/76/008183503d70d4b37a73f19e60c2438112a5a8) is corrupt > [dev@lilydev:lilypond-git]$ fatal: The remote end hung up unexpectedly Rather sounds like a different problem like a dead server/connection. Try again? -- David Kastrup
