Your message dated Mon, 25 Jul 2016 08:45:28 +0200 with message-id <[email protected]> and subject line Re: Bug#708296: git-buildpackage: gbp-pull "sleeps" with git+ssh:// and ssh sockets has caused the Debian Bug report #708296, regarding git-buildpackage: gbp-pull "sleeps" with git+ssh:// and ssh sockets to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 708296: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708296 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: git-buildpackage Version: 0.6.0~git20130506 Severity: normal -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 gbp-pull from the git-buildpackage uploaded to unstable last week has an unpleasant effect (the version in testing is not affected). It tends to fall asleep under certain circumstances: The circumstances or: How to reproduce: 1) a repo with a remote that uses ssh 2) ssh with sockets [0] 3) calling gbp-pull when the socket for the repo's server doesn't exist yet [0] e.g. Host * ControlPath ~/.ssh/sock/%r@%h:%p ControlMaster auto ControlPersist 60 In this combination, gbp-pull waits for ControlPersist seconds. (This does not happen with non-ssh URLs or when the socket exists due to an earlier call to git or ssh or gbp-pull). The problem seems to be caused by commit 8541450; some poking around with ipython and randomly changing the code seems to suggest that the problem is in the subprocess.Popen/communicate call in gbp/git/repository.py line 146, more precisely in the stderr handling; with the current code, the gbp-pull waits until the persistent ssh socket gets killed (in select.poll()). If stderr is not set to a PIPE then this waiting doesn't happen. It looks like Popen waits for the ssh socket ... Unfortunately I have no idea how to fix this, and capturing stderr doesn't sound like a bad idea :) PS: http://bugs.python.org/issue4216 sounds similar. Cheers, gregor - -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'experimental'), (500, 'testing'), (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.8-1-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=de_AT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages git-buildpackage depends on: ii devscripts 2.13.2 ii git 1:1.7.10.4-2 ii man-db 2.6.3-6 ii python 2.7.3-5 ii python-dateutil 1.5+dfsg-0.1 Versions of packages git-buildpackage recommends: ii cowbuilder 0.72 ii pristine-tar 1.28 Versions of packages git-buildpackage suggests: ii python-notify 0.1.1-3 ii unzip 6.0-9 - -- no debconf information -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJRkqUDAAoJELs6aAGGSaoGtVIP/RQ9T+ZX0g3fsweHtDBbc00E 09luDCEgHIVqSq00as//kZzSxNhLpbyURnM0e3/O0EjRJKezLY5so5YTLmf7PYom JAADxTPWNk0tOdLLMBeSX9MP/GKM/WVozyxvFj521Ct6vfEsXqesrOn3sCTINt4H GhdcJMZDcLPSifg0iuu42wB2hOw3NeMd3rHh2dMxOvPkfutxDSoCSCbQNFkTz02a d15UAYi1BI/W4VGQmhgzQJj3AQ7hrtqjwbZpiDtdvrSXmIoqB1q2ogMbsvRPz8Hk 52nqL2nhYXG8JBKi78xws5ew105G21PYdeScgj6vTW19UHp2OzK/FQv5F5Sz1rUR GjgVmpgmsqZe4mwvfuXO7y6+w4Bxi+HUPDd+bnznjOcCliyVItXz+GZ321eziTfx /55LPYu02eIOIw4tlJlBHt/eDfHWtfrUYrIDvV2zoNjGd/lW/wilbVBhUtOWX0Lg 7j1aowZU6yCzqRcJlMpMcDbVD1IyBX4cvE9HcwRNxiYV7lRLlkbkvyr110ynbRWe +fKBM5mklGwYMvCgM5aG1zoEKYAoyfYhoMbzFqfABwu7SxfZkkjft+bc/VMdhkJt ffvPaW7l8k78RAiS+XLl2Xh7vWAU5bx/MP6UOcVjtfJyeEw4ml1Y3kGlUPvYFP/4 3glKRNQuTV6Bfhr5l567 =ba88 -----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---On Sun, Jun 30, 2013 at 07:43:16PM +0200, gregor herrmann wrote: > On Sun, 30 Jun 2013 16:04:41 +0200, Guido Günther wrote: > > > > Unfortunately I have no idea how to fix this, and capturing stderr > > > doesn't sound like a bad idea :) > > > > Here's a possible solution within openssh: > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714526 > > Great, thanks! This work now since this bug has been fixed with the recent ssh upload. Cheers, -- Guido
--- End Message ---
