2012

The FreeBSD ports tree is moving to svn. FreshPorts is ready. Nearly. FreshPorts has been processing doc and src commits via svn for some time. Now it’s time for prots. The first problem to solve: how to resolve the change in pathnames. At present, all files in the ports tree reside under ports/. With the […]

The Vulnerable Ports bug has been fixed and the patches applied to beta. It will be another week or two before it is applied to production. Here is the fix: $ cvs diff -ur 1.171 sp.txt Index: sp.txt =================================================================== RCS file: /home/repositories/freshports-1/database-schema/sp.txt,v retrieving revision 1.171 retrieving revision 1.172 diff -u -r1.171 -r1.172 — sp.txt 24

In recent posts, I’ve spoken about a particular task taking about an hour to process. I think I have found one small improvement. A query has gone from 50ms to about 5ms with the addition of an index. The query is: SELECT count(vuxml_id) FROM commit_log_ports_vuxml CLPV, commit_log_ports CLP, ports P WHERE CLP.commit_log_id = CLPV.commit_log_id AND

FreeBSD makes use of security/vuxml to keep track of vulnerabilities within software. If you install ports-mgmt/portaudit, your daily security summary email will note any reported vulnerabilities that exist within your installed ports. I recommend that you install mgmt/portaudit on all your systems. If you are running jails, I recommend that you install ports-mgmt/jailaudit on your

It takes FreshPorts about an hour to process an entire vuln.xml file. There is a lot of work to do. Let’s cut that up. Usually, a new vuln is being added, or an existing vuln is being changed. It was suggested by someone, I cannot recall who, that we could store a checksum for each

I am seeing this error from time to time: This message was generated by the FreshPorts Daemon. The database is freshports.org at http://dev.freshports.org/ A port specified in the RUN_DEPENDS does not exist: ‘lang’ I am quite sure it’s easy to fix, but there is this time issue….

A couple of days ago, we had a problem with . in filenames. My solution was to manually amend the commit email. Today, I fixed the code after it happened again. This is a good thing. Compare this screen shot with the real commit (may not be fixed in prod yes, but has been in

FreshPorts stopped working overnight. It ran out of disk space. The space was taken by PGCon and BSDCan backups. The slides for the talks can take up a lot of space. After freeing up some space and starting PostgreSQL, the website is back. I think some commits may be missing. I will check this evening

Ruslan wrote in to mention that the ‘Latest Vulnerabilities’ section is not current. I’m trying to find out why. FreshPorts has processed the latest vuln entries; http://www.freshports.org/vuxml.php reports Revision: 1.2685. But http://www.freshports.org/vuxml.php?all lists nothing later than 2012-04-27. I just refreshed the security/vuxml port on the main FreshPorts server. It is now re-processing the latest vuln