From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: B Smith-Mannschott Newsgroups: gmane.emacs.devel Subject: Re: bzr branch makes bogus "No space left on device" claim and dies Date: Fri, 8 Jan 2010 22:03:32 +0100 Message-ID: <28c656e21001081303p3a86f2c6y8aac642f43ded6fe@mail.gmail.com> References: <28c656e21001050711v601b275fm837d5e7ea2126d2b@mail.gmail.com> <878wccb7ix.fsf@bnikolic.co.uk> <28c656e21001070132r2da47b39iba82d0d7c9567b53@mail.gmail.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1262984630 5619 80.91.229.12 (8 Jan 2010 21:03:50 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 8 Jan 2010 21:03:50 +0000 (UTC) Cc: emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jan 08 22:03:43 2010 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1NTLzh-0006xn-32 for ged-emacs-devel@m.gmane.org; Fri, 08 Jan 2010 22:03:41 +0100 Original-Received: from localhost ([127.0.0.1]:33632 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NTLzh-0004xo-NK for ged-emacs-devel@m.gmane.org; Fri, 08 Jan 2010 16:03:41 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NTLzb-0004vR-Qf for emacs-devel@gnu.org; Fri, 08 Jan 2010 16:03:35 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NTLzb-0004uJ-31 for emacs-devel@gnu.org; Fri, 08 Jan 2010 16:03:35 -0500 Original-Received: from [199.232.76.173] (port=53804 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NTLza-0004u5-UN for emacs-devel@gnu.org; Fri, 08 Jan 2010 16:03:34 -0500 Original-Received: from ey-out-1920.google.com ([74.125.78.149]:13557) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NTLza-0002rj-Bl for emacs-devel@gnu.org; Fri, 08 Jan 2010 16:03:34 -0500 Original-Received: by ey-out-1920.google.com with SMTP id 4so3082563eyg.34 for ; Fri, 08 Jan 2010 13:03:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=dpIzc8+gAHCScOF6uwX/zfMlmKrWZcT3PJrGGb/1ZM4=; b=sut2/NGxMbck4Kl/HYevchBOly3IHs8itViOYC+WYXWXeAkXiP6xSJJuimBmgMJrOY auhovJiVcdinhywzAZiMhbcUDsHkQyBMDqIvvt21w1y9eA9ymrfozLT2QLTLp6Vrxozu +jzbGa9UVZ99kXj0oU4rUPXPyt3W7fXlFmA2o= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=oTTtWWBIYkKpK08dg8jquzVTX8ssmMYEn7onq49TTYInlXRCVt+bxIpHw1p8L37AAN Ndgy6il4j9tJmOv9YRg43IsLqkl/W9BGw9j4j1vEpdzF83mZxf7XqATMDKh1Xo3KuxkG qafIWRwzqE1+sH0x5KCHfeyyS7v4U55JJtH/I= Original-Received: by 10.213.51.208 with SMTP id e16mr1850495ebg.5.1262984612938; Fri, 08 Jan 2010 13:03:32 -0800 (PST) In-Reply-To: X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:119733 Archived-At: On Thu, Jan 7, 2010 at 15:48, Stefan Monnier wro= te: >> My ~/.bzr.log was owned by root. =C2=A0This was the cause of the trouble= . > > Make sure you report this problem to the Bazaar people. =C2=A0You should = have > a gotten a more useful error message. https://bugs.launchpad.net/bzr/+bug/296445 This issue was filed about a year ago. James Westby reports that the message is produced by the logging library they're using without communicating this back to the application. Robert Collins asserts, correctly, that detecting permissions problems on .bzr.log is possible independently of what the logging library may do or not do. Nicholas Allen offers a workaround for the problem that isn't actually a workaround for *this problem*. I suppose I could grab the bzr code and take a whack at it myself. (Basically I'd just check for writability of .bzr.log early in startup and write something more descriptive to STDERR if I find it to be unwritable. Not pretty, but serviceable.) Maybe next week. // Ben