bug-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CVS 1.11.18 - Windows Bug - cannot write to stdout


From: Mark D. Baushke
Subject: Re: CVS 1.11.18 - Windows Bug - cannot write to stdout
Date: Wed, 17 Nov 2004 17:44:19 -0800

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Conrad T. Pino <address@hidden> writes:

> > From: Mark D. Baushke
> > 
> > > Should I post the binary as it is?
> > 
> > Probably not. :-(
> 
> OK, the 1.11.18 Windows binary is on indefinite hold.

I suppose you could put up a patched 1.11.18 version for windows if
Derek agrees it is a reasonable thing to do.

> What happens now with respect to the 1.11.18 version?

That is up to Derek, but I am guessing that releasing a 1.11.19 version
fairly soon makes the most sense.

There are a few issues outstanding with the 1.11.18 release that have
been reported so far:

   a) Missing files in the ditribution. Fixed in 1.11.18.1.
      (Report from "Chris Bohn" <address@hidden>.)

   b) Windows bug in handle_m() and handle_e() that generates error no
      output. Fixed in 1.11.18.1.
      (Report from "Conrad T. Pino" <address@hidden>.)

   c) A regression from an older version of cvs where we get an
      assertion failure in the following case:

        % rm -rf /tmp/testcvsroot
        % cvs -d :fork:/tmp/testcvsroot init
        % cvs -d :fork:/tmp/testcvsroot version
        Client: Concurrent Versions System (CVS) 1.11.18 (client/server)
        Server: Concurrent Versions System (CVS) 1.11.18 (client/server)
        % cvs -d :fork:/tmp/testcvsroot rtag testtag CVSROOT/modules
        % cvs -d :fork:/tmp/testcvsroot co -pr testtag CVSROOT/modules
        assertion "repository != NULL" failed: file "recurse.c", line 667
        cvs [checkout aborted]: received abort signal
        % 

      (Report from "John Elgin" <address@hidden>.)

   d) cvs 1.11.18 under MacOS X (10.3.6) sometimes generates a bus error
      during a call to tzset().

      My opinion is that 10.3.6 is just buggy and that users could work
      around the problem changing config.h to use #undef HAVE_TZSET, but
      I have not had opportunity to investigate any further.
      (Report from "Marius Schamschula" <address@hidden>.)

I don't have a fix for #c, but it would probably be a good idea to fix
it before we spin 1.11.19 if possible.

        -- Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)

iD8DBQFBm/5z3x41pRYZE/gRAuT5AKDVuputy+2faFU39XtPBOtRiysk6gCgzHEp
Yn2Ema+mG7MDjRXgeIumrf0=
=TsJk
-----END PGP SIGNATURE-----




reply via email to

[Prev in Thread] Current Thread [Next in Thread]