# push to backup repo periodically fails with "not fast forward" 5 messages from 2008-12-22 to 2008-12-22. Participants: davetron5000, Felipe Contreras, David Copeland, Nicolas Pitre. Thread: https://gitlist.dev/t/16836 ## davetron5000, 2008-12-22 16:24 Subject: push to backup repo periodically fails with "not fast forward" Message-ID: <19016122-e19d-4885-8b0f-dec7b686c6ea@o4g2000pra.googlegroups.com> URL: https://gitlist.dev/e/19016122-e19d-4885-8b0f-dec7b686c6ea%40o4g2000pra.googlegroups.com ``` I have a repo on another disk that I ONLY use to backup my in-use local repo. I have a post-commit hook that does the push (git push -- all remote-repo-name) >git commit -a -m 'some change' Counting objects: 71, done. Compressing objects: 100% (26/26), done. Writing objects: 100% (29/29), 2.31 KiB, done. Total 29 (delta 12), reused 0 (delta 0) Unpacking objects: 100% (29/29), done. To file:///Volumes/Git/pose/main 22d7f10..0037aaf bimonthly-frequency -> bimonthly-frequency ! [rejected] master -> master (non-fast forward) error: failed to push some refs to 'file:///Volumes/Git/pose/main' Created commit 0037aaf: Removed assertion that made no sense. 1 files changed, 0 insertions(+), 2 deletions(-) I'm using git as a front-end to Subversion, but I can't figure out why this is happening. The repo at /Volumes/Git/pose/main is NEVER pulled from or pushed to by anything other than my hook. I can't understand why any push to it would NOT be a fast-forward. Any ideas how I can figure out what's going on? ``` ## Felipe Contreras, 2008-12-22 17:11 Subject: Re: push to backup repo periodically fails with "not fast forward" Message-ID: <94a0d4530812220911l37b825edj55178658f24755c1@mail.gmail.com> URL: https://gitlist.dev/e/94a0d4530812220911l37b825edj55178658f24755c1%40mail.gmail.com In-Reply-To: <19016122-e19d-4885-8b0f-dec7b686c6ea@o4g2000pra.googlegroups.com> ``` On Mon, Dec 22, 2008 at 6:24 PM, davetron5000 wrote: > I have a repo on another disk that I ONLY use to backup my in-use > local repo. I have a post-commit hook that does the push (git push -- > all remote-repo-name) > >>git commit -a -m 'some change' > Counting objects: 71, done. > Compressing objects: 100% (26/26), done. > Writing objects: 100% (29/29), 2.31 KiB, done. > Total 29 (delta 12), reused 0 (delta 0) > Unpacking objects: 100% (29/29), done. > To file:///Volumes/Git/pose/main > 22d7f10..0037aaf bimonthly-frequency -> bimonthly-frequency > ! [rejected] master -> master (non-fast forward) > error: failed to push some refs to 'file:///Volumes/Git/pose/main' > Created commit 0037aaf: Removed assertion that made no sense. > 1 files changed, 0 insertions(+), 2 deletions(-) > > I'm using git as a front-end to Subversion, but I can't figure out why > this is happening. > > The repo at /Volumes/Git/pose/main is NEVER pulled from or pushed to > by anything other than my hook. I can't understand why any push to it > would NOT be a fast-forward. > > Any ideas how I can figure out what's going on? Do you rebase your original repo? -- Felipe Contreras ``` ## David Copeland, 2008-12-22 17:15 Subject: Re: push to backup repo periodically fails with "not fast forward" Message-ID: URL: https://gitlist.dev/e/f95d47890812220915h5286d2bdv7c8412ecf77be999%40mail.gmail.com In-Reply-To: <94a0d4530812220911l37b825edj55178658f24755c1@mail.gmail.com> ``` the original gets rebased from a git svn rebase on occasion; so I guess that is causing things to not be fast-forward. I guess all I really want to do is keep a duplicate copy of my repo somewhere else. Should I just use --force in my hook, or abandon git as the mechanism and use rsync? Dave On Mon, Dec 22, 2008 at 12:11 PM, Felipe Contreras wrote: > On Mon, Dec 22, 2008 at 6:24 PM, davetron5000 wrote: >> I have a repo on another disk that I ONLY use to backup my in-use >> local repo. I have a post-commit hook that does the push (git push -- >> all remote-repo-name) >> >>>git commit -a -m 'some change' >> Counting objects: 71, done. >> Compressing objects: 100% (26/26), done. >> Writing objects: 100% (29/29), 2.31 KiB, done. >> Total 29 (delta 12), reused 0 (delta 0) >> Unpacking objects: 100% (29/29), done. >> To file:///Volumes/Git/pose/main >> 22d7f10..0037aaf bimonthly-frequency -> bimonthly-frequency >> ! [rejected] master -> master (non-fast forward) >> error: failed to push some refs to 'file:///Volumes/Git/pose/main' >> Created commit 0037aaf: Removed assertion that made no sense. >> 1 files changed, 0 insertions(+), 2 deletions(-) >> >> I'm using git as a front-end to Subversion, but I can't figure out why >> this is happening. >> >> The repo at /Volumes/Git/pose/main is NEVER pulled from or pushed to >> by anything other than my hook. I can't understand why any push to it >> would NOT be a fast-forward. >> >> Any ideas how I can figure out what's going on? > > Do you rebase your original repo? > > -- > Felipe Contreras > ``` ## Felipe Contreras, 2008-12-22 17:19 Subject: Re: push to backup repo periodically fails with "not fast forward" Message-ID: <94a0d4530812220919t25233fa9ub461c86f10ec366d@mail.gmail.com> URL: https://gitlist.dev/e/94a0d4530812220919t25233fa9ub461c86f10ec366d%40mail.gmail.com In-Reply-To: ``` On Mon, Dec 22, 2008 at 7:15 PM, David Copeland wrote: > the original gets rebased from a git svn rebase on occasion; so I > guess that is causing things to not be fast-forward. > > I guess all I really want to do is keep a duplicate copy of my repo > somewhere else. Should I just use --force in my hook, or abandon git > as the mechanism and use rsync? I would manually do 'git push backup' at certain points since not all my commits are meant to be backed up, specially on temporal feature branches. But --force should do the trick. -- Felipe Contreras ``` ## Nicolas Pitre, 2008-12-22 18:27 Subject: Re: push to backup repo periodically fails with "not fast forward" Message-ID: URL: https://gitlist.dev/e/alpine.LFD.2.00.0812221326490.30035%40xanadu.home In-Reply-To: ``` On Mon, 22 Dec 2008, David Copeland wrote: > the original gets rebased from a git svn rebase on occasion; so I > guess that is causing things to not be fast-forward. > > I guess all I really want to do is keep a duplicate copy of my repo > somewhere else. Should I just use --force in my hook, or abandon git > as the mechanism and use rsync? Using --force is definitively better than rsync. Nicolas ```