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: Derek Robert Price
Subject: Re: CVS 1.11.18 - Windows Bug - cannot write to stdout
Date: Thu, 18 Nov 2004 11:00:41 -0500
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040616

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

Mark D. Baushke wrote:

> 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.


Minor patches have been added to binaries in the past without
incrementing the version number.

> >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.


That's the plan.  I was going to give it a week or so to see if any
more problems came up.  So, in a week or so if we an solve the
existing problems by then.

>    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>.)


Sometimes?  Like in certain timezones or unpredictably?  Anyhow, if
#undef HAVE_TZSET works, then I will agree with you, at least until a
better solution makes itself apparent.

> 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.


Yep.

Cheers,

Derek
- --
                *8^)

Email: address@hidden

Get CVS support at <http://ximbiot.com>!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFBnMcpLD1OTBfyMaQRAvt1AKCXQt0emp7EU3dtuRHqS8xB3ijLRQCfTf+X
GfwVJ4RJELw5x/zukEtRG4Y=
=SjEv
-----END PGP SIGNATURE-----





reply via email to

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