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

In short, the concept of any computer system is usually straight forward. The complexity comes from the exceptions. Take commits for example. Yes, each commit affects a file. Or so you’d think. Consider this commit. FreshPorts parses the email. In that email, there are no files mentioned. This caused a problem during the loading. FreshPorts,

A while back, the src tree for FreeBSD moved to svn. The ports tree is still on cvs. For some time now, http://svn.freshports.org/ has been including the svn commits. But now, as old mailing lists become inactive, it’s time to start integrating things into the main websites. The dev and beta websites have been running

Alex wrote in to mention that FreshSource was missing some src commits. In fact, he wrote twice. I’m glad he did. I replied to his first post saying that I was seeing www commits… He pointed out that no src commits were turning up. OH! I checked my local mailing list archive (i.e. a folder