[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#616416: marked as done (bzr-gtk: bzr gdiff locks the branch and renders commits impossible)

Your message dated Sun, 27 Oct 2013 12:43:59 +0000
with message-id <[🔎] E1VaPhH-0003yg-R8@franck.debian.org>
and subject line Bug#719658: Removed package(s) from unstable
has caused the Debian Bug report #616416,
regarding bzr-gtk: bzr gdiff locks the branch and renders commits impossible
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 owner@bugs.debian.org
immediately.)


-- 
616416: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=616416
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: bzr-gtk
Version: 0.98.0+bzr692-1
Severity: normal

Hi.

when bzr gdiff is started, vizualising the pending uncommitted changes, it is no longer possible to commit.

$ bzr gdiff &
...
$ bzr commit src/www/admin/userlist.php
bzr: ERROR: Could not acquire lock "/home/olivier/bzr/scm.fusionforge.org/trunk/.bzr/checkout/dirstate": [Errno 11] Ressource temporairement non disponible


That's not necessary IMHO : one can open the view, reviewing pending changes and committing in //. Gdiff is read-only AFAICT, so it shouldn't prevent from changing the branch even though its view may become outdated.

Thanks in advance.


-- System Information:
Debian Release: 6.0
  APT prefers squeeze-updates
  APT policy: (500, 'squeeze-updates'), (500, 'stable')
Architecture: i386 (i686)

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

Versions of packages bzr-gtk depends on:
ii  bzr                     2.1.2-1          easy to use distributed version co
ii  python                  2.6.6-3+squeeze5 interactive high-level object-orie
ii  python-central          0.6.16+nmu1      register and build utility for Pyt
ii  python-glade2           2.17.0-4         GTK+ bindings: Glade support
ii  python-gtk2             2.17.0-4         Python bindings for the GTK+ widge
ii  python-notify           0.1.1-2+b2       Python bindings for libnotify

Versions of packages bzr-gtk recommends:
ii  bzr-dbus                     0.1~bzr39-2 D-Bus announcements plugin for Baz
pn  olive-bzr                    <none>      (no description available)
ii  python-cairo                 1.8.8-1+b1  Python bindings for the Cairo vect
pn  python-gnome2-desktop        <none>      (no description available)
ii  python-gnomekeyring          2.30.0-4    Python bindings for the GNOME keyr
ii  python-gtksourceview2        2.10.1-1    Python bindings for the GtkSourceV
ii  seahorse                     2.30.1-2    GNOME front end for GnuPG

Versions of packages bzr-gtk suggests:
pn  bzr-avahi                     <none>     (no description available)
pn  bzr-loom                      <none>     (no description available)
pn  bzr-search                    <none>     (no description available)

-- no debconf information

--- End Message ---
--- Begin Message --- 
Version: 0.103.0+bzr792-3+rm

Dear submitter,

as the package bzr-gtk has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see http://bugs.debian.org/719658

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Ansgar Burchardt (the ftpmaster behind the curtain)

--- End Message ---
Reply to: