bzr rebase leaves a stale lock lying around after a DNS error

[Jelmer Vernooij]

  affects bzr-rewrite
  status triaged
  importance medium

"bzr rebase" leaves a stale lock lying around after a DNS error. Example:

  $ bzr rebase
  lp:~zookeepr-contributors/zookeepr/contributors
  bzr: ERROR: Connection error: Couldn't resolve host
  'xmlrpc.edge.launchpad.net' [Errno -2] Name or service not known
  $ bzr rebase
  lp:~zookeepr-contributors/zookeepr/contributors
  Unable to obtain lock
  file:///home/rstuart/zookeeper/contributors/.bzr/branch/lock
  held by <email address hidden> on host russell-laptop [process
  #17416]
  locked 33 seconds ago
  Will continue to try until 19:09:39, unless you press Ctrl-C.
  See "bzr help break-lock" for more.
  $

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages bzr-rewrite depends on:
ii bzr 2.1.2-1 easy to use distributed version co
ii python 2.6.6-3+squeeze4 interactive high-level object-orie
ii python-central 0.6.16+nmu1 register and build utility for Pyt

bzr-rewrite recommends no packages.

bzr-rewrite suggests no packages.

-- no debconf information

_______________________________________________
Pkg-bazaar-maint mailing list
<email address hidden>
http://lists.alioth.debian.org/mailman/listinfo/pkg-bazaar-maint