Your message dated Tue, 15 Mar 2005 00:24:37 +0100
with message-id <[EMAIL PROTECTED]>
and subject line [Fwd: Re: Bug #181426 and #139214]
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; 20 Mar 2002 13:40:45 +0000
>From [EMAIL PROTECTED] Wed Mar 20 07:40:45 2002
Return-path: <[EMAIL PROTECTED]>
Received: from 10fwd.cistron-office.nl (smtp.cistron-office.nl) [195.64.65.197]
(mail)
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 16ngKa-0001eF-00; Wed, 20 Mar 2002 07:40:44 -0600
Received: from subspace.cistron-office.nl ([195.64.65.200])
by smtp.cistron-office.nl with esmtp (Exim 3.34 #4 (Debian))
id 16ngKY-0001JG-00
for <[EMAIL PROTECTED]>; Wed, 20 Mar 2002 14:40:42 +0100
Received: (from [EMAIL PROTECTED])
by subspace.cistron-office.nl (8.9.3/8.9.3/Debian 8.9.3-6) id OAA15435
for [EMAIL PROTECTED]; Wed, 20 Mar 2002 14:40:42 +0100
Date: Wed, 20 Mar 2002 14:40:42 +0100
From: MarcoH <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: vim backupcopy option breaks crontab -e
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
User-Agent: Mutt/1.2.5i
X-NCC-RegID: nl.cistron
Delivered-To: [EMAIL PROTECTED]
Package: vim
Version: 6.0.270-1
Vim has several ways to create a backup copy. It either renames the
original file to the backupname and then writes to a newly created file or
it creates a new backup file and copies of the original into the backup.
This behaviour can be controlled with the backupcopy option, when set to
'no', vim renames the file. If set to 'yes' it will copy the file.
The default setting is 'auto' which let vim decides what`s best, resulting =
in
renaming the original instead of copying it.
This breaks crontab -e, when $EDITOR points to vim, with crontab reporting
that there are no changes to the file. This is due to the fact that
crontab keeps the temp file open when handing it over to $EDITOR, and vim
renaming this file and creating a new one, which leaves crontab upon
returning looking at the (possibly already unlinked) backup copy instead
of the new contents.
As a workaround I suggest to add a 'set backupcopy=3Dyes' to the default
vimrc included in the package.
A more permanent fix should be to check if the file is open by another
process before renaming it to the backup.
Grtx,
MarcoH
--=20
Man proposes, God disposes.
-- Thomas `=08a Kempis
---------------------------------------
Received: (at 139214-done) by bugs.debian.org; 14 Mar 2005 23:25:14 +0000
>From [EMAIL PROTECTED] Mon Mar 14 15:25:14 2005
Return-path: <[EMAIL PROTECTED]>
Received: from intrepid.inittab.de (mail1.inittab.de) [62.91.23.197]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DAyvv-0001lS-00; Mon, 14 Mar 2005 15:25:12 -0800
Received: from rollcage.inittab.de (rollcage.inittab.de [192.168.1.2])
by mail1.inittab.de (Postfix) with SMTP id 8A45EC3967;
Tue, 15 Mar 2005 00:24:37 +0100 (CET)
Received: (nullmailer pid 3969 invoked by uid 1000);
Mon, 14 Mar 2005 23:24:37 -0000
Date: Tue, 15 Mar 2005 00:24:37 +0100
From: Norbert Tretkowski <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: [Fwd: Re: Bug #181426 and #139214]
Message-ID: <[EMAIL PROTECTED]>
Mail-Followup-To: [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED]
References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
In-Reply-To: <[EMAIL PROTECTED]>
User-Agent: Mutt/1.5.8i
Content-Transfer-Encoding: quoted-printable
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no
version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
* Pierre Habouzit wrote:
> Le Mar 15 Mars 2005 00:13, Norbert Tretkowski a =E9crit :
> > * Matthijs Mohlmann wrote:
> > >> The following bugs are still open for a long time and we are
> > >> checking if these bugs can be closed:
> > >> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D181426
> > >> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D139214
> > >>
> > >> Can you verify these bugs if those still exists in vim ? Current
> > >> version in Sarge is Vim 6.3-061+1
> > >
> > > Sorry, i don't have access to that machine any more.
> > >
> > > =3D=3D
> > >
> > > This is the mail i get back from this user and from the other user
> > > i got a bounce message saying:
> > >
> > > [EMAIL PROTECTED]
> > > Disk quota exceeded:
> > > mailbox is full: retry timeout exceeded
> > >
> > > The first person can't test it anymore and the second one seems
> > > also not responding (cistron.nl is AFAIK over to xs4all.nl)
> >
> > Hmm... so I'd suggest to close these bugreports if no one else is
> > able to reproduce them.
>=20
> Agreed.
[x] done
Norbert
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
