On Wed, Nov 28, 2018 at 4:21 AM Tong Sun <[email protected]> wrote:
> Oh, thanks for spotting that. > The typo was made during my editing the ../script.log file. The > original command was correct (git remote set-url origin > [email protected]: > go-team/packages/golang-github-danverbraganza-varcaser.git): > > $ git remote -v > origin [email protected]: > go-team/packages/golang-github-danverbraganza-varcaser.git > (fetch) > origin [email protected]: > go-team/packages/golang-github-danverbraganza-varcaser.git > (push) > > I've fixed my SSH connection to salsa, then update the `gbp push` part. > and post it at > http://paste.debian.net/1053483/ > > So basically, following the steps you listed, everything went through > without any problem. > However, when I switch back to my old git, I get the original error again: > > $ gbp push --dry-run --verbose > gbp:debug: ['git', 'rev-parse', '--show-cdup'] > gbp:debug: ['git', 'rev-parse', '--is-bare-repository'] > gbp:debug: ['git', 'rev-parse', '--git-dir'] > gbp:debug: ['git', 'symbolic-ref', 'HEAD'] > gbp:debug: ['git', 'show-ref', 'refs/heads/master'] > gbp:debug: ['git', 'config', 'branch.master.remote'] > gbp:debug: ['git', 'tag', '-l', 'debian/0.0_git20151108.ce61ec4-1'] > gbp:debug: ['git', 'rev-parse', '--quiet', '--verify', > 'debian/0.0_git20151108.ce61ec4-1^{commit}'] > gbp:error: revision 'debian/0.0_git20151108.ce61ec4-1^{commit}' not found > > What could be causing such problem? > > I did some more investigation. Here is all that I have thought of: > > the good run has: > > gbp:debug: ['git', 'rev-parse', '--quiet', '--verify', > 'upstream/0.0_git20151108.ce61ec4^{commit}'] > > while the bad run has: > > gbp:debug: ['git', 'rev-parse', '--quiet', '--verify', > 'debian/0.0_git20151108.ce61ec4-1^{commit}'] > > that extra "-1" is what causing the problem: > Note that it’s not just an extra -1. The bad run is using debian/<full-version>, whereas the good run is using upstream/<upstream-version>. > > $ git rev-parse --quiet --verify upstream/0.0_git20151108.ce61ec4^{commit} > 88a5d5c6c7a557f51fbedbc76f3660079fb62eb2 > > $ git rev-parse --quiet --verify > upstream/0.0_git20151108.ce61ec4-1^{commit} > > $ echo $? > 1 > > what is causing gbp to add that extra "-1"? > > > > Then I duplicate the good repo, and update the files I've changed. > Then the good repo became bad. > > Here are all the files that I've changed, and the only one has > "git20151108" in it: > > $ grep git20151108 debian/changelog debian/compat debian/control > debian/copyright debian/docs debian/gbp.conf debian/gitlab-ci.yml > debian/rules debian/source/format debian/watch > debian/changelog:golang-github-danverbraganza-varcaser > (0.0~git20151108.ce61ec4-1) sid; urgency=medium > > Comparing to the good one: > > golang-github-danverbraganza-varcaser (0.0~git20151108.ce61ec4-1) > UNRELEASED; urgency=medium > Is the “UNRELEASED” distribution in the changelog entry the culprit maybe? > > I can't figure out how it matters. > > So, all in all, I'm at my wits ends now. > > Somebody help please. > Thx > > > On Tue, Nov 27, 2018 at 2:10 AM Michael Stapelberg > <[email protected]> wrote: > > > > In the log, you have a typo in this line: > > > > $ git remote set-url origin salssa.debian.org: > go-team/packages/golang-github-danverbraganza-varcaser.gits > > > > (salssa → salsa) > > > > Please retry without the typo. If it still doesn't work, are you sure > that your SSH key is added to your user account in salsa? > > > > On Tue, Nov 27, 2018 at 5:04 AM Tong Sun <[email protected]> wrote: > >> > >> On Mon, Nov 26, 2018 at 1:47 PM Michael Stapelberg wrote: > >> > >> > Can you reproduce this with the steps I listed? > >> > > >> > If yes, it might be a good idea to file a bug report against > git-buildpackage. > >> > >> Thanks a lot Michael for your help. I think we now have a case: > >> > >> gbp:debug: ['git', 'push', 'origin', 'tag', > >> 'upstream/0.0_git20151108.ce61ec4', '--dry-run'] > >> > >> Could you confirm that indeed we have it first please? > >> > >> The whole log is at > >> http://paste.debian.net/1053361/ > >> > >> thx > > > > > > > > -- > > Best regards, > > Michael > -- Best regards, Michael
