From owner-freebsd-doc@FreeBSD.ORG Mon Jun 17 09:52:59 2013 Return-Path: Delivered-To: www@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 2092388E; Mon, 17 Jun 2013 09:52:59 +0000 (UTC) (envelope-from cvs-src@yandex.ru) Received: from forward1h.mail.yandex.net (forward1h.mail.yandex.net [IPv6:2a02:6b8:0:f05::10]) by mx1.freebsd.org (Postfix) with ESMTP id 90E9D1817; Mon, 17 Jun 2013 09:52:58 +0000 (UTC) Received: from smtp4h.mail.yandex.net (smtp4h.mail.yandex.net [84.201.186.21]) by forward1h.mail.yandex.net (Yandex) with ESMTP id 274AB9E0C9F; Mon, 17 Jun 2013 13:52:55 +0400 (MSK) Received: from smtp4h.mail.yandex.net (localhost [127.0.0.1]) by smtp4h.mail.yandex.net (Yandex) with ESMTP id A31692C0EAC; Mon, 17 Jun 2013 13:52:55 +0400 (MSK) Received: from unknown (unknown [178.76.224.133]) by smtp4h.mail.yandex.net (nwsmtp/Yandex) with ESMTP id PUJwl65DOc-qtcGkG4h; Mon, 17 Jun 2013 13:52:55 +0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1371462775; bh=KzD7jcvTNAL/KIhipgHPOkWIkJuFUxnwfrimN8g6cMc=; h=Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject: References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=eirolqCkTDwznhTysF6fBHo5S9Uaic2AB/t3h/Kv8QxzB6vHYOE6EfbrqS7M8o98H 53PDMaX3tlJN0as97Hn8P+SPAeWTToMcjvvuSpK2RanURMUjkFaJtCJiHFlHVkrSuX 1wdShaWQsHm2V3ngsFcS4OvMpuPF3jHxOdCvNSjA= Authentication-Results: smtp4h.mail.yandex.net; dkim=pass header.i=@yandex.ru Message-ID: <51BEDC62.5040904@yandex.ru> Date: Mon, 17 Jun 2013 13:52:34 +0400 From: Ruslan Makhmatkhanov User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130516 Thunderbird/17.0.6 MIME-Version: 1.0 To: Glen Barber Subject: Re: cgi/ports.cgi: Last database update References: <51930CFB.3020106@yandex.ru> <20130515125415.GA1635@glenbarber.us> <51BDEE9C.5020705@yandex.ru> <20130616210203.GU1692@glenbarber.us> In-Reply-To: <20130616210203.GU1692@glenbarber.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: www@freebsd.org X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jun 2013 09:52:59 -0000 Glen Barber wrote on 17.06.2013 01:02: > On Sun, Jun 16, 2013 at 08:58:04PM +0400, Ruslan Makhmatkhanov wrote: >> Hi Glen, >> >> Glen Barber wrote on 15.05.2013 16:54: >>> On Wed, May 15, 2013 at 08:20:11AM +0400, Ruslan Makhmatkhanov wrote: >>>> Hello, >>>> >>>> some user on a forum pointed out that freebsd.org's ports tree is >>>> not updated since 2012-11-11. F.e. I looking for gajim in the ports >>>> tree: >>>> http://www.freebsd.org/cgi/ports.cgi?query=gajim&stype=all&sektion=all >>>> >>>> There is the message: >>>> "Last database update: 2012-11-11 10:45:48 UTC" >>>> >>>> And gajim version is at 0.15.2 (while it was already updated to >>>> 0.15.3_1) and gajim-devel still here. >>>> >>>> If I understand correctly, this may be related to CVS-exporter deprecation. >>>> >>>> Is this is a known issue and is there any plans to fix that? >>>> Thanks. >>>> >>> >>> I will take a look at this today. >>> >>> Glen >> >> Any news? >> > > Sorry for the delay here. > > So, there are a few different problems all in this area, that are all > related to the same underlying infrastructure. But, here's the short > version: > > I am in the midst of deprecating the machine that used to be responsible > for doing the doc/www builds (previously known as red.FreeBSD.org). > Well, to be more clear, it is already (physically) deprecated, but its > services have been moved to a jail on a different system. > > The problem I've run into is that there are a few things that are so > intertwined, and dependent on the filesystem, that it is actually quite > much of a mess to untangle. > > I have some (I think most) of these running within the new system. > (These are where some of the random error emails originated a few weeks > ago, actually.) But there are still some service-untangling to do. > > Some of the filesystem-dependent things appear to use cvs-style > checkouts of doc/www (meaning, different directories), and I think this > is the core of the problem with the CGI stuff not working. > > Getting this working again is a very high priority for me, but > unfortunately was out of town last week unexpectedly, so not a whole lot > of untangling got accomplished. > > Once I get the CGI hosting moved from the current setup to the new > setup, some (if not all) of these website CGI problems should go away as > a general side effect of the updates. > > I hope, worst case, to have everything fully functional on the new > system within the week. When this happens, I'll send a heads-up to > ops-announce@ mailing list, since I found with the last move that some > things did unexpectedly break, so while I can test the majority of the > services provided here, I likely will miss something. > > I know it is not the answer you wanted to hear. But I am working on it, > and just need a bit more time to make sure I do not break everything, > since there are a lot of interdependencies here. > > Glen Thank you for such an extended response, Glen. Feel free to ping me if you need any help with testing of the new setup (from web-user point of view). -- Regards, Ruslan Tinderboxing kills... the drives.