head 1.9; access; symbols pkgsrc-2013Q2:1.9.0.26 pkgsrc-2013Q2-base:1.9 pkgsrc-2012Q4:1.9.0.24 pkgsrc-2012Q4-base:1.9 pkgsrc-2011Q4:1.9.0.22 pkgsrc-2011Q4-base:1.9 pkgsrc-2011Q2:1.9.0.20 pkgsrc-2011Q2-base:1.9 pkgsrc-2009Q4:1.9.0.18 pkgsrc-2009Q4-base:1.9 pkgsrc-2008Q4:1.9.0.16 pkgsrc-2008Q4-base:1.9 pkgsrc-2008Q3:1.9.0.14 pkgsrc-2008Q3-base:1.9 cube-native-xorg:1.9.0.12 cube-native-xorg-base:1.9 pkgsrc-2008Q2:1.9.0.10 pkgsrc-2008Q2-base:1.9 pkgsrc-2008Q1:1.9.0.8 pkgsrc-2008Q1-base:1.9 pkgsrc-2007Q4:1.9.0.6 pkgsrc-2007Q4-base:1.9 pkgsrc-2007Q3:1.9.0.4 pkgsrc-2007Q3-base:1.9 pkgsrc-2007Q2:1.9.0.2 pkgsrc-2007Q2-base:1.9 pkgsrc-2007Q1:1.8.0.10 pkgsrc-2007Q1-base:1.8 pkgsrc-2006Q4:1.8.0.8 pkgsrc-2006Q4-base:1.8 pkgsrc-2006Q3:1.8.0.6 pkgsrc-2006Q3-base:1.8 pkgsrc-2006Q2:1.8.0.4 pkgsrc-2006Q2-base:1.8 pkgsrc-2006Q1:1.8.0.2 pkgsrc-2006Q1-base:1.8 pkgsrc-2005Q4:1.7.0.8 pkgsrc-2005Q4-base:1.7 pkgsrc-2005Q3:1.7.0.6 pkgsrc-2005Q3-base:1.7 pkgsrc-2005Q2:1.7.0.4 pkgsrc-2005Q2-base:1.7 pkgsrc-2005Q1:1.7.0.2 pkgsrc-2005Q1-base:1.7 pkgsrc-2004Q4:1.6.0.6 pkgsrc-2004Q4-base:1.6 pkgsrc-2004Q3:1.6.0.4 pkgsrc-2004Q3-base:1.6 pkgsrc-2004Q2:1.6.0.2 pkgsrc-2004Q2-base:1.6 pkgsrc-2004Q1:1.5.0.2 pkgsrc-2004Q1-base:1.5 pkgsrc-2003Q4:1.4.0.2 pkgsrc-2003Q4-base:1.4 netbsd-1-6-1:1.3.0.2 netbsd-1-6-1-base:1.3 netbsd-1-6:1.2.0.8 netbsd-1-6-RELEASE-base:1.2 pkgviews:1.2.0.4 pkgviews-base:1.2 buildlink2:1.2.0.2 buildlink2-base:1.2 netbsd-1-5-PATCH003:1.2 netbsd-1-5-PATCH001:1.2 netbsd-1-5-RELEASE:1.1 netbsd-1-4-PATCH003:1.1 netbsd-1-4-PATCH002:1.1 comdex-fall-1999:1.1 netbsd-1-4-PATCH001:1.1 netbsd-1-4-RELEASE:1.1; locks; strict; comment @# @; 1.9 date 2007.05.27.09.49.47; author schmonz; state dead; branches; next 1.8; 1.8 date 2006.01.29.02.40.40; author wiz; state Exp; branches; next 1.7; 1.7 date 2005.03.01.15.36.48; author wiz; state Exp; branches; next 1.6; 1.6 date 2004.04.15.22.28.36; author wiz; state Exp; branches; next 1.5; 1.5 date 2003.12.12.22.05.56; author wiz; state Exp; branches; next 1.4; 1.4 date 2003.07.12.09.19.19; author wiz; state Exp; branches; next 1.3; 1.3 date 2002.11.24.21.31.24; author hubertf; state Exp; branches; next 1.2; 1.2 date 2000.10.18.03.31.16; author hubertf; state Exp; branches; next 1.1; 1.1 date 99.04.20.15.01.11; author mycroft; state Exp; branches; next ; desc @@ 1.9 log @Move cvs to scmcvs so it can be checked out on a case-insensitive filesystem without interference from devel/CVS metadata. PKGNAME stays the same. Discussed with agc. @ text @$NetBSD: patch-ao,v 1.8 2006/01/29 02:40:40 wiz Exp $ --- src/lock.c.orig 2005-05-03 17:34:53.000000000 +0200 +++ src/lock.c @@@@ -420,7 +420,7 @@@@ Reader_Lock (xrepository) (void) fprintf (stderr, "%s-> Reader_Lock(%s)\n", CLIENT_SERVER_STR, xrepository); - if (noexec) + if (nolock) return 0; /* we only do one directory at a time for read locks! */ @@@@ -494,7 +494,7 @@@@ Writer_Lock (list) { char *wait_repos; - if (noexec) + if (nolock) return 0; /* We only know how to do one list at a time */ @ 1.8 log @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. @ text @d1 1 a1 1 $NetBSD: patch-ao,v 1.7 2005/03/01 15:36:48 wiz Exp $ @ 1.7 log @Update to 1.11.19. pkgsrc change: patch-ag, provided by Georg Schwarz, added to fix the build on IRIX. NEWS: Changes since 1.11.18: ********************** BUG FIXES * An intermittant assertion failure in checkout has been fixed. * Thanks to a report from Chris Bohn, all the source files needed for the Windows "red file" fix are actually included in the distribution. * Misc bug and documentation fixes. Changes from 1.11.17 to 1.11.18: ******************************** BUG FIXES * Thanks to a report from Gottfried Ganssauge, CVS no longer exits when it encounters links pointing to paths containing more than 128 characters. * Thanks to a report from Dan Peterson, error messages from GSSAPI servers are no longer truncated. * Thanks to a report from Dan Peterson, attempts to resurrect a file on the trunk that was added on a branch no longer causes an assertion failure. * Thanks to a report from Dan Peterson, imports to branches like "1.1." no longer create corrupt RCS archives. * Thanks to a report from Chris Bohn, links from J.C. Hamlin, and code posted by Jonathan Gilligan, we think we have finally corrected the Windows "red-file" (daylight savings time) bug once and for all. * Thanks to a patch from Jeroen Ruigrok/asmodai, the log_accum.pl script should no longer elicit warnings from Perl 5.8.5. * The r* commands (rlog, rls, etc.) can once again handle requests to run against the entire repository (e.g. `cvs rlog .'). Thanks go to Dan Peterson for the report. * A problem where the attempted access of files via tags beginning with spaces could cause the CVS server to hang has been fixed. This was a particular problem with WinCVS clients because users would sometimes accidentally include spaces in tags pasted into a dialog box. This fix also altered some of the error messages generated by the use of invalid tags. Thanks go to Dan Peterson for the report. * Thanks to James E Wilson for a bug fix to modules processing "gcc-core -a !gcc/f gcc" will no longer exclude gcc/fortran by mistake. * Thanks to Conrad Pino, the Windows build works once again. * Misc updates to the manual. DEVELOPER ISSUES * We've standardized on Automake 1.9.3 to get some at new features that make our jobs easier. See the note below on the Autoconf upgrade for more details. * We've standardized on Autoconf version 2.59 to get presumed bug fixes and features, but nothing specific. Mostly, once we decide to upgrade one of the autotools we just figure it'll save time later to grab the most current versions of the others too. See the HACKING file for more on using the autotools with CVS. @ text @d1 1 a1 1 $NetBSD: patch-ao,v 1.6 2004/04/15 22:28:36 wiz Exp $ d3 1 a3 1 --- src/lock.c.orig 2005-01-31 23:13:07.000000000 +0100 d5 1 a5 1 @@@@ -412,7 +412,7 @@@@ Reader_Lock (xrepository) d14 1 a14 1 @@@@ -486,7 +486,7 @@@@ Writer_Lock (list) @ 1.6 log @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. @ text @d1 1 a1 1 $NetBSD$ d3 1 a3 1 --- src/lock.c.orig Thu Apr 1 23:25:57 2004 d5 1 a5 1 @@@@ -407,7 +407,7 @@@@ Reader_Lock (xrepository) d14 1 a14 1 @@@@ -481,7 +481,7 @@@@ Writer_Lock (list) @ 1.5 log @Update to 1.11.10: Changes since 1.11.9: ********************* SERVER SECURITY ISSUES * Malformed module requests could cause the CVS server to attempt to create directories and possibly files at the root of the filesystem holding the CVS repository. Filesystem permissions usually prevent the creation of these misplaced directories, but nevertheless, the CVS server now rejects the malformed requests. GENERAL USER ISSUES * Case insensitive clients using a case sensitive server can now use a `cvs rm -f file; cvs add FILE' command sequence to add a file with the same name in a new case. * CVSROOTs which contain a symlink to a real repository should work. * The configure script now tests whether it is building CVS on a case insensitive file system. If it is, CVS assumes that all file systems on this platform will be case insensitive. This is useful for getting the case insensitivity flag set correctly when compiling on Mac OS X and under Cygwin on Windows. Autodetection can be overridden using the --disable-case-sensitivity and --enable-case-sensitivity arguments to configure. * A behavior change in `cvs up -jrev1 -jrev2' for modified files with a base revision of rev2 (ie, checked-out version matches rev2 and file has been modified). The operation is no longer ignored and instead is passed to diff3. This will potentially re-apply the diffs between the two revisions to a modified local file. Status messages like from a standard merge have also been added when the file would not or does not change due to this merge request ("[file] already contains the changes between [revisions]..."). * A bug which could stop `cvs admin -mTAG:message' from recursing has been fixed. * Misc documentation cleanup and fixes. * Some of the contrib scripts, some of the documentation, and sanity.sh were modified to use and recommend more portable commands rather than using and recommending commands which were not compatible with the POSIX 1003.1-2001 specification. DEVELOPER ISSUES * A new set of tests to test issues specific to case insensitive clients and servers has also been added. * Support has been added to the test suite to support testing over a :ext: link to another machine, subject to some stringent requirements. This support can be used, for instance, to test the operation of a case insensitive client against a case sensitive server. Please see the comments in TEST and the src/sanity.sh test script itself for more. * We've standardized on Automake 1.7.9 to get a bug fix. See the note below on the Autoconf upgrade for more details. * We've standardized on Autoconf version 2.58 to avoid a bug and get at a few new macros. Again, this should only really affect developers, though it is possible that CVS will now compile on a few new platforms. Please see the section of the INSTALL file about using the autotools if you are compiling CVS yourself. Changes from 1.11.8 to 1.11.9: * CVS now knows how to report, as well as record, `P' record types. * When running the `cvs history' command, clients will now send the long-accepted `-e' option, for all records, rather than explicitly requesting `P' record types, a request which servers prior to 1.11.7 will reject with a fatal error message. * A problem with locating files requested by case insensitive clients which was accidentally introduced in 1.11.6 as part of a fix for a data loss problem involving `cvs add's from case insensitive clients has been fixed. The relevant error message was `cvs [ aborted]: filE,v is ambiguous; could mean FILE,v or file,v'. * Attempts to use the global `-l' option, removed from both client and server as of version 1.11.6, will now elicit a warning rather than a fatal error from the server. Changes from 1.11.7 to 1.11.8: * A problem in the CVS getpass library that could cause passwords to echo on some systems has been fixed. Changes from 1.11.6 to 1.11.7: * A segfault that could occur in very rare cases where the stat of a file failed during a diff has been fixed. * Any user with write privleges to the CVSROOT/checkoutlist file could pass arbitrary format strings directly through to a printf function. This was probably bad and has been fixed. White space at the beginning of error strings in checkoutlist is now ignored properly. * In client/server mode, most messages from CVS now contain the actual command name rather than the generic "server". * A long-standing bug that prevented most client/server updates from being logged in the history file has been fixed. * Updates done via a patch ("P" status) are now logged in the history file by default and the corresponding "P" history record type is now documented. If you're setting the LogHistory option in your CVSROOT/config file, you may want to add "P" to the list of record types. * CVS now will always compile and its own getpass() function (originally from GNULIB) in favor of any system one that may exist. This avoids some problems with long passwords on some systems and updates us to POSIX.2 compliance, since getpass() was removed from the POSIX.2 specification. * A bug that allowed a write lock to be created in a directory despite there being existing read locks when using LockDir in CVSROOT/config has been fixed. * A bug with short patches (`rdiff -s') which caused rdiff to sometimes report differences that did not exist has been fixed. * Some minor corrections were made to the diff code to keep diff & rdiff from printing diff headers with empty change texts when two files have different revision numbers but the same content. * The global '-l' option, which suppressed history logging, has been removed from both client and server. @ text @d3 1 a3 1 --- src/lock.c.orig Tue Nov 11 02:20:10 2003 d5 1 a5 1 @@@@ -405,7 +405,7 @@@@ Reader_Lock (xrepository) d11 1 a11 1 return (0); d14 1 a14 1 @@@@ -477,7 +477,7 @@@@ Writer_Lock (list) d20 1 a20 1 return (0); @ 1.4 log @Update to 1.11.6. * A warning message is now issued if an administrative file contains more than one DEFAULT entry. * An error running a verifymsg script (such as referencing an unset user variable or the script not existing) now causes the verification to fail. * Errors in administrative files commands (like unset user variables) are no longer reported unless the command is actually executed. * When a file is initially checked out, its last access time is now set to the current time rather than being set to the time the file was last checked in like the modification time is. * The Checkin.prog and Update.prog functionality has been removed. This fuctionality previously allowed executables to be specified in the modules file to be run at update and checkin time, but users could edit these files on a per workspace basis, creating a security hole. [NB: already fixed in the package earlier -- wiz] * Corrected the path in a failed write error message. * Autoconf and Automake are no longer run automatically unless you run configure with --enable-maintainer-mode. Accordingly, noautomake.sh is no longer needed and has been removed. * We've standardized on Automake version 1.7.5 and Autoconf version 2.57 to get at a few new macros. Again, this should only really affect developers. See the section of the INSTALL file about using the autotools if you are compiling CVS yourself. @ text @d3 1 a3 1 --- src/lock.c.orig Fri Feb 28 22:46:48 2003 d5 1 a5 1 @@@@ -413,7 +413,7 @@@@ Reader_Lock (xrepository) d14 1 a14 1 @@@@ -485,7 +485,7 @@@@ Writer_Lock (list) @ 1.3 log @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. @ text @d3 1 a3 1 --- src/lock.c.orig Wed Sep 26 20:54:09 2001 d5 1 a5 1 @@@@ -403,7 +403,7 @@@@ d14 1 a14 1 @@@@ -475,7 +475,7 @@@@ @ 1.2 log @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. @ text @d3 1 a3 1 --- src/lock.c.orig Thu Jul 27 18:49:27 2000 d5 3 a7 3 @@@@ -395,7 +395,7 @@@@ FILE *fp; char *tmp; d14 1 a14 1 @@@@ -467,7 +467,7 @@@@ @ 1.1 log @Nuke the klugy CVSREADONLY hack, and instead use a modified version of our old `cvs -u' changes to prevent lock creation. @ text @d3 3 a5 3 --- src/lock.c.orig Wed Mar 4 00:41:50 1998 +++ src/lock.c Tue Apr 20 10:15:04 1999 @@@@ -243,7 +243,7 @@@@ d14 1 a14 1 @@@@ -316,7 +316,7 @@@@ @