X-Original-To: pgsql-docs-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 26AFFD1B44B for ; Thu, 18 Dec 2003 09:06:46 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 84171-04 for ; Thu, 18 Dec 2003 05:06:16 -0400 (AST) Received: from pezone.net (pezone.net [81.169.154.182]) by svr1.postgresql.org (Postfix) with ESMTP id 5CACCD1B449 for ; Thu, 18 Dec 2003 05:06:14 -0400 (AST) Received: from localhost (localhost [127.0.0.1]) by pezone.net (Postfix) with ESMTP id C9F5A2480A9; Thu, 18 Dec 2003 10:03:52 +0100 (CET) Received: from pezone.net ([127.0.0.1]) by localhost (pezone.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 21361-10; Thu, 18 Dec 2003 10:03:52 +0100 (CET) Received: from pezone.net (localhost [127.0.0.1]) by pezone.net (Postfix) with SMTP id 861832480A8; Thu, 18 Dec 2003 10:03:52 +0100 (CET) Received: from 137.226.116.82 (SquirrelMail authenticated user peter) by new.host.name with HTTP; Thu, 18 Dec 2003 10:03:52 +0100 (CET) Message-ID: <35406.137.226.116.82.1071738232.squirrel@new.host.name> Date: Thu, 18 Dec 2003 10:03:52 +0100 (CET) Subject: Re: My SGML build fixed From: "Peter Eisentraut" To: In-Reply-To: <200312180015.hBI0FCA26136@candle.pha.pa.us> References: <200312180102.50115.peter_e@gmx.net> <200312180015.hBI0FCA26136@candle.pha.pa.us> X-Priority: 3 Importance: Normal X-MSMail-Priority: Normal Cc: , X-Mailer: SquirrelMail (version 1.2.7) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 8bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200312/44 X-Sequence-Number: 2204 Bruce Momjian writes: > How often does the postgresql.org site build the SGML files? Whenever something changes. > And just > last week the News build failed because it lost execution bits. Uh, so? Your reasoning is that because some unrelated program on an unrelated machine breaks, we should abandon all work on all programs on machines in the the DNS domain? > I still > don't trust dynamic content on postgresql.org to work reliably. Well, if something doesn't work, please help fixing it rather than duplicating it. Your build breaks just as often as anything else. (Remember last week.) And I want to know when the postgresql.org build was ever broken in the last two years. Right now it just seems like a waste of resources and it confuses the onlookers.