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

Bug#207428: marked as done (A lot of errors when /tmp is mounted over NFS)

Your message dated Wed, 12 May 2004 23:30:52 +0200
with message-id <40A2978C.1010400@hardware.no>
and subject line Not a dpkg bug
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)

Received: (at submit) by bugs.debian.org; 26 Aug 2003 23:56:02 +0000
>From arturcz@hell.pl Tue Aug 26 18:55:31 2003
Return-path: <arturcz@hell.pl>
Received: from blabluga.hell.pl [] 
	by master.debian.org with esmtp (Exim 3.35 1 (Debian))
	id 19rmof-00008k-00; Tue, 26 Aug 2003 18:01:33 -0500
Received: by blabluga.hell.pl (Postfix, from userid 1000)
	id A479615862; Wed, 27 Aug 2003 01:01:23 +0200 (CEST)
Date: Wed, 27 Aug 2003 01:01:22 +0200
From: "Artur R. Czechowski" <arturcz@hell.pl>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: A lot of errors when /tmp is mounted over NFS
Message-ID: <20030826230122.GN8964@blabluga.hell.pl>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-2
Content-Disposition: inline
User-Agent: Mutt/1.3.28i
X-Reportbug-Version: 2.24
Organization: none
X-Operating-System: Linux zlom 2.6.0-test2
X-URL: http://hell.pl/arturcz/
Delivered-To: submit@bugs.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0
X-Spam-Checker-Version: SpamAssassin 2.53-bugs.debian.org_2003_8_17 (

Package: apt-listchanges
Version: 2.42
Severity: normal
Tags: sid


If /tmp is over NFS apt-listchanges returns a heap of errors:
rm: cannot remove directory `/tmp/dpkgJtcjXM': Directory not empty
rm cleanup failed, code 256


-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux zlom 2.6.0-test2 #4 Sun Aug 3 14:13:26 CEST 2003 i686
Locale: LANG=C, LC_CTYPE=pl_PL

Versions of packages apt-listchanges depends on:
ii  apt                           0.5.9      Advanced front-end for dpkg
ii  debconf                       1.3.12     Debian configuration management sy
ii  python                        2.3-4      An interactive high-level object-o
ii  python-apt                    0.5.8      Python interface to libapt-pkg
ii  ucf                           0.20       Update Configuration File: preserv

-- debconf information:
* apt-listchanges/confirm: true
* apt-listchanges/frontend: pager
* apt-listchanges/email-address: 
* apt-listchanges/save-seen: true

Received: (at 165882-done) by bugs.debian.org; 12 May 2004 21:30:58 +0000
>From tfheen@hardware.no Wed May 12 14:30:57 2004
Return-path: <tfheen@hardware.no>
Received: from gamma.hardware.no [] 
	by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
	id 1BO1JZ-0004Ry-00; Wed, 12 May 2004 14:30:57 -0700
Received: from 40.80-202-210.nextgentel.com ([] helo=hardware.no)
	by gamma.hardware.no with asmtp (Exim 4.30)
	id 1BO1JV-0000oy-94
	for 165882-done@bugs.debian.org; Wed, 12 May 2004 23:30:53 +0200
Message-ID: <40A2978C.1010400@hardware.no>
Date: Wed, 12 May 2004 23:30:52 +0200
From: Tollef Fog Heen <tfheen@hardware.no>
User-Agent: Mozilla Thunderbird 0.5 (X11/20040306)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: 165882-done@bugs.debian.org
Subject: Not a dpkg bug
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Delivered-To: 165882-done@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-2.0 required=4.0 tests=BAYES_00 autolearn=no 
X-CrossAssassin-Score: 1

This is not a bug in dpkg; if your filesystem doesn't have UNIX 
semantics, you are on your own and will see spurious errors like this one.

I'm closing this bug.

- tfheen

Reply to: