should drupal CVS "work"?

By mikemee on 15 Jan 2004 at 17:05 UTC

If I download the latest greatest CVS version using the link http://drupal.org/drupal/cvs/drupal/drupal-cvs.tar.gz, should I expect to get a basically working version of Drupal? (Modulus any unintended bugs :->).

I.e., are CVS checkins only allowed that maintain a constantly working Drupal, or can developers checkin partially completed work with more to follow?

The reason I ask is that I can get 4.3.2 running without a problem under 1and1.com's cgi/php, but when I try the CVS version (as of 10 mins ago) using exactly the same steps I get a Server Error 500.

thanks in advance. Drupal is SO cool!

Comments

You should not be getting a 500.

Dries commented 15 January 2004 at 19:18

You should not be getting a 500. I just updated drupal.org to HEAD so something is wrong on your end.

how to debug?

mikemee commented 16 January 2004 at 00:35

Thanks. Any suggestions on how to debug this? Is there some switch I can enable (in conf.php maybe) that will write a text log file? Unfortunately on this virtual hosted service I don't get much access to real error logs.

Note (again) that 4.3.0 installs without error.

I'd like to contribute by finding the problem for you, so any debug hints would be helpful.

cheers, michael

I have the same trouble, 4.3.

pz commented 16 January 2004 at 12:35

I have the same trouble, 4.3.2 works but cvs gives "500 Internal Server Error". When checking apache log I get this "malformed header from script. Bad header=HTTP/1.0 404 Not Found".

Using Win98, apache 1.3.27, php4.2.3.