What’s in the pipeline, how it works, how it’s made…
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 […]
Fixing . in filenames Read More »
Yesterday, a commit came along which made FreshPorts quite upset. To be realistic, it wasn’t upset at all. It processed everything just nicely. Just not the right way. The commit in question (201205250144.q4P1i4Hc009503@repoman.freebsd.org) contained some pathnames such as this: ./databases/qt4-sql pkg-plist ./devel/dbus-qt4 Makefile pkg-plist ./devel/qmake4 Makefile pkg-plist ./devel/qmake4/files Makefile.bsd ./devel/qt4 distinfo ./devel/qt4/files patch-configure ./devel/qt4-assistant Makefile
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 »
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 »