Your message dated Thu, 31 Dec 2009 18:46:20 +0100
with message-id <[email protected]>
and subject line Re: Bug#200895: [PATCH] patch: strange "file seems to be 
locked" error
has caused the Debian Bug report #200895,
regarding patch: strange "file seems to be locked" error
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
200895: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=200895
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: patch
Version: 2.5.9-1
Severity: normal


Recently patch is acting strange.  For example, here I am trying to apply an
incremental kernel patch:

 j...@harehare:/tmp/linux-2.5.74$ bzcat ../patches/patch-2.5.75.bz2 | patch -p1
 patch: **** File CREDITS seems to be locked by somebody else under Perforce

Obviously my /tmp/linux-2.5.74/ tree is not under source control so I
don't expect such an error.  Yes I do have Perforce installed, but I haven't
had this problem before.

I can make the patch run by adding the option "-g0".

-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux harehare 2.5.74 #1 Wed Jul 2 23:07:51 EDT 2003 i686
Locale: LANG=C, LC_CTYPE=C

Versions of packages patch depends on:
ii  libc6                         2.3.1-16   GNU C Library: Shared libraries an

-- no debconf information



--- End Message ---
--- Begin Message ---
Version: 2.6-1

Re: Vincent Legoll 2009-04-11 
<[email protected]>
> I reported that bug upstream, and attached a
> patch that fix the default behaviour.
> 
> https://savannah.gnu.org/bugs/index.php?26148

I had completely missed that the savannah bug was already closed when
I updated the forwarding address of the Debian bug. Thanks to bts-link
for spotting :)

Christoph
-- 
[email protected] | http://www.df7cb.de/

Attachment: signature.asc
Description: Digital signature


--- End Message ---

Reply via email to