Release Notes for P4, the Perforce Command-Line Client, and P4D, the Perforce Server Release 2008.1 Introduction This document lists all user-visible changes to the Perforce server (P4D) and command line client (P4) between Release 97.3 and 2008.1. Release notes for P4Merge, P4SCC, P4V, P4Web, P4Win, and P4WinMerge, as well as supplemental Platform Notes and notes on Internationalization, are available separately on the Perforce Documentation web page. Perforce numbers releases YYYY.R/CCCCC, e.g. 2002.1/30547. YYYY is the year; R is the release of that year; CCCCC is the bugfix change level. Each bugfix in these release notes is marked by its change number. Any build includes (1) all bugfixes of all previous releases and (2) all bugfixes of the current release up to the bugfix change level. Both "p4" and "p4d" will report their version information by passing the "-V" flag. Additionally, "p4" can report the server's information with the "p4 info" command. -------------------------------------------------------------------------- Upgrading the Server DOWNGRADING A 2008.1 SERVER IS NOT POSSIBLE Significant schema upgrades are performed by the 'p4d -xu' command. The 'p4d -xu' command is generally required when upgrading a server with 1000 or more changelists. If a server has fewer than 1000 changelists, it is automatically upgraded when the new server is started. Before Upgrading To upgrade your Perforce server, your Perforce license file must be current. Expired licenses do not work with upgraded servers. In addition to your usual checkpointing scheme, always checkpoint your server immediately before undertaking an upgrade. To ensure that the checkpoint contains the latest information prior to the upgrade, stop the Perforce server and use the 'p4d -r -J -jc' command to make the checkpoint. Significant schema upgrades performed by the 'p4d -xu' command can consume a significant amount of disk space. You will need to ensure that you have in the filesystem where the db.* files are located free space equal to the size of the tables being upgraded, and twice that amount in the filesystem where the journal is located. The significant schema upgrades in each release are: 2008.1: db.change 2007.3: db.archmap (re)build db.archive replacement table 2007.3: db.view (re)build haveMap entries 2005.2: db.revsx (dedicated table for 'spec' depot entries) 2005.2: db.revdx (new table) 2005.1: db.locks, db.revhx (new table) 2003.2: db.user 2003.1: db.depot 2002.2: db.rev, db.working (tempobj entries only) 2002.1: db.changes 2001.1: db.integ, db.have The schema upgrades are cumulative through releases. For example, if you are upgrading a 2003.2 server to 2008.1, the db.locks, db.view, db.change and the new tables db.revhx, db.revdx, db.revsx and db.archmap will all be upgraded/created by the 'p4d -xu' command. If you are upgrading from 97.3 or earlier releases, please see the upgrade note at the end of this file. Upgrading Unix Platforms If your server has fewer than 1000 changelists or there are no significant schema upgrades required for your upgrade, simply replace your p4d binary with the new p4d and restart your server with your site's usual parameters. The server automatically upgrades its schema. If your server has 1000 or more changelists and there are significant schema upgrades required for your upgrade: 1. Replace your p4d binary with the 2008.1 p4d. 2. Issue the 'p4d -r -J -xu' command. This command performs the significant schema upgrades, then exits. 3. Restart your server with your site's usual parameters. Windows Platforms If your server has fewer than 1000 changelists or there are no significant schema upgrades required for your upgrade, simply run the new perforce.exe installer, which will restart your Perforce server service. The server automatically upgrades its schema. If your server has 1000 or more changelists and there are significant schema upgrades required for your upgrade: 1. Run the 2008.1 perforce.exe installer. The installer replaces the p4d.exe and p4s.exe executables, but will be unable to restart the Perforce server service since there are significant schema upgrades required. 2. Issue the 'p4d -r -J -xu' command from a command prompt window. This command performs the significant schema upgrades, then exits. 3. Restart your Perforce server service. After Upgrading 2002.1 jobs searching supports matching punctuation, but old jobs must be reindexed with the 'p4 jobs -R' command before punctuation in those jobs will be found. (See change 27808). Interoperating With Previous Releases 1. Unless stated otherwise you can intermix any release Perforce client with any release Perforce server, but any functionality new to 2008.1 requires you to upgrade the client and/or the server. See marks in the notes below. * -- requires new p4 client program ** -- requires new p4d server program *** -- requires new p4p proxy program 2. Beginning with 99.2, remote depots will interoperate between UNIX and NT. Beginning with 98.2, remote depots will interoperate across (98.2 and higher) releases. In 98.1 and before, remote depots will only operate with another server of the same release. 3. As of 2005.1, remote depot support for 98.2 and 99.1 servers has been dropped. Attempts by 98.2 and 99.1 servers to contact 2005.1 servers still works, but the depots will appear devoid of files. -------------------------------------------------------------------------- -------------------------------------------------------------------------- Release 2008.1. Major new functionality in 2008.1 Performance improvements - #135973, #149641, #148921 ** 1) Server Lock acquisition The algorithm to lock database tables has been changed to prevent wedging. Some commands, for example 'p4 client -d' need to writelock a large group of tables. Previous server versions acquired locks in a blocking fashion. This new algorithm will release previously acquired locks if another command is holding onto a lock which would cause it to block. After a third attempt to acquire the necessary locks in this fashion fails, the command will fallback to a blocking mode. 2) Connection protocol * *** TCP connections between Perforce processes; clients, proxies and servers, now discover network buffering levels and make better use of that buffer space. Performance should be improved especially for long proxy to server connections. 3) Proxy compression *** Uncompress of binary files can be done on the client instead of the server when the proxy is in use. Both the server and new proxy are required. (Bug #16398, #28490) Command improvements - #138839, #145664, #144624, #149074 ** 1) 'p4 fstat' 'p4 fstat' has been optimized to reduce memory allocation and improve performance. The result of this optimization is a 40% decrease in memory usage and a 30% speedup of the compute phase. 2) 'p4 changes' 'p4 changes -m max ' optimization has been improved for this release. Performance of this command is now less dependent on filepath depth or number of changes specified. The new algorithm makes use of a field in the db.changes table, which is calculated on submit or (for existing changes) by a 2008.1 upgrade. (Bug #9314, #28223, #26563). 3) 'p4 integrate' 'p4 integrate' has been sped up (again), markedly in cases where there is much integration history between the source and the target. (Bug #27706). 4) 'p4 obliterate' 'p4 obliterate' has been sped up, sometimes significantly, when obliterating many files in a repository with a large db.archmap table. (Tested with db.archmap with >100,000 entries.) (Bug #28452). New admin command - #137848 ** New command 'p4 admin lockstat' reports the read or write lock status for each database table. Minor new functionality in 2008.1 #152278 ** 'p4 protect' now allows specification of permission 'rights'. Previously, 'p4 protect' only allowed using permission levels which include the specified access (ie 'read') and also all of its lesser permissions (ie 'read' = 'read' + 'list'). Permission rights make it possible to deny individual rights without having to re-grant lesser rights. The new permission rights are '=read', '=branch', '=open', and '=write'. This functionality was previously undocumented, and is now fully supported for 2008.1. #151491 ** 'p4 group' fields MaxScanRows, MaxResults, MaxLockTime, and Timeout now use the value 'unlimited' to specify no limit for a parameter regardless of the limits imposed by a user's other groups. The value of 'unset' is used to specify no limit, but this will be trumped by any other limit for that parameter imposed by a user's other groups. Old group specs with this server will have the values of 'unlimited' replaced with 'unset', and members of all groups should have the same behavior as before. Similarly, Timeout of '0' will be replaced with 'unset', and also '0' Timeout will no longer be allowed for this field (use 'unset'). (Bug #2362, #18057, #19935). #150806 ** A new flag '-e nameFilter' for 'p4 labels/clients/branches' allows the user to limit the query using wildcards. This is very useful for sites that have a large collection of these domains. (Bug #6554). e.g. p4 labels -e "*sep*2000*" //depot/main/releases/... #146787 ** 'p4 triggers' can now make triggers on 'p4 triggers'. Previously, triggers were specifically excluded to avoid trouble. If a broken trigger is installed that prevents the 'p4 triggers' command from working, the only recourse is to rename or remove the db.triggers file from the server root directory. (Bug #26473). #146678 ** 'p4 jobspec' can now specify the default status for fixes created by 'p4 fix' and 'p4 change'. (It had been hardwired to "closed".) This default status is given in the jobspec's Presets value for the Status field, as an optional 2nd value preceded by the string "fix/", e.g. "Status open,fix/fixed" makes the default value for job status "open" but fix status "fixed". The fix status replaces the job status when the associated change is submitted. The new special fix status "same" leaves the existing job status in place. (Bug #9471). #146676 ** 'p4 fix' and 'p4 fixes' now report the job status associated with the fix in all cases. Previously the status was suppressed if it was the status "closed". #141168 ** 'p4 info' now reports the uptime of the Perforce Server. (Bug #1340) #140525 ** The performance of 'p4 revert' has been improved by batching its updates to benefit from the internal cache and a reduction in lock requests. (Bug #27198) #140369 ** Change-commit triggers now use a new script variable, oldchangelist, to report the pre-commit changelist number. (Bug #27287) #138643 ** Counters managed by 'p4 counter' can now be any string, not just a number. (Bug #6096) #137438 ** After a submit has completed, ktext files need to have their digest and size recalculated. Previously updates of the db.rev and db.revhx tables happened individually for each file, these updates are now batched. This change results in fewer lock requests, potentially improving the total elapsed time for submit. #139128 ** 'p4 fstat' has two new flags. The '-S' flag is used to request a different sort order for output. The '-r' flag will reverse the output order. See 'p4 help fstat' for details. (Bug #26301) #134117 ** New server identification startup flags: p4d -In Specify a unique identifiable name for your server. This name is visible with 'p4 -ztag info' output. p4d -Id Specify an identifiable comment for your server. This description is visible with 'p4 -ztag info' output. Bugs fixed since 2008.1 GA #215254 ** Using the Perforce broker against a Perforce server on Solaris could sometimes deadlock. This change adds a configurable environment variable 'P4HIMARKMAX' which can be set on server startup to prevent this from happening. (Bug #35293) #185931 ** 'p4 opened -C' with a non existent client spec causes the server instance to terminate abnormally. This problem occurs only with optimized builds on a limited number of platforms and appears to be an optimizer problem with the compiler. Fixed. (Bug #32247) #180767 ** 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) #179182 ** 'p4 sync -p' via the proxy did not transfer files which were not in the proxy's cache. Fixed. (Bug #31775) #175236 ** When using the proxy, 'p4 print' of binary files without the '-o' flag would be output as compressed and possibly output twice in a row. Fixed. (Bug #31596) #174121 ** 'p4 monitor' with the options '-a' or '-ae' could crash the Perforce server (on windows only). This has been fixed. (Bug #31547) #171545 ** 'p4 integrate' has been modified so that changes which have been copied out of and back into the same branch will now be candidates for re-integration into other branches. This should make synchronizing branches after forced integrations easier, at the cost of scheduling extra integrations in some cases. (Bug #29148). #168144 * Shell wildcard expansion on Windows can once again be disabled by double quoting arguments. (Bug #30753) #164374 ** 'p4 submit -t' would still submit a changelist even though one of the files had been tampered with and reported to the user. This has been fixed (Bug #30569). #164029 ** Using 'p4 -x' with many thousands of files would take longer due to an optimization that was made for the more general use of Perforce. This optimization became a penalty for single file operations. Fixed (Bug #30616). #161164 ** 'p4 admin lockstat' had a protocol error which caused p4v (and possibly other client applications) to generate incorrect results if used jointly with another command using tagged output. This has been fixed. (Bug #30289). Bugs fixed since 2008.1/156517 (beta) #160022 ** The new tcp buffer calculation could be too aggressive on some platforms (causing a deadlock in client/server communications). The algorithm has been tweaked to prevent this from happening. (Bug #29974). #158746 ** Change #153657 introduced a regression that could cause 'p4 integ' to scan the db.integed table excessively. This has been corrected (Bug #29943). #156864 ** 'p4 integrate' of temporary files followed by 'p4 resolve -at' done multiple times with the same target file before a submit would not submit the final resolve but instead the first resolved file. Fixed. (Bug #29811) #156771 ** Commas are no longer allowed as part of branch, client, depot, or label names. Existing entities containing commas in their names can still be accessed, but no new clients, branches, depots or labels can be created with commas in their names. (Bug #12510) Bugs fixed in 2008.1 #154569 ** 'p4 user -f' or 'p4 user -f -i' would allow creation of new users with all-numeric user names. This has been fixed to work as intended, which is to disallow all-numeric user names. (Bug #29250) #153657 ** 'p4 integrate' has been adjusted to detect when a revision has been integrated out and then back into the same file, and to suppress integrating the later revision into another file if the original revision has already been. (Bug #20413, #29176). #152854 ** The proxy was storing revisions which were lazy copied between different local depots in multiple locations. Fixed. (Bug #28635) #149573 ** 'p4 change -u' no longer requires both the username and workspace of the user to match those of the owner of the submitted change. Now only the username needs to match. (Bug #25380, #28412) #149297 * 'p4 set' will now report on the P4POPTIONS variable. (Bug #22108) #149109 ** Editing a client spec form with 'p4 client' can reset 'LineEnd' or 'SubmitOptions' to their default values. This problem only occurred if the 'Options' field was processed after either of the other two (usually through the api). (Bug #28605). #147069 ** 'p4 obliterate' now purges archive files in numerical order rather than alphanumeric. Removing RCS revisions in the correct ascending order is much faster. (Bug #25357). #146485 ** p4d will now report a non-zero exit status and a summary error message of journal files skipped due to recovering those files out of sequence. (Bug #13892) #146472 * 'p4 set' on the Windows platform did not always find the right P4CONFIG file when the P4CHARSET is set to shiftjis. Fixed. (Bug #26042) #144699 ** 'p4 sync' to a deleted revision using tagged protocol no longer reports a bogus file size in its summary data. (Bug #27493). #142417 ** 'p4 integrate' and 'p4 diff2' could produce misleading error messages when trying to explain why there was no output. The most common message was 'No target files in both client and branch view.' Now this message has been augmented with a number of more specific error messages, and the correct argument (source file or target file) is displayed with the error message. (Bug #452, #2061, #6339, #10563, #20914). #142061 ** A user with only an unmapping access line in 'p4 protect' (e.g. 'list user * * -//...') could still cause a license to be consumed. Now such a user gets the same response ("Access for user 'xxx' has not been enabled by 'p4 protect'.") as with no access at all. #141985 ** 'p4 help' for diff, diff2, describe, annotate, and resolve have been updated to clarify the usage and behavior of -d and -s diff options. The server's usage messages have also been updated. (Bug #26279, #23447, #22998, #18164, #16797, #13491, #26793). #141042 ** Users may now revert their own files so long as they have at least "list" permission on the files to be reverted. Previously 'p4 revert' required at least "open" permission to revert files. (Bug #3539, #5899) -------------------------------------------------------------------------- -------------------------------------------------------------------------- Release 2007.3. Major new functionality in 2007.3 Ability to specify group owners - #1591, #9600 ** 'p4 group' has a new 'Owner' field which is used to specify users allowed to modify the group spec without SUPER permission. Owners may change or even delete a group via the new 'p4 group -a' command. Owners are members of their owned group, but with enhanced privilege to also administer the group. Performance improvements - #122007, #124181, #124726, #128272 ** 'p4 integrate' locking changes. To improve concurrency during very long complicated integrate compute cycles, database queries have been modified. The new algorithm allows for early release of locks on the db.working, db.have, db.locks and db.resolve tables. Besides a significant reduction in the time that "update" commands have to wait, the overall elapsed time for a branch has been reduced by as much as 25%. 'p4 submit' locking changes. A rewrite of the commit phase for 'p4 submit' in a previous version improved concurrency for a number of commands. This has now been extended to commands that make use of the db.counters table. For example 'p4 change' can run concurrently during the first (and longest) commit phase of a large branch submit. 'p4 sync' locking changes. Sync has been modified so that during its compute phase it is less likely to block commands that need access to the db.resolve table. This allows commands like 'p4 revert' to operate during this time. Also initial syncs or 'p4 sync -p' operations will no longer read lock the db.have table, thus allowing concurrent syncs update access to this table. 'p4 labels' locking changes. When used with a file argument 'p4 labels' attempts to cache all of the file db.rev data so that the lock on that table can be released early. Sites that have a very large number of labels and run 'p4 labels ' will no longer wedge the server, only 'p4 labelsync' commands will have to wait. Cache management change. Caching of disk pages has changed. Pages are written earlier to avoid writing too many pages together when table locks are released. This also reduces memory and cpu usage by the metadata cache system. TCP buffering change. Perforce clients, servers, and proxies will attempt to increase TCP send and receive buffers to 32Kbytes if those buffers are less than that amount. This can improve network performance on high latency networks. Minor new functionality in 2007.3 #132766 ** 'p4 sync' and 'p4 integ' with large data sets and large protections tables now consume less CPU than before. (Bug #6964). #132360 ** Protections have been tidied up in a few odd cases: 'p4 dirs -H', 'p4 have', 'p4 labelsync', and 'p4 opened' now require having 'list' access. #130733 ** 'p4 groups -v [group]' provides summary data for the named group, much like 'p4 users [user]'. (Bug #25273) #130372 ** Trigger standard output is now passed to the client on success as well as failure. As previously, on trigger failure an error is sent to the client with the standard output embedded. Now, on trigger success a message is sent to the client with the standard output, unadorned. Previously the output was discarded on trigger success. Users can force the old behavior by setting the "api" protocol level to 61 or less with 'p4 -Zapi=61 '. (Bug #7546). #129728 ** 'p4d -jc' and 'p4d -jj' now only hold read locks on the database files, allowing read operations in the server to continue. The db.counters file is still locked, as it is updated. #129045 ** *** Proxy will now cache files as they are submitted through the proxy. A new cache validation system based on MD5 signatures is being used. If a new proxy is working with an old server, the old timestamp validation is used. Recommend running "p4 verify" to assure that the p4d server has MD5 signatures computed as the proxy will not validate its cache for revisions which the p4d server does not have an MD5 signature. (Bug #10866) #127926 ** 'p4 filelog' now sports a '-h' option. This option allows the user to follow 'branch from' and 'copy from' integration history. For more details see 'p4 help filelog'. (Bug #24825) #125001 ** Journal rotation with 'p4d -jc' or 'p4d -jj' is now an instantaneous rename (rather than a copy) on UNIX. The the -z flag (compress checkpoint/journal) still copies. (Bug #21537, #24909) #124026 ** 'p4 protect' entries may now use CIDR syntax for IP address specification. For example "172.16.0.0/16" would match all IPv4 addresses which start with 172.16. You cannot combine wildcards with CIDR notation except at the start to allow proxy or no proxy matching. (Bug #3372) #129897 ** 'p4 change' now allows the user to modify the client of a pending changelist, provided there are no open files. (Bug #25366) Bugs fixed since 2007.3/140672 (first release) #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) #149541 ** '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). #145613 ** Change #130372 caused a server with a form-out spec trigger that generates standard output upon success to crash when a user issued 'p4 spec' or 'p4 jobspec'. Form-out trigger standard output upon success also caused command-line options to be ignored during execution of 'p4 change', 'p4 group', or 'p4 submit' commands that fire the trigger. This has been fixed. (Bug #27892) #143891 ** 'p4 change' would take out unnecessary write locks on certain tables. This has been fixed. (Bug #27919). #143551 ** Change #142077 could cause a truncation error bug, if the journal file supplied with the -J option was in a different file system. This has been fixed (Bug #27922). #142077 ** Some Unix platforms (Solaris, HPUX, AIX) would fail trying to rotate the journal file. This has been fixed (Bug #27607). #141953 * Change #127617 caused P4EDITOR, P4DIFF, and P4MERGE settings with spaces to no longer be broken apart into distinct arguments on non-Windows platforms. This has been fixed. Windows clients continue to treat all parts of the command before the first +, -, or / as an executable path. (Bug #27585) #141402 ** 'p4 client/label/branch -d' would request write locks of database tables that were not required for its operation. This has been fixed (Bug #27504). Bugs fixed in 2007.3 #139650 ** Rpc inbound and outbound sizes in bytes were sometimes incorrectly reported as negative when server tracking had been enabled. This has been fixed. (Bug #26763) #139099 ** Rpc inbound size in bytes was incorrectly reported to be zero when server tracking had been enabled. This has been fixed. (Bug #25684, #24578) #138968 ** Change #119708 introduced a regression causing 'p4 revert -k' to fail to report results of a successful revert when using tagged protocol. This has been fixed. (Bug #27061) #137032 ** Upgrading to 2007.3 will rebuild db.archmap and db.view (haveMap entries). This upgrade will fix bad data which was introduced by bug #24943 and previously patched on-the-fly by change #136742. #136601 ** Failure to connect to a remote depot resulted in a garbled error message. This has been fixed. (Bug #26468) #133838 ** 'p4 help protects' clarifies the behavior of the '-m' flag by noting that it does not report exclusionary mappings. (Bug #25794) #133764 * 'p4 set -S ' will now print $P4AUDIT if it is set. (Bug #26005). #133327 ** 'p4 submit' would let you update the changelist form with files not currently open for add/edit. Although these files would be ignored, the error would not be reported. This has been fixed. (Bug #25771). #133189 ** The change #117342 introduced a regression that would prevent the use of 'p4 login' against a server that failed to find a reverse DNS entry. This has been fixed. (Bug #26009). #132920 ** Very small journal files concatenated together might fail to replay with 'p4d -jr'. This has been corrected. (Bug #25968) #130369 ** Issuing a 'p4 unlock' of a file which someone else was submitting might not always be detected. This has been fixed. (Bug #25408) #130219 ** 'db.monitor' entries are not journalled but are incorrectly checkpointed. This has been fixed (Bug #12532). #130201 ** Fixed memory leak on 'p4 sizes' in summary mode. (Bug #25326) #129956 ** Fixed tiny memory leak when a query string is missing the right-hand side of a relational operation. (Bug #25373) #129950 ** Corrected processing of search queries which contain mixed case and wildcards. Searching is case insensitive. (Bug #25347, #25371) #129925 ** Update the spec depot and index remaining content of jobs when a field contains a word which is extremely long. Note that these words will not be indexed. (Bug #25349) #129820 ** 'p4 change -d' would make an unnecessary scan of the 'db.working' table. This could take a long time on large sites with many open files. Fixed. (Bug #25340) #129045 ** 'p4 sync -p' run through the proxy would update the have list when the proxy needs to bring over a revision from the server. Fixed. (Bug #25274) #129045 ** *** The proxy can effectively cache files with a zero modtime. (Bug #23408) #129045 *** 'p4 -Zproxyverbose print' will now report if the proxy cache was used to satisfy the command. (Bug #22802) #128995 ** 'p4 protect' now describes the 'admin' mode in the comments section. (Bug #11155) #128595 ** Corrected underlying issue which caused the server to fail with 'integbatch: too many handles!' or 'syncbatch: too many handles!' errors. (Bug #25245, #18873, #21511) #128356 ** A perforce server will shutdown with the message "License expired" even when a new license with a valid expire date is 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) #128087 ** Failed authentication attempts are now recorded in the server error log. (Bug #17988) #127651 ** 'p4 submit' of files imported from a remote depot could fail with the following error: Operation: dm-SubmitChange Operation 'dm-SubmitChange' failed. is missing from the rev table. This has been fixed (Bug #10125). #127617 * Spaces in P4EDITOR, P4DIFF, and P4MERGE are now handled differently on Windows and UNIX. On UNIX, as before, separate words are treated as the command name and initial arguments. On Windows, separate words are treated as the command name (with embedded spaces), until a word begins with +, -, or /, which is assumed to introduce initial arguments. (Bug #690, #5297, #24174) #127480 ** 'p4 diff2 -u' incorrectly included binary files, which could result in unreadable binary diffs. This has been changed. Now binary files are only force diffed when the '-t' option is used. (Bug #20986) #127031 ** Server audit output '-A auditlog' could also end up in the errorlog file '-L logfile'. This was most likely to happen when tracking '-vtrack=1' was enabled. (Bug #23377). #124983 ** 'p4 monitor show' will no longer show stale processes. Those processes that never exited correctly will have their status records automatically removed from the db.monitor table. (Bug #12956, #21593) #124936 ** %clienthost% in triggers will be replaced with the IP address of the client if no reverse DNS entry is found. (Bug #19911, #21506) #124875 * 'p4 sync' (and other commands) could loop if the underlying filesystem had certain permission combinations, such as the ability to create but not chmod a file (usually on network filesystems such as samba or NFS). This has been corrected. (Bug #16726, #18049). #124344 ** Submitting a new revision to an RCS ,v file could result in losing previous revisions if the file access mode had been manually modified to remove the read permissions. This is now prevented. (Bug #24961). #123740 ** 'p4 edit' of a file synced back to a point where it had a different filetype than the head revision's filetype would treat the file as if it were the head revision type instead of the sync'ed to revision. This typically caused problems with symlinks either by not changing file modes or changing the file mode of the target of the symlink. (Bug #24900) #121849 * Negative numbers, or numbers which overflow into negative numbers, are no longer allowed as changelist arguments to p4 commands. For instance 'p4 review -c 111111111111' against a windows server would cause the changelist argument to overflow into a negative value, resulting in the server consuming excessive cpu and hanging the machine. Now this no longer happens. (Bug #24538). #121382 * Pending revision entries in db.revpx, created when content triggers are used, now correctly report the file's size (instead of reporting size as -1). (Bug #24558). #131532 ** Client commands originating through proxy servers are now logged in the server and audit log files with the proxy host/client host format. The format for the 'p4 monitor show -e' now reports the client host, rather than the proxy host for these same commands. -------------------------------------------------------------------------- -------------------------------------------------------------------------- Release 2007.2. Major new functionality in 2007.2 New file type 'utf16' - #119109 * ** *** A new filetype utf16 has been added which is a textual file type which stores UTF16 client files. These files must be valid UTF16 translatable into UTF8. When the content of these files is used in command output such as 'p4 diff' that content will be in UTF8. Only full file representations will be in UTF16. This filetype works with the server in non-unicode mode as well as unicode mode. If these files are sync'ed with pre-2007.2 clients, they will be transfered as UTF8. If the server is in unicode mode, command output with contents from UTF16 files will be converted according to the P4CHARSET selected. BOMs are needed to automatically detect utf16 with the 'p4 add' command. Without a BOM, a file is assumed to be in client byte order. When a file is written such as via 'p4 sync', it will be written with a BOM and in client byte order. File type modifier '+S' enhanced - #115478 ** The filetype modifier '+S' has now been extended to include an optional numeric value that informs the server of the number of file revisions to keep. e.g. p4 add -t binary+S7 foo.exe In the above example as the eighth revision is submitted, the first revision will be purged. The numeric values supported are 1 through 10, 16, 32, 64, 128, 256, 512. Note that files with this filetype are never lazy copied. This means that although space is saved when purging old revisions, multiple branching of a file will result in more space used. See 'p4 help filetypes' for more information. (Bug #1880) New 'p4 sync' option bypasses db.have updates - #111247 ** 'p4 sync' now sports a '-p' option. This allows the user to sync files without the server keeping track of it. This option is very useful when populating build clients or when publishing content when there is no requirement for saving the client workspace state. (Bug #22857). Performance improvements - #114771, #113299, #117618, #115072 ** 1) Submit of branched files Continuing on from the branch/submit improvements made in the previous release. The commit phase of 'p4 submit' has been rewritten to improve performance during large branch creation. Most commands are now blocked for only a fraction of the time when compared to previous releases. The overall time taken to create the branch has also been reduced as much as 30%. 2) Connection protocol * The Perforce connection establishment protocol and buffering have been adjusted to avoid the nominal 1/10th second delay that TCP can introduce on some operating systems. In some cases, this can drastically reduce the time needed for a series of short commands. 3) @label,@label speedup Specifying revisions using @label,@label could be really slow when there is little overlap between the filespec and the number of matching files in the label. (Bug #23907). 4) Lockmode changes on last access updates The server no longer takes write locks on db.user or db.domain to update access time unless the access time is actually updated. (Bug #6837) New admin commands - #108286, #118447 ** 'p4 admin dbstat' Dbstat scans the internal nodes pages of database file(s) then outputs some simple statistics. The operation will lock out write access to the database table during its scan, so therefore it should be used with care. 'p4 admin updatespecdepot' Updatespecdepot instructs the server to archive forms into the spec depot. This command can be very useful for installations that have just enabled the spec depot and want to pre-populate it with existing form data. (Bug #19309). See 'p4 help admin' for more information about these new commands. New triggers - #116132 ** 'fix-add' trigger will be executed prior to adding a fix with the 'p4 fix' command. 'fix-delete' trigger will be executed prior to deleting a fix with the 'p4 fix -d' command. 'form-commit' trigger is executed after a form has been committed to gain access to automatically generated fields. (This trigger which was introduced in 2006.2 but undocumented is now fully supported). See 'p4 help triggers' for more information. Minor new functionality in 2007.2 #119528 ** 'p4 protect' will not allow the user to delete its last 'super' entry. (Bug #14419) #119344 ** Content triggers can now access the timestamps on the files being submitted via the 'headModTime' field in the output of 'p4 fstat @='. Previously timestamp information was not available until after the files had been submitted. (Bug #23591) #118826 ** 'p4 change' has a new '-u' option to allow the owner of a submitted change to update its description and/or jobs fields. (Bug #1159). #116469 * ** Changes to integrate and resolve. 'p4 integrate' now performs compatibility checking and will disallow integration between incompatible types, unless the '-t' flag is used. (see chart below for type compatibility). When files have been integrated with '-t', 'p4 resolve' behaves as follows: 'accept theirs' changes the type of the file on the client. 'accept yours' reverts the type change so that the open file type will match the 'yours' file type. Note, this new behaviour is also true if the user issues a 'p4 reopen' and changes the file open type. T - Resolved as text B - Resolved as binary x - Incompatible types (requires 'integrate -t') Compatibility: text binary symlink resource unicode apptxt apple text T B x x T x x binary B B x x B x x symlink x x T x x x x resource x x x B x x x unicode T B x x T x x apptxt x x x x x T x apple x x x x x x B (Bug #202, #218, #7522, #8649, #13352, #15653, #16636, #16845, #16888, #20370, #22382, #23343) #119955 ** The 'p4 integrate' algorithms for suppressing reintegration and for picking the optimum base, which were reimplemented in 2006.1, have been tuned significantly for this release. The following new changes have been made: Integrating a single 'copy from' revision now gives credit for all earlier revisions, so that a subsequent 'p4 integrate' of any earlier revision will find no work to do. This can only come about by 'cherry picking' (providing to 'p4 integrate' specific revisions to integrate). (Bug #23698) Pending integration records (files opened with 'p4 integrate' but not yet submitted with 'p4 submit') are now considered when finding the most appropriate base. This makes integrating into a related file already opened for branch possible without the 'p4 integrate -i' flag. (Bug #24251). 'p4 integrate' follows indirect integrations through complicated combinations of merge/copy/ignore integration records better. This should result in fewer integrations being scheduled, and closer bases being picked, for integration between distant files. (Bug #24207). 'p4 integrate' could wrongly choose a base on the source file after the revisions needing to be integrated if the revisions needing to be integrated were before revisions already integrated. This normally only comes about in cases of 'cherry picking' (providing to 'p4 integrate' specific revisions to integrate). (Bug #23469) 'p4 integrate' in certain cases wouldn't find a base (or choose a poorer base) if the source file was branched and reopened for add, and then the original file was changed further and branched again. (Bug #24150) #115979 ** 'p4 monitor terminate [id]' can now be used successfully on commands that have moved beyond the compute phase of their processing. Note, that it may take up to 10 seconds before the process will actually terminate. (Bug #11938) Bugs fixed since 2007.2/122958 (first release) #140379 ** When integrating between two branches separated by an intermediate branch, 'p4 integrate' would conclude there was nothing to integrate if the target file had merged from a revision of the intermediate file that itself was a copy of a revision in the source file. This merge/copy chain is now treated as a merge, not a full copy. (Bug #27216). #139758 ** The p4d server on SOLARIS could intermitedly terminate a command due to incorrect detection of a client dropped connection. This has been fixed. (Bug #27240). #136754 ** 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). #136614 ** 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). #135827 ** The change (#120526) also introduced a regression that could cause 'p4 changes' to not work correctly with the '-u' or '-c' option when specifying '-m1 '. This has been fixed. (Bug #26464). #135235 ** 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) #132978 ** In the rare case where the Perforce Server on Windows fails to create a thread, the reason is now logged in the server errorlog. Under these conditions the server will no longer try to run the command in the main parent thread, but will wait for resources to become available before executing any more commands. (Bug #25981). #132390 ** 'p4 changes -i', 'p4 fixes -i' and 'p4 jobs -i' under certain conditions could exclude changelists that were integrated into the specified files. This problem has been fixed. (Bug #25828). #131348 ** The Perforce Server on Windows could hang for some commands when the auditlog was enabled. This has been fixed. (Bug #25612). #131114 ** The change (#117342) also introduced a regression that would prevent the use of 'p4 login' (perforce tickets) against a central authentication server. This has been fixed. (Bug #25312). #128851 ** 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). #124999 ** When the 'p4 integrate' command syncs files it will now sync file deletes before adds so as to remove directories in case they are replaced with normal files. (Bug #17409) #124947 ** 'p4 submit' would wrongly prevent a check submission when a binary file is resolved due to simple version updating (i.e. p4 sync to head requiring p4 resolve) rather than due to 'p4 integrate'. The submit report report, "edit or revert" but the file is already open for edit. (Bug #25038) #123381 ** Adding a job with three strings of about 2700 characters in the description could possibly corrupt the jobs index btree. Fixed. (Bug #24793) #123248 ** 'p4 submit -d' would set the status field to "ignore" in all jobs matching the user's JobView. Now jobs matching a user's JobView are not modified when using "p4 submit -d". (Bug #24711). Bugs fixed in 2007.2 #122782 ** '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) #122672 * .DS_Store files are now deleted when removing a directory. (seen mainly on the Macintosh) (Bug #24270). #122284 ** 'p4 submit' would not always honor the submit options if the change form had to be edited a second time. This has been fixed. (Bug #24671). #120969 ** It is now possible to configure the filetype for spec depot files by using 'p4 typemap'. e.g. TypeMap: text //spec/client/... Note, the default for spec files is ctext. By changing the creation filetype to text (like in the example above) the server will not require subdirectories which can be a problem with sites that have more clients than their filesystem can create directories for. When setting a filetype for spec depot files only the server storage type has any relevance, setting storage modifiers will have no affect. (Bug #24454, #24205). #120526 ** 'p4 changes -m1 ' optimization of using the db.revcx table does not always perform well. Now if the scan of the db.revcx table does not find any matching files after trying a pre-set number of rows it will give up and fall back to using db.rev directly. (Bug #17862). #120385 ** 'p4 integ' could change the HaveRev to 'none' of a synced file when used with a branch spec and fileset that creates an out-of-order integration list. This has been fixed. (Bug #24149) #119979 ** Under certain rare circumstances the error: 'Database open error on db.!' 'BTree is corrupt!' Could be incorrectly displayed. This could only happen on windows servers due to an initialization problem. This has been fixed. (Bug #24335) #119708 ** 'p4 revert -k ' was checking the client side file when it does not need to. Fixed. (Bug #21679) #119687 ** Running p4 diff2 with tagged output would leak a small amount of memory on each pair of files diffed. Fixed. (Bug #24079) #119631 ** Tagged output of p4 diff2 -q was including identical files. Changed so that with the -q flag identical files are not included in the tagged output. (Bug #23077) #119616 * 'p4 -d ' run in unicode mode would ignore the command line directory override. Fixed. (Bug #23950) #119597 * Exif format jpeg files were added as binary rather than cbinary (already compressed). Fixed. (Bug #23999) #119596 * p4 diff -sd would wrongly report a symlink as missing if that symlink's target was missing. Fixed. (Bug #24023) #119245 ** Triggers run on Unix platforms were inheriting some open file descriptors from the server. This should no longer occur. (Bug #24204) #119012 ** The error message and documentation have been improved for 'p4 change -f' to reflect which fields are read-only. (Bug #19922, #13231, #18962) #118635 ** 'p4 submit' could submit a branched file with a bad archive entry if the source revision of the branched file is purged before the submit is completed. This has been fixed (Bug #22297). #118282 * Hostname lookups that succeed without returning an address will no longer cause the client to crash. (Bug #24104) #118102 ** Error-handling for the spec commands has been improved to not allow the mutually exclusive '-i', '-o', and/or '-d' flags to be used together in one spec command. Previously wrong errors may have been generated, and in some cases the command may have executed using any one of the flags. (Bug #24116, #24081, #24447) #118064 ** 'p4 obliterate' no longer reports delete revisions in the list of revisions being being "purged". The "purged" message is now reserved for the act of removing file contents from the archive. #118057 * ** 'p4 submit' with the 'revertunchanged' submit mode would fail to reset the client file permissions. This has been fixed (Bug #23536). #117730 ** p4 job -d will only delete jobs that have no associated pending or submitted fix records. (Bug #16296). #117342 * ** Different values of P4PORT for the same server instance e.g. (ip:port# vs host:port#) would result in multiple ticket entries in the Perforce ticket file. This has been fixed so that the same server instance will always produce a single ticket entry that either P4PORT value can use. (Bug #16707, #18349). #117090 ** 'p4 integrate' between two deleted files would give a bogus error message about permissions. Now it more properly says "all revision(s) already integrated." (Bug #23953) #116771 ** 'p4 obliterate file@change' of a file opened for add would remove the open record, while 'p4 obliterate file@change,change' would not. Now neither does: to remove an open-for-add record o you must use 'p4 obliterate file' without a revision. (Bug #23915). #116451 ** Superusers can now delete protected counters using 'p4 counter -f -d'. Previously they could be set, but not deleted. #116428 ** Syncing between revisions where the revision on the client was binary+w (or other non-text types) and the new revision was binary would incorrectly fail with a "Can not clobber" message. Also, if a client had a writable file not controlled by Perforce and that file is then added by another client as a +w type Perforce would overwrite the file when syncing. (Bug #15562, #23777) #116173 ** Failed trigger of type 'change-content' would leave edited files on the client workspace in a read-only state. This has been fixed. (Bug #14880). #116113 * ** Providing the security level permits it, expired perforce tickets no longer override valid P4PASSWD settings. (Bug #15520) #115153 ** *** It is no longer possible to start more than one Perforce Server or Perforce Proxy Server on the same TCP port on a Windows platform. Now such attempts will correctly report that the address is in use. (Bug #23630) -------------------------------------------------------------------------- -------------------------------------------------------------------------- Release 2006.2. Major new functionality in 2006.2 Client file tamper checking - #101065, #101345, 101699 * ** 'p4 submit' will now check that files integrated and resolved with 'am', 'at' or 'ay' are not modifed after 'resolve' and before 'submit'. If such tampering is detected then an error will display the modified file and request that the file be re-edited or reverted in order to complete the submit. e.g. //client/main/foo tampered with after resolve - edit or revert. Since tamper checking also applies to branch creation, the overhead for processing large datasets can be avoided by using the integrate '-v' option which does not copy the file to the client. To check for tampered files before submitting, 'p4 diff -sb' will now report files which are open for integration and have been resolved but have been modified. These files can be reopened for edit with the command 'p4 diff -sb | p4 -x - edit'. Note that in order for tamper checking to work with files resolved with 'am', a 2006.2 client as well as the server is required. (Bug #17607, #15928, #15654, #20029, #20587) New client option 'SubmitOptions' - #106812 ** The new 'p4 client' field 'SubmitOptions' allows the user to alter the behavior of submit. The six different values for this field affects what happens to unchanged files and if submitted files are reopened. For more details see 'p4 help client'. SubmitOptions unchanged submitted value files files ---------------------------------------------------- submitunchanged submitted submitunchanged+reopen submitted reopened revertunchanged reverted revertunchanged+reopen reverted reopened leaveunchanged left open leaveunchanged+reopen left open reopened In addition 'p4 submit' now sports a '-f option' flag. This allows the user to override the SubmitOption which is set in the client. e.g. p4 submit -f leaveunchanged Speedup of 'p4 submit' branched files - #101435, 107393 ** The time taken to update the metadata (locking db.* files) has been reduced by as much as 40% by a combination of the following changes. The biggest reduction is seen when submitting a large number of branched files. 1) db.archmap table replaces db.archive An earlier version of the server improved obliterate performance by introducing the db.archive table. A side effect of introducing this table was a performance penalty when submitting files that resulted in lazy copies. This table has now been replaced with the db.archmap (archive map) table that does not suffer the same performance problem. 2) buffered journal file Performance has generally been improved by optimizing the way that journal records are written. This change reduces the number of writes and the number of locks taken against the journal file. 'Automatic' labels - #107125 ** The new automatic label feature introduced in 2005.2 but undocumented is now fully supported. By adding a "Revision" field to the label specification you can now make that label appear as if 'p4 labelsync' had been done on the label using that revision. The only difference is that if the "Revision" specification is dynamic (e.g #head) the apparent contents of the automatic label will change, while a static label set with 'p4 labelsync' will not. Note that when executing the command 'p4 labels ' automatic labels will not be displayed. (Bug #20887) Improved management of remote depots - #106497, #100829, #108461 ** Several changes have been made that improve the management and interoperability of remote depot servers. 1) Better lock support The server no longer locks the db.rev (or db.revhx and db.revcx) tables when accessing only files in a remote depot. This means that using 'p4 dirs' on a remote depot (often by expanding a remote folder in p4v) will no longer hold local locks. (Bug #19730). 2) MaxScanRows/MaxResults support Remote depot operations are now subject to MaxScanRows and MaxResults limitation imposed by 'p4 group' on the remote user 'remote'. (Bug #18694). 3) Protocol to negotiate table version. By negotiating the highest level for table compatability several problems have been solved. Previously, files with some complex type modifiers (like text+Fk) could not sync from remote depots. The negotiation allows for new fields like the file size to be included in data transfer from the remote server ('p4 sizes' will work with remote depots). (Bug #14896, #22146). New MaxLockTime in 'p4 group' - #106371 ** 'p4 group' now has a 'MaxLockTime' field, which can be used to prevent queries from holding locks on database tables for too long. See 'p4 help maxLockTime'. (Bug #21206). Improved license file handling - #103739 ** The new 'p4 license' administrator command allows a user with 'super' access to add a new license file to Perforce without having to shutdown the server. See 'p4 help license' for additional information. (Bug #1948). Minor new functionality in 2006.2 #112275 ** Journal files now contain lines that demark rows written under a single database lock, to better support tools that parse it. (Bug #3582). #107394 ** 'p4 obliterate' has been changed for this release. Obliterate now makes use of the db.archmap (archive map) table to check for branched files (lazy copies). If lazy copies exist then the archive (file contents) will not be removed, consequently obliterating a file does not guarantee that the corresponding archive file is removed. See 'p4 help obliterate'. #107110 ** Files are now stored in the database archive keyed to the filename and (pending) change number, rather than filename and revision number. This information is normally only ever reported to users by the 'p4 obliterate' command, but administrators who examine the archive will notice the change as well. Note that old revisions in the archives will not be renumbered. (Bug #21543, #22756). #107943 ** Resolve conflict markers will now use whole paths to indicate file names and revisions. The ORIGINAL and THEIRS files will be in depot syntax while the YOURS file will be in client syntax. (Bug #18440) #107082 ** The new 'p4 sizes' command displays size information for files in the depot. It is functionally similar to the UNIX 'du' command. See 'p4 help sizes' for additional information. (Bug #3271). #106450 ** 'p4 submit' now sports a '-d description' option. This allows the user to submit files without the need for a changelist dialog. See 'p4 help submit'. (Bug #258). #105638 ** 'maxScanRows', which can be applied via 'p4 group' to prevent users from consuming too much server resources, has been extended to a number of additional commands and tables. Previously, it only applied to the db.rev, db.revhx, and db.revdx for all commands and the db.revcx table for 'p4 changes'. Now it applies to all tables for the p4 annotate, branches, change, changes, clients, describe, diff, diff2, filelog, files, fixes, fstat, have, integrate, integrated, jobs, labels, labelsync, lock, obliterate, open, opened, release, reopen, resolve, resolved, reviews, sync, and tag commands. maxScanRows applies separately to the number of rows read from each table, not the total from all tables. The most visible effect of this change is that 'maxScanRows' will limit access to the db.integed table for 'p4 integrated'. (Bug #10664, #19802). #102279 ** 'p4 branches/clients/labels' now sports a '-u user' option. This flag limits the command output to those owned by the specified user only. (Bug #6053). #101906 ** 'p4 changes -s pending' now allows a filepath where previously it didn't. (Bug #10634, #21275). #98791 ** The Perforce Server on Windows now uses native I/O routines for database access rather that using the POSIX layer. This fixes the problem of hitting the maximum number of open POSIX file handles. (Bug #19375). Bugs fixed since 2006.2/111150 (beta) #121930 ** 'p4 verify -v' on Windows could leak file handles when encountering missing or corrupt revisions in RCS archive files. This has been fixed. (Bug #24586). #121180 ** Under very rare circumstances of data in a btree, which are more likely just after a checkpoint restore, a btree record insert could cause the server to loop forever. Fixed. (Bug #24532) #120458 ** 'p4 resolve' used interactively resolving a ktext file with 'ay' i.e. accept yours would incorrectly report the resolved file as being tampered with at submit time or with 'p4 diff -sb'. Fixed. (Bug #24389) #119263 ** 'p4 obliterate' could leave database files in an inconsistent state. This could only happen if the user hit ^C or the command 'p4 monitor terminate ' was used during the processing of the obliterate. This has been fixed (Bug #24236). #116847 ** p4 submit would fail for files reopened by a previous p4 submit with a reopen option if those files were branched by the earlier submit. Fixed. (Bug #23776) #114374 * When p4d is in unicode mode, and the p4 command line has P4CHARSET set to a wide character set (i.e. utf16) and P4COMMANDCHARSET set to a character set other than utf8, p4 commands to edit specifications would interpret those specs as utf8 instead of the P4COMMANDCHARSET. Fixed. (Bug #23004) #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) #112219 ** 'p4 describe -s' would fail if the change contained a file in which the file's previous revision had been obliterated. This behavior has been fixed. (Bug #23211) #112011 ** 'p4 change -o' with tagged output would not see any modifications made by a form-out trigger. This has been fixed. (Bug #22578). Bugs fixed in 2006.2 #111144 ** 'p4 describe' on a change where an affected file's previous revision has been deleted could report incorrect differences. This case is now correctly handled by displaying an error message instead. (Bug #22987). #110722 ** 'p4 protects' command now displays an error message if the protections table is empty. (Bug #22731). #110294 ** 'p4 login ' which requires 'super' privilege can change the impersonated user's current session timeout. This has been fixed. (Bug #22537). #109913 * The cygwin 'p4' client program had trouble creating a directory if there was an executable by the same name in the parent directory. This was due to the way cygwin makes "foo" and "foo.exe" look the same. Now the 'p4' client program handles this case. (Bug #18387). #109855 ** Excessive wildcards (... and *) in client views, in branch views, in the protection table, and on the command line could cause the server to consume a lot of memory and time trying to work out all the possibilities. An efficient algorithm has been put in place that simplifies this work, and so such use of wildcards should not cause nearly as much problem for the server. This problem was previously addressed in 2006.1 by enforcing an internal limit on wildcard handling, but that was too restrictive and the limit was removed as a patch. A less restrictive internal limit is back in 2006.2, and that limit is very unlikely to be hit with the new algorithm. (Bug #18182, #10561, #19916) #108679 ** 'p4 filelog' can make unnecessary scans of the rev table under certain conditions. Typically this problem is triggered when the file following the argument filelist is excluded by a protection mapping. Fixed (Bug #22113). #108376 ** 'p4 fstat -Rn' would not filter files correctly as described in the documentation. This has been fixed. (Bug #22332) #108292 ** On some platforms, p4d would not start or log errors if the error log file exceeded 2 Gbytes. Fixed, now log files should not have problems exceeding 2 Gbytes if the platform supports such large files as database files. (Bug #13476) #108230 ** Corrected example trigger type in "p4 triggers" comments (Bug #22296) #108021 ** 'p4 integrate -f' of a deleted file more than once would leave the target file in an unusable state, where 'p4 submit' would say "Merges still pending" and 'p4 resolve' would say "file - has been deleted - revert and sync". Now the subsequent 'p4 integrate -f' has essentially no effect. (Bug #21864) #107629 ** Errors from a remote depot (most likely lack of permission for the 'remote' user) were going unreported by the local server. This has been fixed. (Bug #15878) #107321 ** Creating a new user with 'p4 user -f' with server security 2+ would result in "Bad parameters passed to mangler!" errors. This no longer happens, and the user should now only get the expected password error messages instead. (Bug #14726) #107305 * ** Logic regarding file clobbering and symlinks has changed substantially. Syncing a symlink onto a writable file should now honor the clobber client option. If a file type changes from symlink to text, the sync will no longer report a clobber error if the previous symlink points to a writable file. The P4 API also changed, see the p4apinotes.txt for details. (Bug #9814, #17099) #106098 ** Adding a View entry to any spec form with a leading '$' will result in an error and the form will not be saved. Previously this would not result in an error, and the spec would be saved without the entry, and also result in a bogus db.view value with map state of 3 corresponding to this invisible view. In the case of a branch spec, this would cause subsequent attempts to integrate using the spec to fail. (Bug #21942). #105408 * ** Temporary file handling has changed to not fail if a conflicting temporary filename already exists. Temporary files are also now named using a random sequence. (Bug #19573) #105334 ** Fields in spec forms (branch, client, label, etc) that have a # in the value are now quoted when output, so that the # is not stripped as a comment when the form is read back in. (Bug #20829) #105272 ** Date fields in jobs which are set by the server will be updated once after validating the job contents and again upon commit so that the value will reflect the time of commit. (Bug #21901) #105043 * ** Unknown field types or unknown field options in a spec definition no longer cause the server to abort on windows. (Bug #21822) #104828 ** 'p4 resolve -at' after a 'p4 integ' between files where only one of the files has keyword expansion as part of its type caused problems because keyword expansion would be done based on the source file's type, but after submit, sync would expand keywords based on the target file's type leading to differences which would be reported with 'p4 diff -se'. With this fix, in this case, 'p4 resolve -at' will expand keywords based on the target file's type. The proxy was also cacheing the wrong keyword expansion which could appear in other clients later sync operations. (Bug #20584) #104340 ** Server lock errors "Locking failure: 'table1' locked after 'table2'!", and "Locking failure: no upgrading 'table's' lock!" no longer cause the server to abort. Now the error is logged and will be tracked if server tracking is enabled, and the server will not exit. (Bug #19220) #102859 * ** A multiple resolves into the same target file revision where a subsequent resolve resulted in an 'at/accept theirs' i.e. a copy would cause earlier resolves to be converted into 'ignore'. Now, if you have new clients and this new server these earlier resolves may be converted into 'merge' if the merge system can resonably determine that no work is lost. (Bug #7130, #18896, #17100, #2540) #100946 ** 'p4 integrate' will now integrate into files already opened for add/branch/import. The action (add/branch/import) doesn't change, but a merge for 'p4 resolve' gets scheduled. This is the same behavior that has been available with files opened for edit/integrate. (Bug #12339, #13329). #100886 ** 'p4 integ -b' failure caused by invalid view mappings is reported more accurately. If the failure is caused by invalid havemap entries, the error will not be erroneously reported as invalid overlay mappings. (Bug #20653) #100847 ** The # (comment) character in specs is now treated more consistenly: it never introduces a comment in text blocks, and always introduces a comment in non-text block values. (Bug #21172). #100814 ** 'p4 client -d -f ' will now delete pending changelists created by the named client and also delete any fix records associated with it. The -f flag is now always required when deleting a client that has a numbered pending changelist associated with it. (Bug #2146). #100613 ** / is no longer allowed in client or depot names. Because of the way Perforce manages views, having a / in the name can cause data inconsistencies. Now / is simply disallowed. Most other entities (branches, labels, jobs, etc) can still have a / in them. (Bug 5422, 7152, 12904, 21751). -------------------------------------------------------------------------- -------------------------------------------------------------------------- Release 2006.1. Major new functionality in 2006.1 User file access tracking - #99426 ** The server can now log individual file access to an audit logfile. When auditing is enabled the server logs every time file content gets transfered to the client. Consequently this file will get large very quickly and there may be a small performance impact. To enable this feature: % p4d -r /usr/perforce -A auditlog Example output: 2006/05/09 09:52:45 karl@nail 127.0.0.1 diff //depot/src/x.c#1 2006/05/09 09:54:13 jim@stone 127.0.0.1 sync //depot/inc/foo.h#1 This was undocumented functionality in the 2005.2 release, but is now fully supported. 'p4 integrate' improvements - #96464 ** 'p4 integrate' has been rewritten to improve three areas, mostly with respect to indirect integration (when there is no direct relationship between source and target): 1) Better performance, especially when faced with rich branch history and many out-of-date files; 2) Better recognition of previous integrations, resulting in fewer merges; 3) Better base selection, using a "closest ancestor" approach, resulting in simpler merges. The previous logic almost invariably stuck to the source file when selecting the base. Now any revision of the source, target, or indirectly related files is a candidate, with the revision that shares the most changes with both the target and source being selected. As before, 'p4 integrate -o' and 'p4 resolve -o' report the selected base. (Bug #413, #17318, #17577, #17751, #18293, #20006). Minor new functionality in 2006.1 #99037 ** 'p4 integrated -b branch' now uses the branch view more efficiently to limit the number of integration records that have to be scanned. (Bug #20692). #96538 ** Minor 'p4 integrate' fixes with respect to deleted revisions: 'p4 integrate -Di' now attempts to integrate all outstanding revisions of a file that has been deleted and readded, rather than only those revisions since the last add. Previously '-Di' would find a base prior to the add but would only give credit for the revision after the add. 'p4 integrate -d' now implies 'p4 integrate -Di', as 'p4 help integrate' seems to have suggested. #95979 ** The merge algorithm has been rewritten. It now produces fewer conflicts to resolve, making automatic merging ('p4 resolve -am') more likely to succeed. Also, it is now better able to recognize identical changes that have been made in 'theirs' and 'yours' files. This should reduce the chances of getting duplicate inserts and generally improve merge output. #95535 * Clients operating in unicode mode with utf8 as their character set will now validate that data going to the server is valid utf8 and will error if it is not. New P4CHARSET options allow unvalidated operation. (Bug #19994) #93413 ** The 'monitor' counter now reflects the level of monitoring that the server provides. '0' and '1' are unchanged from from their current behavior of no monitoring or monitor running commands respectively. '2' also reports on idle processes that have run at least one command. Changes to the monitor counter requires a restart of p4d. (Bug #20097, #18869, #17246) #91389 ** 'p4 submit' has been modified to improve concurrency through better database locking. #90477 ** The following 'p4' commands now sport a '-m max' option: 'branches', 'clients', 'diff', 'fixes', 'fstat', 'groups', 'labels', 'opened' and 'users'. When this option is specified it limits output to 'max' number of entries. #88933 ** 'p4 groups' now has a -i flag to include subgroups when listing to which groups a user or group belongs. (Bug #7335). #89305 ** The new 'p4 protects' command shows the lines from the protections table that affect the given user/path. (Bug #2102). Bugs fixed since 2006.1/102189 (first release) #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). #113964 ** Concurrent 'p4 submit -c' and 'p4 change -i' of the same changelist could (under rare circumstances) leave a pending change record. Since the pending change record and the submitted change record share the same description, deleting the pending change would result in removing the committed change description. This has been fixed (Bug #19865). #113941 ** Unable to edit existing jobs which contain a TEXT field of type always or once and were set using a preset. This has been fixed (Bug #23440). #113687 ** 'p4 revert -a' could delete a local (modified) file, if the head revision was deleted and the client had been subsequently synced. This has been fixed (Bug #10201). #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) #109659 * Apple file types (apple, resource, etc...) stored from a PPC or classic Mac and later synced onto an Intel Mac or vis versa would have their Finder information swapped. Fixed. However, such apple files submitted from Intel macs may need to be synced with an old client and resubmitted with a new client to fix bad Finder information. (Bug #22438) #109240 ** The internal buffer on labels for 'p4 labels filespec' has been raised from 10,000 to 1,000,000. The command works regardless of the number of labels being examined, but if under the limit the command releases an important lock (on db.domain) early, allowing other commands to run. (Bug #22460). #109212 ** 'p4 opened -a filename' has been sped up considerably for sites with a large number of client workspaces. Previously, its performance was related to the total number of client workspaces on the server, but now it is only affected by the client workspaces that have the named file(s) opened. (Bug #22288). #108308 ** Change 89167 introduced in r06.1 restricted the use of '...' wildcards in client, branch and protections maps in order to prevent excessive use of cpu and server crashes. The limit imposed by that change was determined to be too restrictive, so the limit was lifted. (Bug #21706) #108264 ** 'p4 fstat -W ' performance could be very slow if a large number of files are opened. This has been fixed (Bug #22306). #107809 ** 'p4 integrate' would sometimes skip integrations when the integration history involved a copy away from the target. This has been corrected. (Bug #22198). #105845 ** Using 'p4 diff2' with a content trigger against a pending revision could incorrectly identify files as identical when they are different. This has been fixed (Bug #21946). #105715 ** Submitting a new version of a file with a pre-2003.2 client would result in the wrong digest value being set. This has been fixed (Bug #21893). #104421 ** Classic Mac OS clients could cause the 2006.1 p4d server to exit with an error about translate paths for OS 'current'. Now the server will not exit. (Bug #21735) #104154 ** Memory leaks fixed. Server leaked a small amount of memory for each table opened which was modified. (Bug #21741, #21742) #104130 ** p4 integrate of files with many branches and a complex integration history could cause the server to run out of memory. Fixed to limit the extent and depth of history searching. (Bug #21624) #104074 ** The new merge code was chosing an edit over a conflict even though the "theirs" edit effectively stomped on the "yours" delete. In most cases since both "yours" and "theirs" are removing lines this is probably a safe thing to do, however for safe merging this case will now be marked as a conflict like it was in the previous release. (Bug #21595). #104039 ** Integrating a ktext file to a text file resulted in bad checksums when running 'p4 verify' using the initial 2006.1 server. Fixed. (Bug #21693) #103879 ** 'p4 changes -i' under certain conditions could exclude changelists that were integrated into the specified files. Fixed. (Bug #21587) #103651 ** When a job is updated without specifying the '-f' flag, the server will reject changing the value of any 'always' or 'once' field to a new non-null value. If these fields are either omitted or have an empty value, then the server will set the 'always' fields as specified in the presets or restore the current values for the 'once' fields. By using this method of updating jobs, an application loses the ability to have the server detect potential job clobbering and will instead have to implement its own method for preventing overwriting of valid data. (Bug #21613) #103316 ** Using an older proxy (i.e. prior to 2006.1) with a 2006.1 server could cause binary files to be treated like text files and subject to newline translations. Other cases where filetypes get changed to text also occur. Fixed. (Bug #21578) #103097 * ** The new merge code was not recognizing certain cases which were borderline conflicts. This change applies a more conservative approach, now chosing to throw those edge cases into conflict blocks. (Bug #21451, #21589) #102793 * p4 integrate with a 'cherry picked' source range might choose a bad base when a 'dirty merge' from the target to the source files is present. Fixed. Similar to bug #15656. (Bug #21513) Bugs fixed since 2006.1/101179 (beta) #102186 ** 'p4 revert -a' could incorrectly report "no file(s) opened for edit". This was introduced by change #94600 which prevents file type changes from being reverted with the '-a' flag. This has been fixed (Bug 21467). Bugs fixed in 2006.1 #100015 ** 'p4 login' with a very high value for timeout would always create a new server ticket, rather than extending it. This would mean that logging in from one machine would effectively log you out of another. This has been fixed (Bug #21070). #99861 ** 'p4 integrate' no longer needlessly locks the db.revsx table (the revision table for spec depot entries), so that long running 'integrate' commands don't block spec updates. (Bug #21033) #99829 ** Shell expansion of 'p4' command line arguments no longer occurs when the command invokes a trigger. (Bug #20599) #95339 ** p4 print without the -o option can constructively use the proxy's cache now. For this to work both the server and the proxy must be upgraded. (Bug #19759) #94979 ** The error "Client 'client' can only be used from host 'host.com'" would also be generated if the hostname was case mismatched. This check has now been made case-insensitive. (Bug #4169). #94951 ** 'p4 revert' has been changed to prevent a user from reverting a file opened by different user. (Bug #1138). #94600 ** 'p4 revert -a' default behaviour has been changed so that it no longer reverts files that have been opened with a different type. (Bug #11390). #94008 ** Starting 'p4d', or performing checkpoint, journal, or recovery options on a depot with upgrade counter = 0 will generate the informational message "Perforce db files in 'P4ROOT' will be created if missing...". (Bug #20002, #9869) #93944 ** 'p4 diff -sl [ file[rev]... ]' displays unopened files with the status of 'same', 'diff', or 'missing' as each file is compared to its revision in the depot. When used in conjunction with '-f', this command may show this diff summary for all files in the file argument, including opened files. (Bug #14864) #93514 ** The Spec depot now handles concurrency correctly. Multiple changes to a spec occurring at the same time should no longer result in missing revisions. (Bug #18555) #93503 * ** The file types "text+C" and "text+F" are now treated by 'p4 diff2', 'p4 resolve' using merge, and 'p4 describe' as text files. Now files of these types can be compared and merged. (Bug #20111) #93286 ** 'p4 depot' will not save a depot spec unless the Map entry contains a trailing set of ellipses. The trailing ellipses is the only wildcard allowed. (Bug #18580, #19128) #90843 ** jobspec fields which are specified as 'always' will have the read-only nature of the field enforced by the server unless the -f flag is used. Since the server will populate these fields upon commit, any user data will be lost. This behavior can be used to prevent most job clobbering situations by including an always field of type date (e.g., a field for LastModifiedDate). (Bug #14813) #90571 ** 'p4 labels file[revrange]' can block other Perforce commands that need to update the db.domain table. This problem has been fixed by early release of this table lock. (Bug #19566). #90261 * p4 print -o would fail when the result file specified is a device such as /dev/null or /dev/fd/1. (Bug #19649). #89366 ** Wildcards (..., *, or %%x) are no longer allowed to be right next to each other in file arguments or views. Putting them together serves no useful purpose and consumes CPU as the server tries to deal with the combinations. (Bug #11188). #89167 ** Excessive use of ... wildcards in client or branch mappings (more than a few mapping lines with more than one ... in them) could cause the server to consume a lot of memory and time trying to work out all the possibilities. Generally this was not the intent of the user. Now the server has an internal limit and returns an error rather than wasting time when the ... wildcard handling gets excessive. (Bug #18182). -------------------------------------------------------------------------- -------------------------------------------------------------------------- Release 2005.2. Major new functionality in 2005.2 PERFORMANCE IMPROVEMENTS A number of changes have been made in the 2005.2 server that should result in better performance at most sites. Optimization of head revision operations - #79472 ** This release adds a new table db.revdx which when combined with the other head revision table db.revhx (2005.1) gives faster access to the top revision required by some commands e.g. 'p4 sync'. This improvement will reduce the compute phase (where locks are taken) especially where files have many revisions. Speedup for the 'integ' command - #77216 ** The performance of 'p4 integ' has been improved by batching its updates to benefit from the internal cache and a reduction in lock requests. Depending on usage, performance can be as much as 3 times faster than previous server versions. Early release of db.working/db.resolve during sync - #84071, #85678 ** Long running 'p4 sync' commands (compute phase) will no longer block 'p4 add/delete/edit' or 'p4 revert' in most cases. (Bug #14146) Server Performance Tracking - #86623 ** The p4d server now produces diagnostic output to help identify performance problems. The new support is on by default but can be turned off or adjusted with the '-vtrack=x' flag to the server. Any user commands that exceed certain thresholds for resource usage (CPU, lapse time, database I/O, network I/O, among other things) automatically get logged into the server error log P4LOG. The levels that can be set with -vtrack=x are: 0 turn off tracking 1 track all commands 2 track excess usage for a server < 10 users 3 track excess usage for a server < 100 users 4 track excess usage for a server < 1000 users 5 track excess usage for a server > 1000 users If -vtrack is not provided on the server command line or set with P4DEBUG, the tracking level is computed from the number of users listed in the server license file. The exact format of the tracking output is not documented, and subject to change. Spec depot interferes less with other commands - #86495 ** Revision entries for a 'spec' depot are now kept in a separate database file db.revsx, so that long running reporting commands don't block updates to user/client/branch/etc forms. (Bug #18939). Special handling for @changelist - #85130 ** The syntax '//path/file@change1,@somethingelse' now performs better in many common cases. Previously, the server would search based on changelist number or file path according to hard-coded rules. This worked poorly in a few common cases: both '//singlefile@1,@date' and '//...@5000,5001' started with the wrong search. This left users trying odd syntax to second guess the server. Now the server adaptively tries searching by change number, but if that appears to be too inefficient (more than 80% of the revisions not matching the path), it switches to searching by path. (Bug #18689). Speedup for clients with many opened files - #80624 ** 2002.1 and 2005.1 special optimizations were made to avoid scans when accessing the db.have table with a depot file argument (the db.have table is keyed on the client file). This optimization has now been extended to the db.working table (also keyed on the client file), and largely eliminates the need for large scans when referring to a small set of files. Further, this optimization no longer depends on the client view and db.have table being "in sync", often referred to as "mapState 1". Now the client view is augmented upon upgrade to 2005.2 and every time the client view is changed, and so mapState has been retired. (Bug #8348, #8929, #8930, #8931, #13439, #14006, #14500, #16985) EXTERNAL AUTHENTICATION TRIGGERS - #83081 ** External authentication support is built upon the 2004.2 support for ticket based authentication. When the user issues a 'p4 login' request the first trigger of type auth-check is executed, with the user's typed password on the trigger command's standard input. If the trigger successfully authenticates then a Perforce ticket is issued. Similarly, when the user issues a 'p4 passwd' request the first trigger of type auth-set is executed to set the new password (after the old one has been verified with any auth-check trigger). The user name is available as %user% to be passed on the trigger command line. (Bug #2398, #6730, #15417) UTF-16 SUPPORT - #85454 * When the server is in unicode mode, clients can support UTF-16 as a P4CHARSET settting. Details in i18nnotes.txt (Bug #1536) -------------------------------------------------------------------------- Minor new functionality in 2005.2 #86443 ** When using overlay mappings, adding a file on the overlay when a deleted file is present on the non-overlay mapping would give a file name changed error. Fixed. (Bug #11924). #86149 ** Jobs saved in the special 'spec' type depot are now updated automatically if their contents are changed with 'p4 fix', 'p4 change', or 'p4 submit'. The most likely automatic changes are those to the 'Status:' and 'Date:' fields. Previously the 'spec' depot was only updated by direct edits with 'p4 job'. (Bug #18030). #85670 * Character set translation failures during file transfers now report a line number near the first failure. Also, we now inspect the first 8192 bytes of a file to determine if it is a likely unicode vs text or binary file. (Bug #15369) #83894 ** Job fields marked as being 'always' updated are now updated when a fix is added or deleting to the job using the 'p4 fix' or 'p4 changelist' commands, or when a changelist affecting the job is submitted with 'p4 submit'. This is in addition to being updated when the job is updated directly with 'p4 job'. Previously (but never clearly documented) the 'always' fields were updated only upon the change of status due to 'p4 fix' (with a committed changelist) or 'p4 submit'. #83599 ** The trigger names in 'p4 triggers' have been renamed so as to clarify their purpose. The old trigger names 'submit', 'content', 'commit', 'in', 'out', 'save', and 'delete' are still recognized but the new names 'change-submit', 'change-content', 'change-commit', 'form-in', 'form-out', 'form-save', and 'form-delete' are preferred. #82165 ** 'p4 monitor show -e' and server log output will display a version string appended to the program name. If a client's version string is not available to the server (as set via 2005.2+ ClientApi::SetVersion()), the version string defaults to the protocolClient value. (Bug #15773) #80660 ** 'p4 opened -a file' and 'p4 opened -c change' have both been optimized to avoid a wholescale scan of the db.working table. (Bug #16132) #80493 ** The new 'p4 annotate -i' flag follow branches, just as 'p4 filelog -i' does. (Bug #15451) #78928 * ** Unicode type files could be submitted to a depot with a leading Byte-Order-Mark (BOM) which is not translatable into any character set other than UTF-8. Now, such files will sync into other character sets ignoring leading Byte-Order-Marks. This may cause discrepancies with p4 diff -se or -sa for such files. (Bug #17244) #77727 ** The new option 'p4 add/edit/delete -n' just displays the files that would be opened without actually opening them. (Bug #8946). #76458 ** 'p4 sync' now sports a '-k' option. This (keep) files option updates the server so that it appears that a client workspace already has the file(s) requested. Using this flag prevents files from being moved to the client workspace. #76292 ** 'p4 revert' now sports a '-k' option. This (keep) files option clears the open file action maintained by the server but does not change files in the client workspace. (Bug #16275). #75760 * Three Russian/Cyrillic character sets added. They are 'koi8-r', 'cp1251' (Windows Code Page 1251), and 'iso8859-5'. (Bug #8996) #73787 ** 'p4 annotate' now sports the -db and -dw flags from 'p4 diff' et al: ignore whitespace changes, and ignore whitespace altogether. (Bug #16286). Bugs fixed since 2005.2/88704 (beta) #101271 ** Memory leak fixed. A server running with spec depot enabled or additional local depots would leak memory. Typically this would be 20 bytes for each additional depot multiplied by the number of file arguments. (Bug 21127). #99156 ** Servers built with the SmartHeap memory manager (linux, windows), could require input from the user when the server was unable to obtain more memory. On linux this could happen when the server was holding locks, which (eventually) brings the server to a halt. The default behaviour has been changed so that the server does not prompt when out of memory. (Bug #20905). #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). #92200 *** The proxy would not properly expand the Date and DateTime keywords for file submitted with modtimes during daylight savings times while the submit actually happened not during daylight savings or vis versa. Fixed. (Bug #19757) #91541 * Temporary files were sometimes left in client workspaces by MacOS X clients. Fixed. (Bug #19576) #90419 * ** 'p4 -G jobs' lost the 'specdef' field when tagged output for forms was implemented in 2005.2. Now this field has been restored. (Bug #19600) #90017 ** 'p4 submit' using files with invalid or missing file modification dates will no longer cause file corruption. Instead, an error will be generated and the submission will fail. (Bug #16559, #18645) #89981 * ** Add new environment variables P4DIFFUNICODE and P4MERGEUNICODE which are like P4DIFF and P4MERGE for invoking external tools from the command line except that when the file is of type unicode and the server is in unicode mode, the character set is passed as an argument to the commands those variables point to. This can allow p4merge to be invoked from the p4 command line tool on UTF-16 files successfully. (Bug #19465) #89793 * Arguments to commands defined in P4MERGE or P4DIFF will no longer cause the commands to fail to execute. This behavior was due to a short-lived bug only in the beta release, and has now been fixed. (Bug #19529) #89471 'p4 edit/delete/add' of a file in a spec depot should not be allowed, this has been fixed. (Bug #19463) #89406 Deleting a form when a spec depot has been enabled will result in a server crash, this has been fixed. (Bug 19455) Bugs fixed in 2005.2 #88299 The server was not updating the filesize or digest for spec depot files. This has been fixed, older files can be updated by using the 'p4 verify -u' command. (Bug #19044) #86806 ** 'p4 label' or 'p4 client' could cause the server to crash if the label or client name contained the "%%" wildcard character sequence. Now this character sequence is not allowed in the name of any new labels, clients, branches or depots. Any entity which already has this illegal character sequence in its name is still accessible. (Bug #17563) #86505 ** p4 submit -r would leave branched files read-only while also open for edit. Now such files are made read-write. p4 submit -r should now leave open all submitted files which remain on the client after a submit. (Bug #15937, #17684, #18435) #86189 * ** p4 resolve would wrongly duplicate a common insert in some cases. Fixed. (Bug #18844) #85995 * 'p4 -x ' would report unknown client in the server log file for argument processing after the first 128 arguments which are run in second and subsequent commands. Fixed. (Bug #18780). #85795 ** Importing from a remote depot could result in an unusable db.rev archive file. This would require a certain combination of multiple integrations where the last is an ignored local depot file. Subsequent access to the newly submitted revision would result in the error "Can't map //remotedepot/filename to archive!". This has been fixed. (Bug #17823). #85674 ** An integrate command may miss that a delete needs to be integrated when there are multiple levels of indirection between the source and target. Fixed. (Bug #18652). #85630 ** A narrow performance problem involving labels, the "*" wildcard, and directories with lots of subdirectories has been fixed. (Bug #18819). #85445 ** 'p4 -R' now works with marshalled input from Ruby 1.8.x (Bug #18053, #18433) #84221 ** A revision specification of @change,change against a remote depot works again. For a long time using a change number in the revision syntax for remote depot files would use the local change index against the remote files. Now it filters remote files using their own change numbers. (Bug #13451). #84221 ** A revision specification of pattern@1,@date now uses a lot less memory, related to the number of files matching 'pattern' rather than all files since change 1. (Bug #18441). #81300 ** Really long arguments (>2048 bytes) to 'p4 dirs' could crash the server. This has been fixed. (Bug #17199). #80547 ** 'p4 logout -a' now removes the ticket stored on the client as well as the ticket stored on the server. (Bug #17798). #80127 ** 'p4 logout' can now be executed if the user has a valid ticket but it has expired. Previously the user would have to run 'p4 login' first. (Bug #17727). #76684 ** 'p4 fstat' now accepts multiple -O and -R flags. (Bug #16957) -------------------------------------------------------------------------- -------------------------------------------------------------------------- Release 2005.1. Major new functionality in 2005.1 PERFORMANCE IMPROVEMENTS A number of changes have been made in the 2005.1 server that should result in better performance at most sites. Speedup for the 'dirs' command - #69248 ** The performance of the 'dirs' command is now no longer affected by the number of files deleted at their head revision. Since the 'dirs' command is used by GUIs such as P4V and P4Win, browsing through portions of the repository with files deleted at their head revision will now be faster. This speedup uses the new db.revhx table. (Bug #7068) Speedup for the 'obliterate' command - #72594 ** A number of changes have been made to reduce the fixed overhead of 'p4 obliterate'. Now the overhead is more or less relative to the number of clients and labels, rather than the size of the clients and labels. Also improved is the handling of lazy copies in that obliterating a revision that is the source of many lazy copies no longer creates many revisions in the versioned files tree. This speedup uses the new db.archive table and leverages the MapState simplification (see below). (Bug #15047) Btree passive reorganization - #68043 ** As updates are made to the db.* tables, the server now reorganizes portions of the table as necessary to maintain sorted order across contiguous leaf pages. These passive reorganizations will result in better performance when scanning portions of the table since physical movements of the disk heads will be reduced and readahead will be more effective. This feature should reduce the need to periodically recreate the db.* tables from a checkpoint to improve performance, but may increase the size of some of the db.* tables due to the allocation of new contiguous pages. MapState simplification - #72631 ** Using depot syntax for a number of commands ('p4 sync', 'p4 have', 'p4 fstat') has been sped up considerably in certain cases. Previously, such commands were fast only if the client workspace was 'in sync' with its current client view. This limitation no longer applies. Now the results of the first scan after changing the client view are used to avoid further costly scans, whether the client is in sync or not. SPEC DEPOT - #69793 ** A new depot of type 'spec' archives all edited forms (branch, change, client, depot, group, job, jobspec, protect, triggers, typemap, and user) into special, read-only files in that depot. The files are named //specdepot/type/name[suffix]; suffix is optionally given as the 'Suffix:' field on the depot form. The archived forms can be accessed as any other file, but there is no special provision for using the forms, other than using the form-specific command's -i flag (e.g. p4 client -i). Automatic updates to a form, such as access times, opened files (for changes), status (for jobs), etc, do not change the saved forms: only those made through the regular form editing commands. The spec depot was introduced as undocumented functionality in the 2003.2 release, but is now fully supported. (Bug #250). PARTIAL FILETYPES - #68575 ** The filetype given to 'p4 add', 'p4 edit', 'p4 reopen', and 'p4 typemap' can now be just a partial filetype, with the '+modifiers' only. A partial filetype modifies rather than replaces the default one. For example, if a text and binary file are added to a location in the repository covered by a typemap entry specifying a partial filetype of '+l', the text file is added with a filetype of 'text+l' and the binary file is added with a filetype of 'binary+l'. See 'p4 help filetypes' for additional information. (Bug #594, #4003, #6562, #6742) DELETE TRIGGERS - #68258 ** Complementing the spec triggers introduced in the 2004.2 release is a new spec trigger type of 'delete'. This trigger will run prior to deleting the spec. A delete trigger can be used to limit when a spec is deleted. For example, a delete trigger can be used to prevent unauthorized users from deleting jobs. (Bug #15235) -------------------------------------------------------------------------- Bugs fixed since 2005.1/79540 (first release) #89300 ** A Perforce server running with monitor enabled could encounter problems with a multi-threaded client issuing overlapping requests on the same server connection. Under certain conditions this could lead to a server crash. This has been fixed. (Bug #19381). #86943 ** Under rare circumstances a btree passive reorganization may fail with an 'insert failure'. Fixed. (Bug #18960) #86558 ** Using mmap (memory mapped) file access for the server platform AIX 5.3 has been disabled due to a problem with that O.S. implementation. (Bug #18951). #82815 ** Servers running on some versions of Linux prior to 2.6.11 could be prone to seeing sporadic zombie processes. Although this is a Linux kernel bug this change provides a workaround for those customers who cannot obtain a later release of the fixed kernel. (Bug #17328). #82100 ** Failure to archive forms to the 'spec' depot were not being reported to the client application, this has been fixed. (Bug #18091). #81216 ** Bug fix #80169 (update db files) could be executed for each database access instead of once. Although this update should not pose any problems it could slightly affect performance. This has been fixed (Bug #17960). #81207 ** 'p4 verify -q' would not detect a missing archive file if the digest had already been computed and saved. This has been fixed (Bug #17909). #80631 * ** p4 resolve or merge tools when 'accept theirs' is chosen could leave a file which did not match the server's version of the theirs file. Bad auto merges are also possible. Fixed. (Bug #17752) #80628 ** Upgrading to 2005.1 from a release older than the previous 2004.2 release could result in an incorrect value for a files size being reported (p4v, p4ftp). This has been fixed (Bug #17822). #80169 ** Upgrading to 2005.1 (this release) when the server's db files were created originally by a p4d version prior to 2001.1 and which a checkpoint has never been recovered by a server version 2001.1 or later will have database update problems. Fixed. Once this fixed server is run, you can not run older 2005.1 servers without a checkpoint recovery. (Bug #17732) #79941 ** p4 filelog -i would show details of files for which the user has no permissions if those files were branched to files the user has access to. Now, filelog -i will silently not visit ancestor files which the user does not have permission to inspect. (Bug #17691) Minor new functionality in 2005.1 #72238 ** 'p4 verify' has a new flag '-m maxRevs' which limits the number of revisions which can be verified. Using this option may require several iterations before each revision has been processed. As of change #70719 newly submitted files will have the length maintained by the server. Previous revisions will have their length computed when running verify with either the '-u' or '-v' option. It is recommended for a large repository where this update could take a long time to use the '-m' option when updating the metadata for the first time after upgrade. #71026 ** 'p4 filelog' has a new flag '-L'. This option produces long output with a 250 character truncated changelist description. (Bug #15880). #70950 ** 'p4 changes' has a new flag '-L'. This option produces long output with a 250 character truncated changelist description. (Bug #15791). #70906 * Allow the ticket file location to be configurable. The user can now define the location of the file used by 'p4 login' and subsequent connection attempts by setting the environment variable P4TICKETS. This variable, like other Perforce variables can be set at the command prompt or set in a P4CONFIG file or as an NT registry variable through 'p4 set'. e.g setenv P4TICKETS /secure/myname/ticketfile (UNIX csh) p4 set P4TICKETS=c:\secure\myname\ticketfile.txt (NT) (Bug #14912). #70719 ** The server now maintains the filesize in the metadata, this makes the 'p4 fstat' option '-Ol' much faster. (Bug #15844). #70543 ** Remote depot access for 98.2 and 99.1 servers has been dropped. #70419 ** 'p4 fstat' has a new flag '-Of'. When this option is selected all revisions for the given file(s) are displayed. (Bug #15810). #70345 ** Some commands have now been given synonyms: synonymn command -------- ------- changelist change changelists changes workspace client workspaces clients Either name will be accepted, however errors and form fields will continue to refer to the original command name irrespective of what name the command was executed with. #69880 ** 'p4 fstat' adds 'desc' (change description) to its list of output fields. This field will only be displayed when the option to display files affected by a given changelist number '-e changelist#' is specified. (Bug #15693). #69803 ** 'p4 opened' has a new flag '-C client' which limits output to files opened by the specified client. (Bug #15676). #69639 ** 'p4 fstat' adds 'otherChange#' to its list of output fields, this field will only be displayed if the file is opened. (Bug #15599). #68917 ** 'p4 fstat' adds 'digest' to its list of fields that are ouput, this field will only be displayed when the '-Ol' option is used. (Bug #15484). Bugs fixed in 2005.1 #79498 ** Application-licensed servers cannot be accessed remotely, this has been fixed (Bug #14978). #79322 ** For certain client views 'p4 labelsync' could repeatedly delete and add the same file each time its executed. (Bug #16613). #78873 ** On some platforms (linux) with 'monitor' enabled the command 'p4 admin stop' could hang the server. This has been fixed (Bug #13509). #77879 ** Indirect Integrations involving recently branched files which are then deleted via integration might stop propagating the delete via indirect integrations. (Bug #17233) #75719 ** Under certain circumstances and on particular server platforms (Solaris) the 'Options' field of a Perforce client could get corrupted when being displayed. This has been fixed (Bug #16806). #75711 ** 'p4 -Rc -e #changelist' could take a long time if the client view prevented any of the files in the changelist from being mapped. This has been fixed (Bug #16482). #74983 ** 'p4 job Job' against an NT server would override the same storage used by 'p4 jobspec'. (Bug #16300). #74847 ** 'p4 tag' would create labels with uninitialized access and modification times, this has been fixed. (Bug #14524). #74432 ** Indirect integration credit was missed in certain combinations of a copy from and a branch from a common ancestor. (Bug #16478) #74228 ** 'p4 fstat -W' has been speeded up by removing the redundant db.have client file scan. (Bug #16031). #73742 ** 'p4 fstat -e #changelist -W' on some platforms would fail to return the files opened in that changelist. This has been fixed (Bug #16342). #73518 ** The filetype option 'apple+k' would fail in previous versions with the error "AppleSingle/Double corrupted". This failure was due to an incompatability between the apple resource fork code and the RCS keyword substitution code. This combination is prohibited and is now rejected when trying to set it rather than after submit. (Bug #16238). #72937 ** Indirect integrations might schedule deletes without the -Ds or -d flags when such flags would be needed. Fixed. (Bug #15917) #72512 ** Revisions for a 'group' stored in the spec depot did not contain all the users added to that group only the last ones added in the last update. This has been fixed (Bug #15583). #72406 * On Windows clients operating with character set UTF8 use Unicode Windows APIs to get user related environment variables and allow Perforce variables to supply these enviroment values. (Bug #15933) #71608 ** Indirect Integration credit was not given for all paths when more than one credit path shares intermediate credit paths indirectly resulting in some unnecessary integrates being scheduled or base files for merging which are older than needed. Fixed. (Bug #15942) #71169 ** The 'Timeout' field which can be set by 'p4 group' was not allowing a value of 0 (no timeout), this has been fixed. (Bug #15712). #70975 ** Starting p4d as a service on NT would fail if upper case was used for the executable name. Fixed. (Bug #11839) #70890 ** 'p4 integ' would schedule integrations which are not needed when the source was a copy integration from a third file which was edited into the target. (Bug #15719) #69841 ** A trigger on 'p4 change' wouldn't fire on 'p4 change -s', which is used by p4win. Now it does. (Bug #15602). #68886 ** 'p4 login' IP based tickets would not work against a central authentication server, this has been fixed. (Bug #15469). #67888 ** If a post-submit trigger fails then the server can incorrectly issue the message "Submit validation failed -- fix problems then use 'p4 submit -c '". If no ktext files are refreshed during the submit then no error message is seen at all. This change fixes both these problems. (Bug #15265) #67042 ** p4 sync #none no longer changes permissions on symlink target files (Mac OS X and Darwin only). (Bug #15175) -------------------------------------------------------------------------- -------------------------------------------------------------------------- Release 2004.2. Major new functionality in 2004.2 SECURITY LEVEL (Authorization and security levels) The new security features introduced in 2003.2 but undocumented are now fully supported. Most of the changes are built upon the existing system which when used correctly provide adequate protection for most development environments. However, this system did not provide for password enforcement, password strength enforcement and allowed unsafe practices to be established. 2004.2 introduces the concept of a perforce server security level, basically the higher the level the greater level of enforcement. In some cases enforcing a greater security level will make the usage too restrictive for some sites where it simply isn't necessary. The new security features do not offer native data encryption. As in previous versions, Perforce recommends SSH or VPN as a means of access over insecure networks. Setting a security level: To provide backwards compatability the default setting for security allows similar authorization as previous versions. To set a security level in the server a super-user must set the new 'security' counter into the system: e.g. p4 counter -f security 1 (server must be stopped/restarted) The following is a list of the values and their action. security feature/function 0 (unset) * 'p4 login' support. 1 * 2003.2+ clients enforce passwords * 2003.2+ clients require strong passwords 2 * cannot modify password through 'p4 user' * cannot modify password through 'p4 passwd -O -P' * pre-2003.2 clients cannot set password * pre-2003.2 clients cannot use login * unverified strength passwords must be changed * passwords no longer stored/retrieved from registry (NT) 3 * 'p4 login' tickets are the only way to connect to a server, passwords are no longer accepted. NEW LOGIN/LOGOUT COMMANDS PROVIDE PERFORCE ACCESS THROUGH TICKETS The new 'p4 login' command allows a user to establish an authorized connection to the Perforce server by a ticket granting mechanism. A session can be terminated by issuing a 'p4 logout' command. See 'p4 help login/logout' for usage. New field 'Timeout' in 'p4 group' 'p4 group' now has a 'Timeout' field, which can be used to change the default (12 hours) login timeout value for a group of users. This value represents the number of seconds that an issued ticket from the server will be valid for. NEW TRIGGER SUPPORT (mid-submit, post-submit and forms) 'p4 triggers' now supports mid- and post-submit triggers in addition to the existing pre-submit ones. mid-submit triggers happen after file transfer and use a limited set of commands to access the file content via the special revision specification @=change, where change is the pending changelist number. post-submit triggers happen after the commit and therefore cannot stop the operation. (Bug #1651, #1929, #11861) Also, 'p4 triggers' supports triggers on all forms (like 'p4 branch' and 'p4 user'). There are three triggers available: 'out', 'in', and 'save'. An 'out' trigger is run form when the form is generated; an 'in' trigger is run when the form is being saved, but before the server parses it. Both 'out' and 'in' can modify the form. A 'save' trigger is run after the form is parsed and validated by the server. A 'save' trigger cannot modify the form. (Bug #796, #1651, #9738, #10536) NEW INDIRECT INTEGRATION DEFAULT 'p4 integrate' now always considers indirect integrations through intermediate branchs when determining that files are related and what changes need to be integrated. The direct/indirect option in branch specifications has been removed as all integrations will be considered indirect. Related is that 'p4 integrate' may select a base for merge resolution from a common ancestor which is neither the source nor the target file. NEW SMART RESOLVE LOGIC Conflict resolution with 'p4 resolve' has been changed. The new logic reduces conflicting regions with more complex detection of commonality of changes. FILEPATHS THAT CONTAIN CHARACTERS @#%* CAN NOW BE ADDED TO THE DEPOT Previously the special characters "@#%*" could not be included in a file submitted to the repository, instead an error would be generated. As of this release the Perforce command 'p4 add -f' will allow these special characters to be included as part of a filepath. Without the '-f' option an error message will be generated for files containing wildcards. Once added these files can only be referred to in their formatted syntax. For example 'p4 add foo#bar' will result in a file being submitted under the formatted name 'foo%23bar', notice that the '#' gets translated to it ascii hexadecimal represented value '%23'. The syntax to edit the file once it has been submitted would therefore be 'p4 edit foo%23bar'. Perforce commands like 'p4 have' and 'p4 fstat' will show both formatted and local (filesystem) names. These filenames will of course be expanded back to their original submitted name when synced down onto client machines. (Bug #1339, #13270). Note that due to this change, the wildcard %d used in reordering filepaths in viewspecs has now changed to %%d. NEW TAG COMMAND PROVIDES EASY WAY TO ASSIGN A LABEL TO A FILELIST Similar in syntax to the more advanced 'p4 labelsync' command 'p4 tag' allows the user to tag files with a label without requiring a client spec. See 'p4 help tag' for further details. (Bug #9903). -------------------------------------------------------------------------- Minor new functionality in 2004.2 #58026 ** 'p4 fstat' has two new flags. The '-O' flag used to request extra information that is usually suppressed and the '-R' flag that is used to restrict output depending on certain criteria. A number of old fstat flags have been folded into these new options. See 'p4 help fstat' for details. (Bug #13343) #56674 ** 'p4 integrate -Di' allows the integrate command to find a base for file merge prior to the latest add of the source file. That is if a source file was deleted and recreated (via add or a branch) those revisions prior to the add could provide a base for integration. This is intended to support cases where files are deleted and readded but still maintain content continuity across the delete. (Bug #11929) #56035 ** 'p4 submit -r' now supports reopening of files that have been branched. (Bug #13380). #56034 ** The 'p4 integrate' command can now determine if a base for merge resolution lies on any ancestor version even if that version is a file which is neither the source nor the target. The base file and version is reported by a change in the output of 'p4 integrate', 'p4 resolve', and 'p4 resolved' if a '-o' option is given with those commands. (Bug #413) #55851 ** The new 'p4 integrate' default of considering indirect integration history allows the command to refuse baseless merges while considering indirect integrations when the -i and -I flags are not supplied. Changes to help descriptions and spec descriptions and problems regarding integrate and branch are corrected. (Bug #3757, #9034, #10740, #11631) #53703 ** 'p4 fstat' has a new flag '-e #changelist'. When this option is selected only files that are affected by this changelist are displayed. (Bug #13258) #53137 ** 'p4 fstat' adds 'type' to its list of output fields, this field will only be displayed if the file is opened. (Bug #13259). #52894 ** 'p4 labelsync' is now atomic in its update of the label table. Previously if a user issued a 'p4 sync //...@labelname' command during a labelsync operation (of the same label) it could be possible to get an inconsistent sync. (Bug #13184). #52329 * ** Files stored as compressed binary (most binary files) are now left compressed over the wire and uncompressed only when they reach the client. (Previously, they were uncompressed on the server and sent to the client that way.) This new behavior is not optional, and is unaffected by the client's "compress" option, which continues to compress all data between the client and server. #51751 ** 'p4 monitor' now sports a '-e' flag to allow superusers to see more about a users environment. The '-e' flag adds the client program name (if known), client name and host address to the list of fields displayed. (Bug #12737) #50570 * P4CHARSET now supports iso8859-15 which is essentially latin-1 with the Euro currency symbol. #50459 ** Overlay (+) mappings are now supported in client views. This allows a client to overlay a sparse tree from the depot on top of a denser on already mapped on the client. Overlay mappings are specifically prohibited in branch views, and have no special effect in label or other views. Bugs fixed since 2004.2/68597 (first release) #81443 * ** During change resolution via p4 resolve an 'accept theirs' could leave a file on the client which does not match the server's original 'theirs' file. (Bug #17890) #80025 * ** Problem with resolve/merge duplicating code when the base file has extra lines at the end that the source and target file do not has been fixed. (Bug #17695) #79733 ** Triggers were inheriting too many handles from the server process on Windows and could exhaust a system wide handle resource limit. Critical handles no longer inheritied. (Bug #17654) #79315 * P4 clients on MacOS X which change files not owned by the user who runs the p4 client may encounter crashs and many temporary files left after the crash. Error messages will now be produced. (Bug #17399) #76944 ** Prevent server from exiting prematurely on encountering a lock upgrade problem. (Bug #17078) #76880 * ** Resolve logic to expand common change regions could cause crashes or bad merges. Changed to only rarely expand common changes when changes align at start. (Bug #16991) #76510 ** 'p4 fix' of a job against a non-existent changelist could result in a server crash, this has been fixed (Bug #16959). #74828 ** Resolve might cause a server crash or repeat the whole file contents as a conflict in rare cases. Fixed. (Bug #16596) #73359 ** Bug fix #72493 introduced another possible crash. Revised that fix to avoid the crash. Diffs may report slightly differently with this revised fix. (Bugs #16118, #16425, #16248) #73084 ** With maxResults or maxScanRows set with 'p4 group', changing your client view to map files to a different location could result in being unable to refer to existing files in the client workspace using depot syntax (//depot/name). This has been corrected. (Bug #16205). #72935 ** Trying to sync a compressed binary file from a pre-2004.2 remote server would result in the error: "Operation 'rmt-FileFetch' failed. Unsupported librarian file type 7!" This has been fixed (Bug #15831). #72642 ** Integrate might miss files which need integration when there is a mix of cherry picked integrations and those which are not in intermediate integrations when searching for indirect integration credits. Fixed. (Bug #16141) #72638 * ** Resolve might not detect conflicts when the two files have a change which starts as a duplicate, becomes a conflict, then one file has a change. Fixed. (Bug #16142) #72493 * ** Resolve might cause the server to crash. Crash was due to reading past the end of the yours file. Fixed. (Bug #16118) #71759 * ** The new resolve logic might cause the server to crash. Would happen on very complex merges with overlapping changes and similar regions. Fixed. (Bug #15968) #71497 * ** The new resolve logic might loop consuming all CPU in the server or merge tool when the two files being merged are substantially the same but with many small fragments in common with the base. Fixed, but more cases may be reported as conflicts than before this fix. (Bug #15930). #71324 ** The variable '%change%' for submit triggers is no longer available. This change corrects this omission (Bug #15597). #70948 * ** The new resolve logic might loop consuming all CPU in the server or merge tool when blocks of lines are shuffled with few actual new lines or lines really removed. Fixed. (Bug #15867) #70343 * ** The new resolve logic might drop a line in the following situation: * There is a change common to the 'theirs' and 'yours' files. * Just after that change a line in all files matches a line at the end of a change in one but not both of the 'theirs' and 'yours' files. When this problem happens that common line is lost at end of the insert block which is not common. Servers with versions between 69424 and this fix actually reported a conflict in this case and the conflicting base case would report lines already merged. Fixed. (Bug #15751) #70281 ** 'p4 obliterate' cannot distinguish between an already deleted archive file and failure to undo a lazy copy due to lack of disk space, this can lead to archive data loss. This has been fixed by backing out change #45574. (Bug #15756). #69739 ** 'p4 monitor show' could crash the server on SGI due to large pid value. This has been fixed (Bug #15657). #69731 ** Client server would deadlock with the server on a Linux machine. Reverted change 55835 so that we once again look at the OS TCP send buffer size rather than the receive buffer and we reduced the maximum expected amount of returned data to 16000 bytes. (himark limit) (Bug #15606) #69727 ** Integrations with source revisions ranges specified (so called cherry picked integrations) might choose the base on the target file instead of the source file. Fixed. (Bug #15656) #69643 ** The handling of 'p4 sync @=changelist' accidentally changed to cause files not in the changelist to be removed from the client. This syntax is used by p4win to speed up syncing a single change. Now 'p4 sync @=changelist' again means the same as 'p4 sync @changelist,changelist' as it should, and only affects the files in the given changelist. (Bug #15640) #69424 * ** The new resolve logic could report conflicting regions as too small and those lines would appear to not be conflicting. If that happened, sometimes lines would also be omitted from the end of the file. (Bug #15425) #69124 * Due to an inconsistent implementation of a specific system call on LINUX, it was possible for p4 clients such as p4v to consume lots of CPU and appear to hang. This has been fixed (Bug #15538). #69080 * ** The new resolve logic could duplicate lines in the result if accept theirs were selected interactively from a client. Fixed, however there may be minor differences in the report of fragment counts regarding differences during result and differences in reported common lines. Standalone GUI merge clients are affected. (Bug #15502) Bugs fixed in 2004.2 #65225 ** The Perforce Windows Service now shuts down normally during a system reboot. Before it was terminated by the Service Control Manager. (Bug #13257) #62199 ** 'p4 -G job -o' and 'p4 -R job -o' failed if the jobspec contained required fields that deliberately defaulted to invalid values. This has been fixed (Bug #11561). #61038 ** Saving a client spec with view arguments to depots which the user has no access (i.e. no 'list' access or better as granted by 'p4 protect') could cause the server to crash. (Bug #14462). #60787 ** Some passwords greater than 16 characters would not be recognized after being set by the user, this has been fixed (Bug #14431). #60299 ** The server will now recognize a license file called "license.txt" as well as the default one "license". This will make installation easier on Windows platforms where often the file has to be renamed before the server can be started correctly. (Bug #14461) #59047 ** Archive files with redundant versions of revision text and ancestral revisions of such a revision can be read properly. (Bug #13954) #58393 ** Mac OS X now uses Unix permissions instead of HFS locking to prevent edits to a file. If it detects a file has the HFS lock set, it will convert it to the new system. HFS locks will never be set by Perforce. (Bug #7096, #11534) #58391 ** Syncing or opening links for edit will no longer change the flags on the files pointed to by the link, but will affect the link itself. Mac OS X only. (Bug #13639, #13640) #58964 ** Archive files with missing revision contents but revision listed in archive header will no longer crash the server. (Bug #14229) #57966 ** Jobs with empty names can no longer be created (but they can be deleted). (Bug #14141). #57268 ** 'p4 login' tickets would not work against a proxy server, this has been fixed. (Bug #13931). #57034 ** After 'p4 verify -u' had been used against the revisions in a spec depot, all new revisions would be reported as 'BAD' by 'p4 verify'. This was caused by the server incorrectly reusing the checksum of the previous revision. This fault has now been fixed. (Bug #13096) #57029 * Client connections would fail if P4PORT specified a hostname starting with a digit. This has been fixed (Bug #4796) #56972 ** 'p4 dirs' is no longer limited by the number of directories it can report. (Bug #13803). #55835 ** Client server would deadlock if the server's operating system reported more TCP buffer space available than was really available typically happens if a server has been configured with very large TCP buffers. p4d is now more conservative and tries to keep less than 30000 bytes expected in its receive buffer. Also, measure the OS TCP receive buffer rather than the send buffer for this setting (himark limit) (Bug #13364) #55389 ** Under certain conditions where old tempobjs and new tempobjs were being submitted together it was possible that some of the new tempobj archive files would not be deleted. This has been fixed (Bug #13628). #54731 ** During a 'p4 submit' operation it was possible for another Perforce client (same P4USER, same P4CLIENT) to interfere with the operation by (for example) reverting files currently being submitted. Checks have now been put in place that make sure that this cannot happen. Should such a change be detected 'p4 submit' will issue the error message "Files newly opened or reverted during submission" and abort. (Bug #13279, #4104) #54050 ** Missing '%' character in a 'p4 triggers' command string could cause a server crash during a submit. This has been fixed. (Bug #13346). #53436 * ** Text file diffs would rarely produce non-optimal diffs on small files with short lines. (Bug #13228) #51219 ** Merely adding or removing a "-" to the mapping of a trigger table line of 'p4 triggers' would fail to be recognized as a change to the table. This has been fixed. (Bug #12789) #50451 ** By remapping a file opened for edit to another depot file, and then syncing that depot file using depot syntax, it was possible to forget that the file was opened. This has been fixed. (Bug #1445) #50435 * ** 'p4 diff2' now always displays '' to indicate "no file". Previously '< none >' was used on the left side. Users requiring the old behaviour for scripts or applications can set the protocol variable "api" to a pre 2004.2 value for example -Zapi=56. (Bug #2127) #50078 ** 'p4 client' and similar commands that edit specs could cause a server crash if a view argument was preceeded by a double-quote with no matching end quote. This has been fixed (Bug #13730). -------------------------------------------------------------------------- -------------------------------------------------------------------------- Release 2003.2. Major new functionality in 2003.2 Performance Improvements 2003.2 incorporates a number of changes addressed at the performance of large installations. While these changes were tested against a server of 1M files they should, of course, benefit all servers to some degree. Optimization for frequent syncs - #47694 ** A narrow optimization was made for large client workspaces that do frequent 'p4 sync' commands, typically automated build or test client workspaces. The syntax 'p4 sync @changelist,#head' now makes use of a database index to make its speed related to the number of files affected since the named changelist, rather than the number of files already in the client workspace. To take advantage of this, scripted build or test clients must remember a recent changelist number and sync to changes since that changelist. The provided changelist can be earlier than that previously synced, but the closer it is the faster. This optimization is targeted towards automated client workspaces, because they are in a position to track a recent changelist number. Further, interactive users typically don't sync all of a large client workspace at once. Label use speedups - #47813, #47771 ** Specifying revisions using file@label,label, where the label doesn't contain the named file, no longer causes quadratic behavior. (Bug #11540) Specifying revisions using @label, where the label doesn't contain revisions from a remote depot, will no longer access the remote depot. (Bug #7225) Locking and memory use improvements - #47939, #47402, #46797 ** Concurrency and memory use on 'p4 sync' and 'p4 integrate' have been improved by freeing up temporary resources earlier. Subtle database locking improvements have been made. Previously, any command that could expect a revision specification locked tables (such as db.have and db.label) in anticipation of needing them. Now they are only locked if the command actually makes use of them by including a @client or @label revision. 'p4 sync' now batches its updates to benefit from the internal cache and reduce lock contention. (Bug #9893). Speedups for large client views and protections tables - #48061 ** Large client views or protection tables should no longer slow 'p4 sync' or 'p4 integrate' quite so severely. Indirect integration much faster - #47038 ** Performance of 'p4 integrate -I', which looks at intermediate integations when determining a base, has been significantly improved. Its performance should now be similar to the normal direct integration only case. (Bug #10587). Minor new functionality in 2003.2 #50484 ** 'p4 annotate' now sports a -c flag: output change numbers instead of revision numbers with each line of the file. #48532 ** Depots to which the user has no access (i.e. no 'list' access or better as granted by 'p4 protect') no longer show up in the output of 'p4 depots'. Nor do they appear in the default branch, client, and label views. (Bug #11969). #47719 * ** The MD5 digest (fingerprint) of files are now computed and stored during submit. For best performance, use both a new 2003.2 client as well as server, as the new 2003.2 client programs offload the MD5 computation from the server. (Bug #2696). #47373 * 'p4 diff -db|-dw' now ignores line-ending differences as well as whitespace. This is very useful when used in a mixed platform environment. (Bug #11639). #46947 * 'p4 diff' can now ignore line-ending differences when used with the flag "-dl". This is very useful when used in a mixed platform environment. (Bug #4654). #46649 ** 'p4 integ' has an additional option -D, which allows the user to specify whether source or target deleted revisions are okay to integrate around. See 'p4 help integ' for further details. Bugs fixed since 2003.2/51929 (first release). #68583 ** 'p4 changes -m1 ' where the filepath does not exist can cause a scan of the revcx table. This command can now be controlled with the maxscanrows limit, also it is interruptable by the 'p4 monitor terminate' command. (Bug #15421). #68580 ** On some platforms (windows, HP) during high concurrency the server errorlog could contain truncated or incomplete output. This has been fixed (Bug #15356). #62096 ** The performance of //filepath/...@changeno,@changeno declined for some commands in 2003.2. This problem could also cause maxresults or maxscanrows to be exceeded when in prior versions they would not be. This has been fixed (Bug #14588). #61159 ** Under certain circumstances if an error occurred during an internal sort, the server could exit. The error could be due to out-of-memory conditions or maxResults exceeded. This has been fixed (Bug #14550). #59667 ** RCS files could be truncated during sync if the number of lines in the file was greater than 10,000,000. Typically RCS files are smaller and are not the best archive format for very large files (use ctext instead). This limit has however been raised significantly to prevent the truncation. (Bug #14115). #59362 ** Integrating a ktext file to a non-ktext file could result in a bad digest being copied to the target of a lazy copy. The problem would be reported by a subsequent verify command. (Bug #13495). #56802 ** Windows/NT Server performance could degrade over time due to heap memory fragmentation. This change links in a third party memory manager which has shown to not fragment memory and to significantly improve performance on multi-cpu hardware. (Bug #13378). #56585 ** Increase the number of directories that 'p4 dirs' can report about to 100000. (Bug #13803). #54142 * ** Some platforms may exhibit problems setting a password using 'p4 passwd'. This would result in either an error message "Bad parameters passed to mangler!" or that a subsequent passing of the password would be rejected. This has only been observed on OSF (Digital UNIX). (Bug #13427). #53591 ** Using a 2003.1 client (or previous) against a 2003.2 server could result in the server not setting the correct modTime at submit. Subsequent syncs would observe the incorrect time, this has only been reproduced against a 2003.2 server running windows OS. This has been fixed. (Bug #13353). #53371 ** p4 integ -I could report all revisions integrated incorrectly or choose the wrong base for integration when a branch of a common ancester is edited and integrated into the source file. Fixed. (Bug #13115, #13234) #52835 ** The Perforce server could incorrectly report a lack of available memory on the Mac OS X platform. (Bug #13198) #52747 ** 'p4 files //...@labelname' or similar could return incomplete results if some of the files involved were from a remote depot. This has been fixed. (Bug #13162). #52650 ** The @change,change syntax, where change was old, could be slower in 2003.2 than 2003.1. (This syntax is generated by p4win and other programs when integrating by change number.) This has been optimized to be as fast as the new @=change syntax. (Bug #13150). #52585 ** After upgrading to 2003.2 some user passwords may not work anymore. This upgrade process has now been fixed. (Bug #13164) #52474 ** Users without access could create (useless) entries for themselves in the users table, consuming a user license. They can no longer do so. This was new to 2003.2. (Bug #13098) Bugs fixed in 2003.2 #51358 ** 'p4 depots' would include depots where the user had been denied list access. This has been fixed. (Bug #12238) #51351 * 'p4 diff' of an "apple" type file on an non-mac platform would result in the erroneous error "WARNING: AppleSingle/Double corrupted." This has been fixed. (Bug #11023) #51346 * ** Merge resolution could silently accept an insert twice if the two versions being merged both inserted text near another change. Conflicts are now reported. (Bug #12708, #12768) #51293 In certain cases using 'p4d -xf 925' to correct inconsistencies between the db.locks and db.working tables could erroneously delete lock records. This has been fixed (Bug #12694). #50946 NT only - need to perform service pack check after -V option has been processed. If not then the installer can fail. (Bug #12693) #50517 ** An unlikely combination of data might cause database corruption especially during checkpoint recovery. The cause of corruption has been fixed (Bug #12567) #50158 ** On Windows the server might crash if the error log file became locked say during backup or a long copy operation. Now, instead of crashing we silently drop errors if we can not write to the log file. Because of this, administrators should be careful not to lock the error log file for any significant time such as due to leaving an editor open on it. Consider frequent log changes or copying the log file prior to viewing it with an editor. (Bug #12403) #50127 ** RCS files are limited to 2 Gigabytes. However on platforms that have large file support it is possible to write one greater than 2 Gigabytes. A file that is of this size should be stored as compressed text. This change prevents the writing of such a large file and suggests the appropriate file type change. (Bug #11837). #48418 ** p4d -jr (journal and checkpoint recovery) run concurrently with regular server operation might cause database corruption. This is primarily seen with p4jrep. The cause of corruption has been fixed. (Bug #11817). #48343 ** The user password as stored in the db.user table (and logged in the journal) is no longer directly usable as a password on the client. (Bug #11544). #48194 ** 'p4 integrate -I' indirect integration support would sometimes determine the wrong base for integrations and/or report that integrations were not needed or that they were needed when they were not. (Bug #10912, #11831, #12129). #47628 ** 'p4d -xi' which sets the server into i18n mode after checking that the depot contains only UTF-8 conforming metadata did not detect some invalid UTF-8 sequences. This check should now detect more invalid sequences. (Bug #11678). #47518 ** Some platforms could only start the server in "restricted mode" if their designated listening port was greater than 32767. This has been corrected (Bug #11689). #48707 * 'p4 delete' on a file of type "applefile" could terminate with a "Fatal client error" if either the data or resource forks had been manually deleted from the workspace. This problem has been fixed. (Bug #11982). #48448 ** 'p4 submit' could cause the server to crash when trying to submit a file when the user did not have the appropriate permission to do so. (Bug #11920). #46400 * In Unicode mode clients, error and informational messages which have some characters which can not be displayed properly in the character set specified by P4CHARSET will now display the message with the untranslateable characters as '?'. Prior to this change the whole message would not be shown, only a 'no translation' error message. #46044 ** Text files with keyword expansion (ktext, text+k) were not always handled properly when the proxy was in use. This is fixed. A new p4p or p4d is required, but performance is best if both the new p4p and p4d is in use. (Bug 11212). #45941 ** 'p4 verify -q' would compute digests of archive files unnecessarily adding to the time taken in running this command. (Bug 11305). #45574 ** 'p4 obliterate' would halt if it tried to unlink a lazy copy and failed because the archive was already removed. This change causes the server to issue a warning message but continue processing. #45067 ** 'p4 fstat -W' would be slow to return data even if no files were open on the client. The command has now been optimized to make better use of the db.working table as an index. (Bug 9252). -------------------------------------------------------------------------- -------------------------------------------------------------------------- Release 2003.1. Major new functionality in 2003.1 2003.1 includes a number of as yet undocumented internal changes required for versioning and configuring of p4 specs. NEW MONITOR COMMAND DISPLAYS STATUS OF RUNNING P4 PROCESSES - #41063 ** The new 'p4 monitor' command displays the status of current running p4 processes. It is functionally similar to the UNIX 'ps' command. A perforce administrator can also use monitor to terminate long running processes. See 'p4 help monitor' for usage. (Bug #2931, #9889). Minor new functionality in 2003.1 #43840 * ** 'p4 resolve -a' of a binary file where either "yours" or "theirs" has changed from the base now does an automatic "accept theirs/yours", a conflict will still require manual selection. Interactive resolve will now suggest "at/ay" as appropriate. (Bug #5547). #39123 ** The new option 'p4d -c command' runs the command while the database tables are locked. (Bug #9887). #38864 ** 'p4 changes' has an additional option "-t" when specified will display the time as well as the date. (Bug #3224) Bugs fixed since 2003.1/46260 (first release). #48707 * 'p4 delete' on a file of type "applefile" could terminate with a "Fatal client error" if either the data or resource forks had been manually deleted from the workspace. This problem has been fixed. (Bug #11982). #48448 ** 'p4 submit' could cause the server to crash when trying to submit a file when the user did not have the appropriate permission to do so. (Bug #11920). #48379 ** p4d -jr (journal and checkpoint recovery) run concurrently with regular server operation might cause database corruption. This is primarily seen with p4jrep. The cause of corruption has been fixed (Bug #11817) #47686 ** 'p4 add' would ignore the executable bit for applefiles that had '+x' user permissions. This change causes those files to be submitted as 'apple+x' by default. Bugs fixed in 2003.1 #46143 ** 'p4 obliterate' would halt if it tried to unlink a lazy copy and failed because the archive was already removed. This change causes the server to issue a warning message but continue processing. #45952 ** Linux Perforce server was incorrectly reporting out of memory when close to 1GB had been consumed. (Bug #11363). #45779 ** Setting the JobStatus field on a change form would not always propagate the fix status to the included jobs. (Bug #11312). #47686 ** 'p4 add' would ignore the executable bit for applefiles that had '+x' user permissions. This change causes those files to be submitted as 'apple+x' by default. (Bug 11409) #45010 * On Windows/NT a sync "delete" action that tries to unlink a busy file fails to report the error. In addition the db.have table is incorrectly updated as if the delete actual occurred, this has been corrected. (Bug #11068). #44920 ** Some translated error messages that have been stored in perforce in a foreign language were being obscured by in-built English language versions. This has been fixed. (Bug #11173). #44136 * On Windows/NT a manual 'p4 resolve' could result in edits being lost if the target (local file) was busy during a rename operation. This change allows the user to close down the editor or whatever process is holding on to the local file and continue without losing work. (Bug #953). #44444 * ** 'p4 diff -db' or '-dw' could crash if both files ended in identical lines of one space without a trailing newline. This has been fixed. (Bug #11026). #43856 ** 'p4 change -o changelist#' no longer requires a valid client to be able to dump change information. (Bug #10980). #43660 ** The 97.3 (and earlier) p4win can no longer edit any form data against a 2003.1 or later server. This all but obsoletes the 97.3 p4win. #43605 * 'p4 -G job -o' with a custom jobspec that had an invalid preset (usually a value like 'set-me') failed, because the 'p4 -G' support was inadvertantly trying to validate the fields of the blank jobspec. Now 'p4 -G' doesn't validate the fields of the forms being output. #43555 ** 'p4 client' allowed the user to input a single double-quote character into the clientspec 'Root' field. This could lead to corruption of the spec requiring it to be recreated. An error is now raised to prevent this happening. (Bug #10569). #43360 ** 'p4 obliterate' no longer selects all revisions of a file when supplied with #head or #head,#head as its file revision spec. Some other commands that were not obeying #head,#head semantics correctly have also been fixed by this change. (Bug #10883). #43205 ** Access to remote depots was requiring an extra user license to enable the connection on the remote site, this has been fixed. (Bug #2128) #42761 ** The diff algorithm used internally by perforce by the various p4 diff/merge commands has been altered to provide better results when run against large text files (between 10000 and 50000 lines). (Bug #10840) #42269 ** p4d no longer holds the error log file open so that it can be renamed/moved without needing to stop the running p4d. (Bug #606) #42258 ** 'p4 client -d' has now been optimized so that during the removal of client data it no longer blocks other users. (Bug #9519). #41499 ** 'p4 sync' now completes all deletes before adding any files to a client's workspace. By performing the 'sync' in this order the amount of disk space required by the client is kept to a minimum. (Bug #607). #39841 ** 'p4 resolve' and other Perforce merge tools will no longer report as conflicting changes on adjacent lines which do not strictly overlap. This should result in fewer conflicting file merges. (Bug #3811, #7912) #38826 * On Windows/NT clients a failed 'sync' due to a file access issue (e.g. file in use) would leave the file writeable. This would cause a subsequent 'sync' to fail with the message "Can't clobber writeable file ". This has been fixed (Bug #786). #38730 ** Case-insensitive servers (Windows) could inadvertently change the case of certain entity names (e.g. client name) when referenced with a non-matching name. For example the client name 'myclient' could be changed to 'MYclient' with the following command 'p4 files ...@MYclient'. This has been fixed (Bug #9566). #38395 ** Previously installations that did not create a depot "depot" would still get a viewspec entry for one each time they created a new client. Now new installations will come initialized with this default depot which can be deleted if not required. Upgraded installations will have an entry created if necessary (i.e. there are "//depot" entries already in existence). If the installation has no reference to any "//depot" file then the depot "depot" will no longer appear in client specifications. (Bug #5960) -------------------------------------------------------------------------- -------------------------------------------------------------------------- Release 2002.2. Major new functionality in 2002.2 INTEGRATE ACROSS DISTANT BRANCHES - #35537 ** 'p4 integrate' now fully handles merging changes between branches that don't have a direct parent/child relationship. This occurs often when, say, both a release line and a development line are branched from a main line and changes must be merged directly from the development line to the release line. Previously, users had to rely on instructions in technical note #9 to ensure that the Perforce server chose the right base revision for merging. Now an updated option to 'p4 integrate' does the work. The '-I' option looks for "indirect" integration history through intermediate files when determining the base for merging. This makes it able to handle files distantly related by branching, not just those with a direct parent/child relationship. The new branch option 'indirect' implies 'p4 integrate -I' for the branch, so that it need not be passed on the command line. While it is harmless to use the '-I' flag for directly related branches, it is slower. See 'p4 help integrate' and 'p4 help resolve' for updated descriptions of their operation. (Bug #413, #9323). NEW ANNOTATE COMMAND SHOWS HISTORY OF LINES IN A FILE - #35149 ** The new 'p4 annotate' command displays the lines of a file along with the number of the revision that introduced each line. It is functionally similar to the CVS annotate command, except that it has the option to show deleted lines and note both the revision of introduction and deletion. See 'p4 help annotate' for usage. (Bug #574). SHARING CLIENTS USING MULTIPLE CLIENT ROOTS - #34879 ** Client workspaces that are shared across multiple platforms can now be better accomodated by the ability to specify multiple client roots. If the same workspace is accessed from different hosts, the same set of client workspace files can appear with a different root directory. Previously, only one root could be given in the client spec, and the user had to change it manually as he moved among platforms. Now 'p4 client' supports up to three (3) client roots, one main (named "Root") and two alternates (named "AltRoots" ). The client's current working directory is tried against all three, and the first one that matches is used. If none match, the main is used anyhow. 'p4 info' reports the applicable root. This support allows for client roots shared via multiple UNIX paths with symlinks, shared via NFS or Windows shares, or even between MacOS Classic and MacOS X. When used with the 'p4 client' LineEnd 'share' option, client workspaces can be effectively shared between UNIX and Windows. See 'p4 help client' for details on using multiple client roots. (Bug #4471, #6200, #6243, #6275, #6521, #7268) SPRUCING UP DIFFS The various commands that diff files have seen some enhancements to make them more compatible with the GNU diff and patch programs. Ignoring whitespace - #31144, #31078 * ** 'p4 diff', 'p4 diff2', 'p4 describe', and 'p4 resolve' now can ignore whitespace changes, as the GNU diff does. The -db flag ignores changes in horizontal whitespace, and the -dw flag ignores horizontal whitespace altogether. 'p4 resolve' also passes the flags to the diff option in resolve dialog. Note that 'p4 resolve' will use text from the client (aka "yours") file where the files differ only in whitespace. 'p4 diff' requires a p4 client upgrade; 'p4 diff2' and 'p4 describe' require a p4d server upgrade. 'p4 resolve' rquires both. (Bug #879, #1671, #1932). Patch-friendly output - #35143 ** 'p4 diff2 -u', which produces more patch-friendly output, is now supported. It has long been present but undocumented. (Bug #380). TEMPOBJ FILETYPE REDUX - #36061 ** The 'tempobj' filetype, which stores only the head revision of the file (to conserve space), has been reimplemented to remove some of the serious problems associated with using this filetype. It is now safe to use. Previously, the server knew there were multiple revisions but they all shared the same text. This created problems with 'p4 submit' (aborted submits would update the text anyhow), 'p4 verify' (the revision fingerprint would change), 'p4 sync' (syncing a non-head rev would still give the head rev's text), and 'p4 obliterate' (obliterating the non head rev would remove the head rev's text). Now the server associates text with each revision (just as with non-tempobj files) and goes through the extra step of purging the previous revision during 'p4 submit'. 'p4 filelog' will display non-head revisions as 'purged' and they are treated like a deleted revision: 'p4 sync' will remove the file on the client and 'p4 verify' will ignore them. With this change, the filetype modifier "+S" changes from a storage type (uncompressed binary with only the head rev stored) to a storage modifier (purge non-head revs). Any type of file (text, binary, compressed) may now take on the "+S" modifier. The filetype modifier "+M", which previously indicated compressed binary with only the head rev stored, has been supplanted by +S's new meaning. This table might make it clearer: keyword pre-2002.2 2002.2 -------- ---------- ----------- tempobj binary+Sw binary+FSw xtempobj binary+Swx binary+FSwx ctempobj binary+Mw binary+Sw +F = uncompressed +S = binary head-rev only (pre-2002.2) +S = purge non-head-revs (2002.2) +M = compressed binary head-rev only (pre-2002.2) +w = client file always writable (all tempobjs) +x = executable bit set on client The 2002.2 server will upgrade existing tempobj files to the new. This requires a database upgrade with 'p4d -xu'. (Bug #1025, #2642, #3888, #7775). NEW PROTECTION LEVEL FOR SEMI-SUPER USERS - #35832 ** A new 'p4 protect' level 'admin' has been introduced below 'super' to permit many administrative commands without granting total superuser access. The commands now requiring only 'admin' access are: p4 branch -f p4 change -f p4 client -f p4 job -f p4 jobspec p4 label -f p4 obliterate p4 typemap p4 unlock -f p4 verify The commands still requiring 'super' access are: p4 admin p4 counter -f p4 depot p4 group p4 jobs -R p4 passwd user p4 protect p4 triggers p4 user -f (Bug #3037, #1306, #2842, #3520, #5004. This change only tangentially addresses some of these bugs.) Minor new functionality in 2002.2 #36081 ** "p4 resolve" now writes its messages through the methods of the ClientUser class rather than directly to stdout to allow API users to capture and parse the output. This change is only relevant to API users. (Bug #6881.) #35972 ** 'p4 resolve' now recognizes if the resulting file has been edited to match either 'yours', 'theirs', or the automatically merged result, and changes its default suggested action appropriately. In this way, if an external merge tool produces exactly 'theirs' then 'p4 resolve' can still arrange for a lazy copy in the server. #35391 ** 'p4 describe' of a pending changelist now includes the affected files. This fixes our oldest open bug. (Bug #13, #4974). #35390 ** The new option 'p4 revert -n' just displays which files would be reverted without actually reverting them. #35368 ** Long running operations that have been cancelled by the client can now be detected and terminated in the server. This feature may not be available on all platforms. (Bug #409). #35145 ** The new options 'p4 files -a' and 'p4 print -a' display all revisions in a revision range, rather than just the highest revision. #35114 ** 'p4 filelog' has an additional option "-t" when specified will display the time as well as the date. (Bug #553). #35063 * Adding support for Mac OS Roman character set in i18n mode. To use, set P4CHARSET to "macosroman". #34972 ** p4 info now displays the offset from UTC of the server timezone numerically and with a symbol if the symbol supplied from the OS is ASCII. (Bug #9359). Bugs fixed since 2002.2/39491 (first release). #43923 ** The proxy's RCS based cache files could be corrupted if concurrent updates to that RCS file occurred due to multiple clients requesting a revision from that file. Fixed. Related, the executable bit will no longer be set on RCS files. Also related, RCS anomolies if one client is used concurrently by multiple processes to submit the same file. (Bug #6054 & #10512) #42711 ** A 3 way merge during a resolve of large files (>20000 lines) could cause the server to crash, this has been fixed. (Bug #10835). #42453 ** Prior to 2002.2 there was a bug that under certain conditions allowed a lazy copy of a tempobj archive file. In 2002.2 the new tempobj implementation purges old copies (,t) files replacing them with the appropriate base type. A 2002.2 user can run into a problem if they try and access one of the branched files that have (since 2002.2 upgrade) had the base file for the lazy copy purged. This fix prevents old tempobj files (,t) from being removed during a submit although they will still be marked as "purged" in the rev table. When trying to access a file that had been purged as previously stated the user would receive an error something like this: Librarian checkout depot/branch/foo.c failed. open for read: depot/branch/foo.c,t: The system cannot find the file specified Even if this fix has been applied it is still possible to get the above error message if the base file was purged before this version was installed (in a previous 2002.2 release). If this happens the file can be manually fixed up, for help on this please contact technical support. (Bug #10581). #41819 ** Due to the sometimes significant overhead of indirect integration, 'p4 integ -i' has been reverted to its previous use of just allowing baseless merges. A new option 'p4 integ -I' is required to use the new 2002.2 feature to find intermediate files when determining a base. (Bug #10587). #41516 ** 'p4 print -o' through the proxy might fail silently depending on network timing. Fixed. (Bugs #10491, #10511, #10574) #41173 ** 'p4 verify' could crash the server if it ran out of available memory. (Bug #10468). #41169 ** Long running operations that have been cancelled by clients running on NT were not detected on an NT server. Fixed (Bug #10465). #41147 ** 'p4 sync' through the proxy was not honoring a client's 'allwrite' option if files were delivered from the proxy. Fixed. (Bug #10398) #40318 * 'p4 revert' of a file with the client option "modTime" set under certain circumstances could lead to the error: ("utime: filepath: Access is denied.") This problem has been fixed. (Bug #10202). #40313 * 'p4 resolve' when prompted for a "confirm accept (y/n)" would incorrectly throw up two messages if the user answered in the negative "n". This would be very confusing and has been fixed (Bug #10212). #40216 ** Certain p4 commands with a "filepath@label" argument could cause a unnecessary scan of the label table. This would occur if the filepath supplied did not contain any file revisions. This problem has been fixed. (Bug #10204). #40122 ** Trying to integrate from the new tempobj type would result in the incorrect warning message "can't branch without -d flag". This problem has been fixed. (Bug #10166). #39934 ** On NT servers, under certain conditions an internal file rename operation could fail. A retry has been added to this part of the code and extra diagnostics have been enabled to log relevant information in an attempt to track down this problem. Bugs fixed in 2002.2 #38452 ** p4d sometimes core dumped on shutdown on hpux11 PA-RISC machines. This has been fixed. (Bug #9641) #38559 * The "share" client line-end option has been extended to include support for Mac files that use linefeeds as their line terminator. (Bug #9068). #37237 ** p4d -xv and p4d -xr did not recongnize or correct btree corruption where a btree page's first few bytes had been corrupted. This case should now be handled properly. (Bug #9501). #37746 ** 'p4 integrate -i' was "giving credit" for indirect integrations that hadn't necessarily affected the target file, suppressing proper integrations from happening. This has been fixed. (Bug #9573). #37236 * Client programs running in timezones east of GMT sometimes miscalculated their GMT offset, resulting in incorrect modtimes on submitted and sync files. This has been corrected. This fix does not attempt to fix the modtimes of files previously submitted with the wrong modtime. (Bug #9503). #36747 * Clients on OSF incorrectly offset file modtimes by one day: submits were one day into the future and syncs would be one day into the past. This problem would only become evident if you also operated with other, non-OSF clients. The OSF clients now set file modtimes correctly. (Bug #9212). #36584 * On Cygwin the p4 client program would exit (quickly) if the 'rmdir' client option was set when a file was removed from the current directory (either through 'p4 sync' or 'p4 delete'). This has been corrected with an internal workaround. (Bug #7478, #7543). #36150 * 'p4 revert -a' wasn't resetting the modification time for a file when the client had the option 'modtime' set. This has been fixed. (Bug #8978). #35946 ** 'p4 obliterate -z' without the '-y' (make the changes) now only reports what it would do. It used say it was in report mode, but then actually undo lazy copies. Now '-y' is required for 'p4 obliterate -z' to take effect. (Bug #3613). #35869 ** 'p4 diff2 @label1 @label2' would issue a bogus error message ("RelateMap has empty maps!"). This has been fixed. (Bug #1382). #35829 ** Some server errors that occur before protocol initialization (like being unable to open the database) could result in a bogus error message ("Required parameter 'func' not set!") sent to the client. This has been fixed. (Bug #8110). #35799 ** Using p4d -xi to enable I18N mode would sometimes incorrectly fail reporting non-UTF8 data in either the db.job or db.change table. This has been corrected. (Bug #9011). #35738 ** 'p4 changes -s pending' is not compatible with a file argument as it will always return no data (since only submitted change information is available in the rev table). Supplying a file argument has now been disallowed to avoid any confusion. (Bug #371). #35403 ** 'p4 job -f' would not allow an update of read-only "once" fields. This has been corrected. (Bug #5938, #8111). #35274 ** To speed p4win, performance of 'p4 changes -m1 filepath' has been specially optimized. This only speeds this exact command: filepaths including @client and @label will not be affected by this change. (Bug #7306). #34362 ** The internal support for optimizing p4win's performance against large servers (see #29329 below) sometimes didn't work with the case-insensitive (Windows) Perforce server. This has been corrected. (Bug #8404). #34284 ** 'p4 edit ' where the number of files is greater than the value set for "maxscanrows" would result in an incorrect error message being returned. This has been corrected. (Bug #7837). #34069 ** A new error message indicates attempted access by a user not enabled at all via 'p4 protect'. Previously, it was not possible to tell if a user had no access at all or just no access for the requested command. #33552 ** 'p4 filelog @