Re: [Python-modules-team] Processing of paramiko_2.7.1-1_source.changes
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: [alias] dpush = push origin : --follow-tags drelease = !gbp dch -R --commit (I left my "git drelease" alias as well, I use it just before to update the changelog...) Cheers, -- ⢀⣴⠾⠻⢶⣦⠀ Raphaël Hertzog ⣾⠁⢠⠒⠀⣿⡁ ⢿⡄⠘⠷⠚⠋The Debian Handbook: https://debian-handbook.info/get/ ⠈⠳⣄ Debian Long Term Support: https://deb.li/LTS
Re: [Python-modules-team] Processing of paramiko_2.7.1-1_source.changes
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 changes (ie, the main branch only gets pushed if there is a release tag). It certainly helps to keep the upstream and pristine-tar branches up to date, however. There is also equivalently $ gbp pull $ gbp clone to ensure all of these branches are updated from the remote without the need to switch to them in turn and push/pull them. Gordon > 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" the diffs you're pushing) but it's stuck > in my bash history so there it is > > > Anyways, it should be there now! > > indeed it's there -- thanks! > > -- > Sandro "morph" Tosi > My website: http://sandrotosi.me/ > Me at Debian: http://wiki.debian.org/SandroTosi > Twitter: https://twitter.com/sandrotosi >
Re: [Python-modules-team] Processing of paramiko_2.7.1-1_source.changes
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 pristine-tar... :/ Any trick to avoid those errors in general? Anyways, it should be there now! a. -- It is capitalism and government which stand for disorder and violence. Anarchism is the very reverse of it; it means order without government and peace without violence. - Alexander Berkman
Re: [Python-modules-team] Processing of paramiko_2.7.1-1_source.changes
> 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" the diffs you're pushing) but it's stuck in my bash history so there it is > Anyways, it should be there now! indeed it's there -- thanks! -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
Re: [Python-modules-team] Processing of paramiko_2.7.1-1_source.changes
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 > paramiko_2.7.1.orig.tar.gz > paramiko_2.7.1-1.debian.tar.xz > paramiko_2.7.1-1_amd64.buildinfo > > Greetings, > > Your Debian queue daemon (running on host usper.debian.org) > > ___ > Python-modules-team mailing list > python-modules-t...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
