Your message dated Mon, 29 Jan 2007 16:47:02 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#374673: fixed in bzr 0.14-1
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: bzr
Version: 0.8.2-3
Severity: wishlist

If I do such things as 'bzr info', 'bzr diff' and 'bzr status', I get a
hard error if I do so in a directory I don't have write permissions to,
due to temporary files.

It'd be really really convenient if this were possible, like it's
possible with svn, so that one can quickly look at a status of a branch
without needing to branch.

--Jeroen

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-686
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)

Versions of packages bzr depends on:
ii  python2.4                     2.4.3-7    An interactive high-level object-o
ii  python2.4-celementtree        1.0.5-5    Light-weight toolkit for XML proce

bzr recommends no packages.

-- no debconf information

-- 
Jeroen van Wolffelaar
[EMAIL PROTECTED] (also for Jabber & MSN; ICQ: 33944357)
http://Jeroen.A-Eskwadraat.nl


--- End Message ---
--- Begin Message ---
Source: bzr
Source-Version: 0.14-1

We believe that the bug you reported is fixed in the latest version of
bzr, which is due to be installed in the Debian FTP archive:

bzr_0.14-1.diff.gz
  to pool/main/b/bzr/bzr_0.14-1.diff.gz
bzr_0.14-1.dsc
  to pool/main/b/bzr/bzr_0.14-1.dsc
bzr_0.14-1_all.deb
  to pool/main/b/bzr/bzr_0.14-1_all.deb
bzr_0.14.orig.tar.gz
  to pool/main/b/bzr/bzr_0.14.orig.tar.gz



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Wouter van Heyst <[EMAIL PROTECTED]> (supplier of updated bzr package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Wed, 24 Jan 2007 00:05:48 +0100
Source: bzr
Binary: bzr
Architecture: source all
Version: 0.14-1
Distribution: experimental
Urgency: low
Maintainer: Rob Weir <[EMAIL PROTECTED]>
Changed-By: Wouter van Heyst <[EMAIL PROTECTED]>
Description: 
 bzr        - bazaar-ng, the next-generation distributed version control system
Closes: 374673 389518 395203 397535 397852
Changes: 
 bzr (0.14-1) experimental; urgency=low
 .
   * New upstream release
     + More gracefully deals with readonly branches (Closes: #374673)
   * Acknowledge NMUs. (Closes: #395203, #389518, #397535, #397852)
   * Bump debhelper compat to 5.
   * Comply with python policy mandated dependencies of debhelper and
     pycentral.
   * Flip DEB_BUILD_OPTIONS logic on the testsuite until someone figures out
     why it intermittently hangs under fakeroot.
Files: 
 3421ab53e5dd72e157702d2d72415a32 920 devel optional bzr_0.14-1.dsc
 281c777f377cc149b6ba60c720f70033 1159335 devel optional bzr_0.14.orig.tar.gz
 d35be55417e2753bfaa967d2979341ec 7518 devel optional bzr_0.14-1.diff.gz
 9b7fcd8f8480f6eb947c85deb7a00116 1156586 devel optional bzr_0.14-1_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFFviIo5M5hmdCYCpkRAuiKAJoClALZpP0swanbEsgVhRyEt6TuegCg4p3v
ww8BdS4Yki8uXfSxXsljeJE=
=3QpB
-----END PGP SIGNATURE-----


--- End Message ---

Reply via email to