Re: [Python-modules-team] Processing of paramiko_2.7.1-1_source.changes

2020-05-13 Thread Raphael Hertzog
On Mon, 11 May 2020, Sandro Tosi wrote: > when i push i always do > > $ git push --all ; git push --tags To push only branches which are shared on both sides and the associated tags I use this: $ git push origin : --follow-tags Which I alias as "git dpush" so I have this in ~/.gitconfig:

Re: [Python-modules-team] Processing of paramiko_2.7.1-1_source.changes

2020-05-12 Thread Gordon Ball
On Mon, May 11, 2020 at 10:37:47PM -0400, Sandro Tosi wrote: > > Any trick to avoid those errors in general? > You can also do $ gbp push which will automatically push the main (master or debian/master), upstream and pristine-tar branches. However, by default it does not push UNRELEASED

Re: [Python-modules-team] Processing of paramiko_2.7.1-1_source.changes

2020-05-11 Thread Antoine Beaupré
On 2020-05-11 22:27:57, Sandro Tosi wrote: > Antoine, you did not push the upstream branch. please do so, in order > to keep the repo consistent Oops, sorry about that, somehow I forgot that one... This is one of my problems with the multi-branch layout: I always forgot either upstream or

Re: [Python-modules-team] Processing of paramiko_2.7.1-1_source.changes

2020-05-11 Thread Sandro Tosi
> Any trick to avoid those errors in general? when i push i always do $ git push --all ; git push --tags i also have these in ~/.gitconfig [push] default = current followTags = true with should make the `git push --tags` unnecessary after `git push --all` (as tags will "follow"

Re: [Python-modules-team] Processing of paramiko_2.7.1-1_source.changes

2020-05-11 Thread Sandro Tosi
Antoine, you did not push the upstream branch. please do so, in order to keep the repo consistent On Mon, May 11, 2020 at 10:15 PM Debian FTP Masters wrote: > > paramiko_2.7.1-1_source.changes uploaded successfully to localhost > along with the files: > paramiko_2.7.1-1.dsc >