constructions that parse out to [ -z "$foo" ] && foo=""
These are bad examples that get copied and pasted into new code, so the
hope is that with less bad examples there will be less need for me to
bring this up in review.
In a few of these files all that were changed were comments so that next
time I search for these patterns I won't trip on the file for no reason.
In a few places, add $FreeBSD$
No functional changes, so no PORTREVISION bumps
be generated or checked, and will be silently ignored for now. Also,
generalize the MD5_FILE macro to DISTINFO_FILO.
PR: 149657
Submitted by: rene
Approved by: portmgr
Tested on: pointyhat i386 7-exp
#189734 **
The new tcp buffer calculation could cause a deadlock in
client/server communications. This problem was only detected
on configurations involving Solaris or Linux. Due to the
complications of platform specific tcp implementations the
algorithm has been reworked to make allowances for certain
eccentricities. (Bug #32494).
#188676 *
'p4 resolve' using the automatic option could crash the client
application when running on windows. This would only happen
if the 'theirs' file had been locked by another windows
application e.g. microsoft word. (Bug #32384)
Updated p4web. Bugs fixed:
#190006
Always offer browse depot selection in multiuser mode. (Bug #32704)
Complete release notes at:
http://www.perforce.com/perforce/doc.082/user/relnotes.txthttp://www.perforce.com/perforce/doc.082/user/p4webnotes.html
#188676 *
'p4 resolve' using the automatic option could crash the client
application when running on windows. This would only happen
if the 'theirs' file had been locked by another windows
application e.g. microsoft word. (Bug #32384)
#188603 **
A user with a complicated view map could crash the server
by creating a spec using '-i' or editing a spec to use
a name which contains '%%<somenumber>'. This has
been fixed. (Bug #31933)
Noted by: pointyhat via pav
#179182 **
'p4 sync -p' via the proxy did not transfer files which
were not in the proxy's cache. Fixed. (Bug #31775)
#184476 **
Excessive wildcard use in client views could crash the
ntx64/p4d server under circumstances that would be handled
correctly by the ntx86/p4d server. It was discovered
that the 64-bit version of the windows server requires more
stack space to perform commands involving excessive wildcard
usage in client mappings. This has been resolved so that the
ntx6/p4d process behaves similarly to the ntx86/p4d.
(Bug #31737)
#181214 **
'p4 fstat -F' with a filter that contains a not (^) crashes
the Perforce server. This has been fixed. (Bug #31771)
#183252 **
A failure to open a temporary file during submit of a compressed
file could lead to a server crash. This problem could occur on
a windows server only. Fixed. (Bug #31952)
#168144 *
Shell wildcard expansion on Windows can once again be disabled
by double quoting arguments. (Bug #30753)
- Drop alpha support
- Fix log dir location [1]
- Fix depot permissions [1]
- Separate DIST_SUBDIR [2]
Submitted by: Bernard Treves Brown [1], infofarmer [2]
#152382 **
Sometimes 'p4 integrate' would find a distant base when
cherry picking revisions to integrate. Now 'p4 integrate'
insists that the base be the revision before the first
revision being integrated when cherry picking revisions.
(Bug #29016).
#152296 **
'p4 submit' could report "No files to submit" if the
combination of client mapped files and protections table
exceeded an internal limit. This limit was incorrectly
reached on case-insensitive Servers (Windows) by repeated
values in a generated map. This has been fixed. (Bug #28853)
#149704 **
'p4 integrate' could skip integrations in the face of
large branch views coupled with large protection tables.
This has been corrected. (Bug #28659)
#149538 **
'p4 integrate' could report "no permission on file(s)" if
the protections managed by 'p4 protect' had excessive wildcards
(too many ...'s in too many entries). Now 'p4 integrate'
should be no more sensitive than other commands to the number
of wildcards in protections, and in any event should fail
with a more appropriate message ("too may wildcards").
(Bug #28422).
Changes: http://www.perforce.com/perforce/doc.073/user/relnotes.txt
Bugs fixed: (from release notes):
#136755 **
A perforce server could shutdown with the message
"License expired" even when a new license with a valid
expire date was put in place (either manually or with
the 'p4 license' command). This only happened if the
license that the server was originally started with
became out of date. (Bug #24800)
#136742 **
'p4 obliterate' under certain conditions could purge an
archive file which still had lazy copies pointing to it.
This change prevents that from happening. (Bug #26682).
#136586 **
In certain cases inconsistent results depending on depot
path could be observed for some commands. Typically when
this happened an unrestricted 'p4 sync' would bring back
correct behaviour. This problem only occured when a file
that had been previously synced was no longer mapped by the
current client view and the client path name had a '.' in
a significant position of its path. This has been fixed
(Bug #24943, #26541).
#135236 **
Unintegrated revisions prior to a delete could cause
undesirable file re-branching in subsequent integrations.
This change brings back an older behavior, which is to
not re-branch from revisions prior to a delete when the
target is also deleted. (Bug #25662)
For complete list of changes, see:
http://www.perforce.com/perforce/doc.062/user/relnotes.txt
Bugs fixed: (from release notes):
#129932 **
'p4 submit' could fail when 'p4 integrate' mistakenly
attempts to branch from a deleted revision if that
source file was readded and that readded revision was
ignored into the target file. Fixed. (Bug #24663)
#128837 **
The server no longer exits after 10 consecutive attempts
to accept an incoming connection. Usually the reason for
this is that the computer is under configured and its
simply a server resource problem. In some cases the
problem can be on the client end, because of this the
server now sleeps, then continues to retry. (Bug #24156).
For complete list of changes, see:
http://www.perforce.com/perforce/doc.061/user/relnotes.txt
Noticed by: pavmail
Bugs fixed: (from release notes)
#114840 **
CPU usage has been reduced for 'p4 integrate' when it is
handling indirect integrations through a large number of
branches (hundreds or more). (Bug #23592).
For complete list of changes, see:
http://www.perforce.com/perforce/doc.061/user/relnotes.txt
Noticed by: "Stefan Schablowski" <stefan.schablowski@prolificx.com>
Bugs fixed (from release notes):
#113339 **
'p4 opened -a //...' was being adversely affected by
the optimization in change #109212. It is now back to
its previous performance. (Bug #23307)
#113270 **
Files changed from type ktext to text would be stored
at the server with the keywords unexpanded even if the
files had been submitted with the keywords expanded.
This behavior, present only in release 2006.1, has been
fixed. (Bug #23258)
#112408 **
'p4 depot' will not abort when it encounters a UNC
path in the Map field so long as the path also ends in
'...'. UNC path handling in the depot form was broken
by change 93286, but it has now been fixed. (Bug #23191)
#94339 **
'p4 changes @changelist' could be slower in 2005.2 than it
was in 2005.1 due to an optimization intended to speed up
changelist ranges (@changelist,changelist). The optimization
has been tuned to be no slower than 2005.1. (Bug #20192).
For complete list of changes, see:
http://www.perforce.com/perforce/doc.061/user/relnotes.txt
PR: ports/107137
Submitted by: gabor
