Development

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

It takes a long time for FreshPorts to process a new vuln.xml file. A very long time. Why? Because it process all entries in the file. Every time. Anton Berezin proposed an idea. I paraphrase, but in brief, he said: Figuring out what changed is as easy as hashing an entry and storing it in

A number of new features have recently gone into FreshPorts. Each of which has been written above before. I will outline the changes, and provide a link to the original post about that feature. svn coming soon… – FreshPorts now handle commit from three mailing lists: cvs-doc, cvs-ports, and svn-src-all. What ports are dependant upon

In my previous post, I mentioned problems encountered with processing vuxml entries for horde4-imp. The problem was not specific to a particular port, but came to light because a vuln was registered for a port, and then later removed. I tracked down the cause to not clearing out statistics before processing the new vulnerabilities. This