Return-Path: Mailing-List: contact gump-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list gump@jakarta.apache.org Received: (qmail 24234 invoked from network); 25 May 2003 12:06:21 -0000 Received: from nan-smtp-12.noos.net (HELO smtp.noos.fr) (212.198.2.83) by daedalus.apache.org with SMTP; 25 May 2003 12:06:21 -0000 Received: (qmail 57900665 invoked by uid 0); 25 May 2003 12:06:19 -0000 Received: from unknown (HELO vma) ([195.132.246.233]) (envelope-sender ) by 212.198.2.83 (qmail-ldap-1.03) with SMTP for ; 25 May 2003 12:06:19 -0000 From: "Vincent Massol" To: Cc: "'Sam Ruby'" Subject: [Cactus] Still some problems with web site publication Date: Sun, 25 May 2003 14:06:06 +0200 Message-ID: <006a01c322b6$0595c700$e9f684c3@vma> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4024 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hi Sam, There are still gotchas with the cactus web site publication after the Gump build. On /www/jakarta.apache.org, there are 3 files/directories related to cactus: cactus0/ cactus/ jakarta-cactus-doc-20030518/ - I think jakarta-cactus-doc-20030518/ should be removed (but I can't do it as I don't have the permissions) - I think cactus0/ is the original site before you made the try. This I will remove after you copy the 1.4.1 and clover-* directories (see below). - cactus/ is probably from your last gump publication and is the cactus web site. There is a potential bug in the publication algorithm. It must *override* the existing web site and not be a "clean" publication. This is because there are some files that are not republished every time. More specifically: - cactus0/1.4.1 should also be in cactus/1.4.1 (however, I don't have the rights to do the copy). Can you do that? - cactus0/clover-12 and cactus0/clover-13 should also be in cactus/ The permissions should allow anyone from the group to have write access. Can you either perform the change or change the permissions so that I can do it? Also, it seems the publication is not working fine as nothing has been published since the 18th. For example the build was fine on the 25th but nothing was published... Can you help? Thanks -Vincent