aborts rather than printing warning when configuration file is inaccessible

[Jelmer Vernooij]

when opening a configuration file raises PermissionDenied, bzr prints it (with a backtrace) and aborts.

Instead, it should just ignore the configuration file, print a warning and continue.

This is causing also causing problems when running the tests under fakeroot. When we create a safety net, the users' configuration file is read. If this configuration file is e.g. in /root the tests blow up spectacularly.

[Launchpad Janitor (janitor)]

This bug was fixed in the package bzr - 2.4.0-3ubuntu1

---------------
bzr (2.4.0-3ubuntu1) oneiric; urgency=low

  * Merge from Debian. Remaining changes:
   + Drop build dependencies on python-{subunit,meliae,lzma,medusa}, which are
     not in main.
   + Disable support for running selftest in parallel (requires subunit).

bzr (2.4.0-3) unstable; urgency=medium

  * Fix regression in open_write_stream, which breaks the bzr-builddeb
    testsuite. Closes: #638219, LP: #831351

bzr (2.4.0-2) unstable; urgency=medium

  * Ignore permission denied errors when opening configuration files.
    LP: #837324, Closes: #639004

bzr (2.4.0-1) unstable; urgency=low

  * New upstream release.
   + Suggest python-gpgme python-gpgme-dbg for new signatures features.
   + Build-conflict with python-gpgme for the moment because of
     failing GPG tests when it is installed.
 -- Jelmer Vernooij <email address hidden> Wed, 31 Aug 2011 17:08:56 +0200