Development

The fix: $ cvs di -ub port.pm Index: port.pm =================================================================== RCS file: /home/repositories/freshports-1/scripts/port.pm,v retrieving revision 1.52 diff -u -b -r1.52 port.pm — port.pm 6 Jun 2008 18:13:41 -0000 1.52 +++ port.pm 10 Aug 2008 21:09:51 -0000 @@ -160,6 +160,7 @@ # we are updating # NOTE: NULLIfEmpty invokes db_escape + # these items were escaped […]

The FreshPorts website has moved. It was at 216.168.29.4 and is now at 64.147.113.42, on the other side of the country. If your DNS is lagged, you will be redirected from http://www.freshports.org/ to http://beta.freshports.org/. Once your DNS catches up, you won’t be directed. This wonderful solution is accomplished with this directive on the old website:

A very key point in this article. Product vs project. Read: http://people.planetpostgresql.org/greg/index.php?/archives/120-Postgres-is-not-for-sale.html

Want $200? Free admission to BSDCan? And tutorials? Read this: http://blog.kozubik.com/john_kozubik/2007/12/bounty-posted-f.html

I’ve found work. Details here.

Here is the patch I just comitted which reduces the amount of RAM consumed. [dan@ngaio:/usr/websites/freshports.org/classes] $ cvs di -ub display_commit.php Index: display_commit.php =================================================================== RCS file: /home/repositories/freshports-1/classes/display_commit.php,v retrieving revision 1.8 diff -u -b -r1.8 display_commit.php — display_commit.php 10 Jul 2007 11:39:07 -0000 1.8 +++ display_commit.php 22 Oct 2007 17:22:23 -0000 @@ -87,19 +87,16 @@ $i=0; $GlobalHideLastChange

I was scanning the error logs this morning, looking for anything unusual. I found it: [Mon Oct 22 12:31:10 2007] [error] PHP Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 512 bytes) in display_commit.php on line 91 I have seen this before, but could not recall where. I also could not

FreshPorts encountered its first corrupted cvs-all email today. It handled it correctly. It errored out, put the emails aside in the retry queue, and sent me a notice. Af first, I thought the email had been corrupted on the way into my system. But after checking the above URL, I realised it was bad at

New categories arise from time to time. The descriptions for all categories are held in www/en/ports/categories. There are two situations when FreshPorts needs to fetch this file from CVS: When a new port is created. When www/en/ports/categories is updated. I have case #2 coded. Case #1 is not as easy to do. In case #2,

The tk category now has a member! This category was added to www/en/ports/categories about six months ago. It was this commit that did it. The previously reported problem with virtual categories repeated in production. That is to be expected. The proposed solution exists only on my private dev server at home. Regretably, the solution has