Late yesterday, I noticed a couple of sanity test failures. What was interesting about these reports was the lack of an error message. I emailed the committer to let them know I was looking into it. There were two failures. The first against devel/aunit; the second against devel/florist-gpl. By the time you read this, the […]
Sanity test failure reports no problem Read More »
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
The RAM shortage fix Read More »
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
The previous post was based on a question from Martin Wilke, who was looking for a vuxml entry against phpMyAdmin. We eventually found it. It had the wrong dates but it was found. Martin corrected the problem with a followup commit. This incident prompted me to make a couple of changes to FreshPorts with respect
List the vulnerabilities for this port Read More »
This isn’t about detecting vulnerabilities. It is about finding vulnerabilities that others have already reported. Background reading: FreeBSD Porter’s Handbook: Keeping the community informed FreeBSD VuXML Here are the various vuxml pages provided by FreshPorts: The latest vulnerabilities are listed on the home page A complete list of all vulnerabilities by date A complete list
Vulnerabilities – finding them easily (vuxml) Read More »
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
Back in August, I wrote about patching the ports tree to cater for master/slave relationships. I am happy to report that this patch is no longer required. Instead of MASTERPORT, as provided by that patch, I can use MASTER_PORT, which is now part of the stock ports/Mk/bsd.port.mk. \o/ No more patching.
No more patching for MASTERPORT Read More »
Since FreshPorts started caching the HTML, the watch list count started to lag. At present, it is refreshed only when the port is updated. The BETA website has a patch for this. It should go into production soon. To play with the patch, login at the BETA website, and add/remove a port to/from your watch
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,
At present, master/slave relationships in FreshPorts are not stored optimally. Each port has a field, master_port, which contains the category/port of its master_port, otherwise, it is an empty string. The ideal situation would be a table such as this: create table master_slave ( master_port_id integer not null, slave_port_id integer not null, primary key (master_port_id, slave_port_id)
Master/slave relationships Read More »