pkgsrc/devel/scmcvs/patches/patch-ao

23 lines
566 B
Text
Raw Normal View History

$NetBSD: patch-ao,v 1.1 2007/05/27 09:49:53 schmonz Exp $
Update to 1.11.21: Changes since 1.11.20: ********************** BUG FIXES * Thanks to Serguei E. Leontiev, CVS with Kerberos 5 GSSAPI should automatically link on FreeBSD 5.x. (bug #14639). * Thanks to Rahul Bhargava, heavily loaded systems suffering from a disk crash or power failure will not lose data they claimed to have committed. * CVS server now handles conflict markers in Entry requests as documented. * CVS now remembers that binary file merge conflicts occurred until the timestamp of the updated binary file changes. * CVS client now saves some bandwidth by not sending the contents of files with conflicts to the server when it isn't needed. * CVS now does correct locking during import. * A problem where the server could block indefinitely waiting for an EOF from the client when compression was enabled has been fixed. * `cvs diff' no longer splits its arguments on spaces. * Thanks to an old report and patch from Stewart Brodie, a potential crash in response to a corrupt RCS file has been fixed. * CVS now locks the history and val-tags files before writing to them. Especially with large repositories, users should no longer see new warnings about corrupt history records when using the `cvs history' command. Existing corrupt history records will still need to be removed manually. val-tags corruption should have had less obvious effects, but removing the CVSROOT/val-tags file and allowing a 1.11.21 or later version of CVS to regenerate it may eliminate a few odd behaviors and possibly cause a slight speed up of read transactions in large repositories over time.
2006-01-29 03:40:40 +01:00
--- src/lock.c.orig 2005-05-03 17:34:53.000000000 +0200
Update to 1.11. Changes since 1.10: * The new "cvs version" command gives a short version message. If the repository is remote, both the client and server versions are reported. * "cvs admin -t" now works correctly in client/server mode. * The "cvs history" command output format has changed -- the date now includes the year and is given is ISO 8601 format (yyyy-mm-dd). Also, the new LogHistory option in CVSROOT/config can be used to control what information gets recorded in the log file and code has been added to record file removals. * The buggy PreservePermissions code has been disabled. * Anonymous read-only access can now be done without requiring a password. On the server side, simply give that user (presumably `anonymous') an empty password in the CVSROOT/passwd file, and then any received password will authenticate successfully. * There is a new access method :fork: which is similar to :local: except that it is implemented via the CVS remote protocol, and thus has a somewhat different set of quirks and bugs. * The -d command line option no longer updates the CVS/Root file. For one thing, the CVS 1.9/1.10 behavior never had updated CVS/Root in subdirectories, and for another, it didn't seem that popular in general. So this change restores the CVS 1.8 behavior (which is also the CVS 1.9/1.10 behavior if the environment variable CVS_IGNORE_REMOTE_ROOT is set; with this change, CVS_IGNORE_REMOTE_ROOT no longer has any effect). * It is now possible for a single CVS command to recurse into several CVS roots. This includes roots which are located on several servers, or which are both remote and local. CVS will make connections to as many servers as necessary. * It is now possible to put the CVS lock files in a directory set by the new LockDir option in CVSROOT/config. The default continues to be to put the lock files in the repository itself.
2000-10-18 05:31:15 +02:00
+++ src/lock.c
Update to 1.11.21: Changes since 1.11.20: ********************** BUG FIXES * Thanks to Serguei E. Leontiev, CVS with Kerberos 5 GSSAPI should automatically link on FreeBSD 5.x. (bug #14639). * Thanks to Rahul Bhargava, heavily loaded systems suffering from a disk crash or power failure will not lose data they claimed to have committed. * CVS server now handles conflict markers in Entry requests as documented. * CVS now remembers that binary file merge conflicts occurred until the timestamp of the updated binary file changes. * CVS client now saves some bandwidth by not sending the contents of files with conflicts to the server when it isn't needed. * CVS now does correct locking during import. * A problem where the server could block indefinitely waiting for an EOF from the client when compression was enabled has been fixed. * `cvs diff' no longer splits its arguments on spaces. * Thanks to an old report and patch from Stewart Brodie, a potential crash in response to a corrupt RCS file has been fixed. * CVS now locks the history and val-tags files before writing to them. Especially with large repositories, users should no longer see new warnings about corrupt history records when using the `cvs history' command. Existing corrupt history records will still need to be removed manually. val-tags corruption should have had less obvious effects, but removing the CVSROOT/val-tags file and allowing a 1.11.21 or later version of CVS to regenerate it may eliminate a few odd behaviors and possibly cause a slight speed up of read transactions in large repositories over time.
2006-01-29 03:40:40 +01:00
@@ -420,7 +420,7 @@ Reader_Lock (xrepository)
Update cvs to 1.11.2. Changes: Changes since 1.11.1p1: * The "log" and "rlog" commands now have a -S option to suppress the header information when no revisions are selected. * A serious error that allowed read-only users to tag files has been corrected. * The "annotate" command will no longer annotate binary files unless you specify the new -F option. * The "tag" and "rtag" commands will no longer move or delete branch tags unless you use the new -B option. (This prevents accidental changes to branch tags that are hard to undo.) * We've standardized on the 1.5 Automake release for the moment. Again, this should only really affect developers. See the section of the INSTALL file about using the autotools if you are compiling CVS yourself. Changes from 1.11.1 to 1.11.1p1: * Read only access was broken - now fixed. Changes from 1.11 to 1.11.1: * The "cvs diff" command now accepts the -y/--side=by-side and -T/ --initial-tab options. (To use these options with a remote repository, both the client and the server must support them.) * The expansion of the loginfo format string has changed slightly. Previously, the expansion was surrounded by single quotes ('); if a file name contained a single quote character, the string would not be parsed as a single entity by the Unix shell (and it would not be possible to parse it unambiguously). Now the expansion is surrounded by double quotes (") and any embedded dollar signs ($), backticks (`), backslashes (\), and double quotes are preceded by a backslash. This is parsed as a single entity by the shell reguardless of content. This change should not be noticable unless you're not using a Unix shell or you have embedded the format string inside a double quoted string. * There was a bug in the diff code which sometimes caused conflicts to be flagged which shouldn't have been. This has been fixed. * New "cvs rlog" and "cvs rannotate" commands have been added to get log messages and annotations without having to have a checked-out copy. * Exclusive revision ranges have been added to "cvs log" using :: (similar to "cvs admin -o"). * The VMS client now accepts wildcards if you're running VMS 7.x. * ZLIB has been updated to version 1.1.3, the most current version. This includes mostly some optimizations and minor bug fixes. * The ~/.cvspass file has a slightly modified format. CVSROOTs are now stored in a new canonical form - hostnames are now case insensitive and port numbers are always stored in the new format. Until a new login for a particular CVSROOT is performed with the new version of CVS, new and old versions of CVS should interoperate invisibly. After that point, an extra login using the old version of CVS may be necessary to continue to allow the new and old versions of CVS to interoperate using the same ~/.cvspass file and CVSROOT. The exception to this rule occurs when the CVSROOTs used with the different versions use case insensitively different hostnames, for example, "empress", and "empress.2-wit.com". * A password and a port number may now be specified in CVSROOT for pserver connections. The new format is: :pserver:[[user][:password]@]host[:[port]]/path Note that passwords specified in a checkout command will be saved in the clear in the CVS/Root file in each created directory, so this is not recommended, except perhaps when accessing anonymous repositories or the like. * The distribution has been converted to use Automake. This shouldn't affect most users except to ease some portability concerns, but if you are building from the repository and encounter problems with the makefiles, you might try running ./noautomake.sh after a fresh update -AC.
2002-11-24 22:31:20 +01:00
(void) fprintf (stderr, "%s-> Reader_Lock(%s)\n", CLIENT_SERVER_STR,
xrepository);
- if (noexec)
+ if (nolock)
Update to 1.11.15 (security update): Changes since 1.11.14: ********************** SERVER SECURITY ISSUES * Piped checkouts of paths above $CVSROOT no longer work. Previously, clients could have requested the contents of RCS archive files anywhere on a CVS server. CLIENT SECURITY ISSUES * Clients now check paths from the server to verify that they are within one of the sandboxes the user requested be updated. Previously, a trojan server could have written or overwritten files anywhere the user had access, presenting a serious security risk. GENERAL USER ISSUES * Method options (used by WinCVS & CVS 1.12.7+) in CVSROOTs are ignored. * Configure no longer checks the $TMPDIR, $TMP, & $TEMP variables to set the default temporary directory. * CVS on Cygwin correctly handles X:\ style paths. * Import now uses backslash rather than slash on Windows when checking for "CVS" directories to ignore in import commands. * Relative paths containing up-references (`..') should now work in client/server mode (client fix). * A race condition between the ordering of messages from CVS and messages from called scripts in client/server mode has been removed (server fix). * Resurrected files now get their modes and timestamps set correctly and a longstanding bug involving resurrection of an uncommitted removal has been fixed (server fix). * Some resurrection (cvs add) status messages have changed slightly. * `cvs release' now works with Kerberos or GSSAPI encryption enabled (server fix). * File resurrection from a previously existing revision no longer just reports that it works (server fix). * Misc error & status message corrections. * Diffing of locally added files against arbitrary revisions in an RCS archive is now allowed when a file of the same name exists or used to exist on some branch (server fix). * Misc documentation fixes. Changes from 1.11.13 to 1.11.14: ******************************** GENERAL USER ISSUES * Imports will now always ignore directories and files named `CVS' to avoid violating assumptions made by other parts of CVS. * A problem with `cvs release' of subdirs that could corrupt CVS/Entries files has been fixed (client/server). * The CVS server's protocol check for unused data from the client is no longer called automatically at program exit in order to avoid potential recursive calls to error when the first close is due to memory allocation or similar problems that cause calls to error() to fail. The check is still made when the server program exits normally. * The spec file has been updated to work with more recent versions of RPM. * Several memory leaks have been plugged (client/server). DEVELOPER ISSUES * Misc cosmetic, readability, and commenting fixes.
2004-04-16 00:28:36 +02:00
return 0;
/* we only do one directory at a time for read locks! */
Update to 1.11.21: Changes since 1.11.20: ********************** BUG FIXES * Thanks to Serguei E. Leontiev, CVS with Kerberos 5 GSSAPI should automatically link on FreeBSD 5.x. (bug #14639). * Thanks to Rahul Bhargava, heavily loaded systems suffering from a disk crash or power failure will not lose data they claimed to have committed. * CVS server now handles conflict markers in Entry requests as documented. * CVS now remembers that binary file merge conflicts occurred until the timestamp of the updated binary file changes. * CVS client now saves some bandwidth by not sending the contents of files with conflicts to the server when it isn't needed. * CVS now does correct locking during import. * A problem where the server could block indefinitely waiting for an EOF from the client when compression was enabled has been fixed. * `cvs diff' no longer splits its arguments on spaces. * Thanks to an old report and patch from Stewart Brodie, a potential crash in response to a corrupt RCS file has been fixed. * CVS now locks the history and val-tags files before writing to them. Especially with large repositories, users should no longer see new warnings about corrupt history records when using the `cvs history' command. Existing corrupt history records will still need to be removed manually. val-tags corruption should have had less obvious effects, but removing the CVSROOT/val-tags file and allowing a 1.11.21 or later version of CVS to regenerate it may eliminate a few odd behaviors and possibly cause a slight speed up of read transactions in large repositories over time.
2006-01-29 03:40:40 +01:00
@@ -494,7 +494,7 @@ Writer_Lock (list)
{
char *wait_repos;
- if (noexec)
+ if (nolock)
Update to 1.11.15 (security update): Changes since 1.11.14: ********************** SERVER SECURITY ISSUES * Piped checkouts of paths above $CVSROOT no longer work. Previously, clients could have requested the contents of RCS archive files anywhere on a CVS server. CLIENT SECURITY ISSUES * Clients now check paths from the server to verify that they are within one of the sandboxes the user requested be updated. Previously, a trojan server could have written or overwritten files anywhere the user had access, presenting a serious security risk. GENERAL USER ISSUES * Method options (used by WinCVS & CVS 1.12.7+) in CVSROOTs are ignored. * Configure no longer checks the $TMPDIR, $TMP, & $TEMP variables to set the default temporary directory. * CVS on Cygwin correctly handles X:\ style paths. * Import now uses backslash rather than slash on Windows when checking for "CVS" directories to ignore in import commands. * Relative paths containing up-references (`..') should now work in client/server mode (client fix). * A race condition between the ordering of messages from CVS and messages from called scripts in client/server mode has been removed (server fix). * Resurrected files now get their modes and timestamps set correctly and a longstanding bug involving resurrection of an uncommitted removal has been fixed (server fix). * Some resurrection (cvs add) status messages have changed slightly. * `cvs release' now works with Kerberos or GSSAPI encryption enabled (server fix). * File resurrection from a previously existing revision no longer just reports that it works (server fix). * Misc error & status message corrections. * Diffing of locally added files against arbitrary revisions in an RCS archive is now allowed when a file of the same name exists or used to exist on some branch (server fix). * Misc documentation fixes. Changes from 1.11.13 to 1.11.14: ******************************** GENERAL USER ISSUES * Imports will now always ignore directories and files named `CVS' to avoid violating assumptions made by other parts of CVS. * A problem with `cvs release' of subdirs that could corrupt CVS/Entries files has been fixed (client/server). * The CVS server's protocol check for unused data from the client is no longer called automatically at program exit in order to avoid potential recursive calls to error when the first close is due to memory allocation or similar problems that cause calls to error() to fail. The check is still made when the server program exits normally. * The spec file has been updated to work with more recent versions of RPM. * Several memory leaks have been plugged (client/server). DEVELOPER ISSUES * Misc cosmetic, readability, and commenting fixes.
2004-04-16 00:28:36 +02:00
return 0;
/* We only know how to do one list at a time */