Bug 136291 - [patch] editors/openoffice.org-3: gpatch failure
Summary: [patch] editors/openoffice.org-3: gpatch failure
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-openoffice (Nobody)
Depends on:
Reported: 2009-07-03 18:30 UTC by Pavel Plesov
Modified: 2011-02-13 07:35 UTC (History)
0 users

See Also:

file.diff (792 bytes, patch)
2009-07-03 18:30 UTC, Pavel Plesov
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Pavel Plesov 2009-07-03 18:30:08 UTC
gpatch fails to apply the patches to many parts of OO.org. He dies with the message:
/usr/local/bin/gpatch: **** File libmspack/mspack/mspack.h seems to be locked by somebody else under Perforce

I have checked some of files gpatch fails on. Them was not owned to root - e.g. uid=500 or 1500 (I have no such uids registered on my host anyway). All of them have have 0755 mode.

I am pretty sure these files are not locked under Perforce.

Fix: gpatch needs "-g0" command line flag or PATCH_GET=0 env var to be set.
       -g num  or  --get=num
          This  option  controls  patch's  actions when a file is under RCS or
          SCCS control, and does not exist or is  read-only  and  matches  the
          default  version, or when a file is under ClearCase or Perforce con-
          trol and does not exist.  If num is positive, patch gets (or  checks
          out)  the  file  from  the  revision  control system; if zero, patch
          ignores RCS, ClearCase, Perforce, and SCCS  and  does  not  get  the
          file;  and if negative, patch asks the user whether to get the file.
          The default value of this option  is  given  by  the  value  of  the
          PATCH_GET  environment  variable  if  it is set; if not, the default
          value is zero if patch is conforming to POSIX, negative otherwise.

Attached oo-gpatch.txt solved the problem. OO.org 3.1 seems to operate well.

Patch attached with submission follows:
How-To-Repeat: cd /usr/ports/editors/openoffice.org-3 && make
Comment 1 Edwin Groothuis freebsd_committer 2009-07-03 18:30:21 UTC
Responsible Changed
From-To: freebsd-ports-bugs->openoffice

Over to maintainer (via the GNATS Auto Assign Tool)
Comment 2 Martin Wilke freebsd_committer 2011-02-13 07:35:25 UTC
State Changed
From-To: open->closed

this report can be close because, these version no longer supported in 
FreeBSD ports.