July 2012

I noticed last night that the list of ‘Latest Vulnerabilities’ on dev and beta differ from that found on production. Specifically, prod lists entries for: php5 Jul 23 php52 Jul 23 php53 Jul 23 rubygem-activemodel* As previously noted, the new vuxml processing code is on the dev and beta servers, but not yet in production. […]

This is a partial list of things that had to change for svn. I’m basing this on my cvs logs and memory. ~/.procmailrc – make sure we process the incoming email from the new mailing list mailing list subscription – subscribe to the new commit messages adjust verifyport.pm to not fetch directories (which appear in

Can we produce a src only news feed? I think so. FreshSource, our sister website, runs off the same database instance as FreshPorts. It merely uses a different web interface. It has a new feed, but it covers all commits, not just src and ports. The SQL used to generate that news feed is: SELECT

I have identified a lingering SVN issue, relating to tag expansion when accessing the repository via the web interface. The VUXML page is not displaying the details of the last processed vuln.xml. It should show something like (this example from pre-SVN): Revision: 1.2752 Date: 2012/07/11 Time: 01:47:55 Committer: swills This problem is related to non-expanding

With the recent move of the FreeBSD ports tree to SVN from CVS, there are some subtle changes on FreshPorts. Early this morning, I noticed a commit which demonstrated a side effect that I had not anticipated. The issue isn’t obvious from the above link, but I noticed it when the commit failed to properly

The FreeBSD Ports tree is now on SVN. I had a few last minute things to change, such as fetching files from the new svn repo. That proved to be a bigger task than I thought it might be. At present, everything seems to be working fine. However, links from FreshPorts to the repo still

I think I have a solution for the move to svn. It seems quite straight forward. First, we have the concept of a repository. For the ports tree, all the commits will go under ports/. This is exactly like svn. However, I need to munge the incoming filenames. For example, take this test svn commit

Early this morning I started poking around the database to see if there were some issue I needed to fix. I found some. Specifically, the port commits are all under ports/, but the src commits appear to be under /. This situation can be fixed fairly easily via SQL, but to maintain the structure will

After my earlier post regarding my first impressions regarding the move to svn, I’ve found an example which hints that the system is already munging pathnames. For example, look at this src commit. You’ll see these pathnames: /sys/cam/scsi/scsi_all.c /sys/cam/scsi/scsi_ch.c However, in the original email, you’ll these pathnames: head/sys/cam/scsi/scsi_all.c head/sys/cam/scsi/scsi_ch.c This is very very promising. I

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