Bug#877464: git-remote-gcrypt: git push always behaves as if --force is given

2024-05-09 Thread Joey Hess
Joey Hess wrote: > with the old ref I saw on the remote. If the shas are different, I > check `git log --oneline $old..$src` -- if this outputs nothing, then > history is not advancing and it refuses to push that ref, and > reports the error to git. That's not quite right, because git log

Bug#877464: git-remote-gcrypt: git push always behaves as if --force is given

2024-04-27 Thread Sean Whitton
Hello, Many thanks for this. Hopefully someone will be interested in implementing it at some point. -- Sean Whitton signature.asc Description: PGP signature

Bug#877464: git-remote-gcrypt: git push always behaves as if --force is given

2024-04-26 Thread Joey Hess
I was implementing another gitremote-helper today and ran into what I think is the same problem. Since I've worked around the problem in my gitremote-helper successfully, I wanted to share what I've learned in case it can help git-remote-gcrypt. When git push is run, for a non-forced push, it

Bug#877464: git-remote-gcrypt: git push always behaves as if --force is given

2020-04-03 Thread montag451
Hi, A solution could be the use of --force-with-lease instead of --force. It would prevent the behavior observed by the OP. BR --- montag451

Bug#877464: git-remote-gcrypt: git push always behaves as if --force is given

2017-10-22 Thread Sean Whitton
control: outlook -1 git-remote-gcrypt needs a test suite before this kind of bug can be fixed Hello John, On Mon, Oct 02 2017, John Goerzen wrote: > On 10/02/2017 11:47 AM, Sean Whitton wrote: >> >> Could you say which backend you were using when you saw this, please? >> Possibly it affects

Bug#877464: git-remote-gcrypt: git push always behaves as if --force is given

2017-10-02 Thread John Goerzen
On 10/02/2017 11:47 AM, Sean Whitton wrote: > > Could you say which backend you were using when you saw this, please? > Possibly it affects all backends, but which were you able to test? Hi Sean, I tested it with both the rsync and the git:// backends and observed the same behavior with both. -

Bug#877464: git-remote-gcrypt: git push always behaves as if --force is given

2017-10-02 Thread Sean Whitton
Dear John, On Sun, Oct 01 2017, John Goerzen wrote: > The expected result here is an error, and the usual way to handle it > would be to do a git pull followed by another push attempt. > > Unfortunately, with git-remote-gcrypt, the push from repo B silently > clobbers the most recent commit made

Bug#877464: git-remote-gcrypt: git push always behaves as if --force is given

2017-10-01 Thread John Goerzen
Package: git-remote-gcrypt Version: 1.0.1-1 Severity: important Here's a secnario - I have repo A and repo B. Both have the same git-remote-gcrypt repository named origin, and both begin with the same HEAD. Now, make a commit on repo A and push it. Make a different commit on repo B and run