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
Latest Vulnerabilities … aren’t Read More »
Baptiste Daroussin (bapt) brought my attention to a new port today. It’s about three months old, but it wasn’t showing up in FreshPorts. If you look at ports-mgmt/pkg now, it should look like this: bapt speculated that perhaps pkg was a reserved word in FreshPorts. I thought not. I was wrong. It is a special
ports-mgmt/pkg not found Read More »
Well, perhaps not 5000 errors, but quite a lot of errors. A recent change to Mk/bsd.perl.mk has caused all sorts of grief on two of the FreshPorts servers. The problem occurs when specifying PORTDIR. Here is an example: #!/bin/sh make -V BUILD_DEPENDS -V FORBIDDEN \ -f /usr/home/dan/ports/databases/p5-DBIx-Class/Makefile DISTDIR=/usr/ports/distfiles PORTSDIR=/usr/home/dan/ports make -V BUILD_DEPENDS -V FORBIDDEN \
Mk/bsd.perl.mk bug causes 5000 errrors…. Read More »
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
VUXML – doing it faster Read More »
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
Upgrades over the weekend.. Read More »
This issue was brought to my attention by wxs (Wesley Shields). The issue is evident at http://www.freshports.org/graphs2.php. When you get there, click on click on Commits Over Time by Committer and then wait for the page to load. Scroll down to the D’s. There you’ll see a few committers suffixed with ‘(ports committer)’. Looking in
The committer field is not always an email address Read More »
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
Fixes for vuxml processing Read More »
Mr Thomas wrote me regarding mail/horde4-imp and a particular vulnerability. Specifically, he figured that a recent commit (link to mail archives) fixed a bad entry in vuxml. Let’s look into that now. I first compared dev, beta, and production. All three had the port flagged as vulnerable. This situation is indicated by a skull at
mail/horde4-imp vulnerability Read More »
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,
commits without files Read More »