<?xml version="1.0" encoding="UTF-8"?><!-- generator="WordPress/2.5" -->
<rss version="0.92">
<channel>
	<title>FreshPorts News</title>
	<link>http://news.freshports.org</link>
	<description>News and announcements regarding FreshPorts, The Place For Ports.</description>
	<lastBuildDate>Tue, 24 Jan 2012 01:49:10 +0000</lastBuildDate>
	<docs>http://backend.userland.com/rss092</docs>
	<language>en</language>
	
	<item>
		<title>VUXML - doing it faster</title>
		<description><![CDATA[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 [...]]]></description>
		<link>http://news.freshports.org/2012/01/23/vuxml-doing-it-faster/</link>
			</item>
	<item>
		<title>Upgrades over the weekend..</title>
		<description><![CDATA[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 [...]]]></description>
		<link>http://news.freshports.org/2012/01/23/upgrades-over-the-weekend/</link>
			</item>
	<item>
		<title>The committer field is not always an email address</title>
		<description><![CDATA[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&#8217;s.  There you&#8217;ll see a few committers suffixed with &#8216;(ports committer)&#8217;.
Looking [...]]]></description>
		<link>http://news.freshports.org/2011/11/01/the-committer-field-is-not-always-an-email-address/</link>
			</item>
	<item>
		<title>Fixes for vuxml processing</title>
		<description><![CDATA[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 [...]]]></description>
		<link>http://news.freshports.org/2011/10/02/fixes-for-vuxml-processing/</link>
			</item>
	<item>
		<title>mail/horde4-imp vulnerability</title>
		<description><![CDATA[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&#8217;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 [...]]]></description>
		<link>http://news.freshports.org/2011/09/25/mailhorde4-imp-vulnerability/</link>
			</item>
	<item>
		<title>commits without files</title>
		<description><![CDATA[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&#8217;d think.  Consider this commit.
FreshPorts parses the email.  In that email, there are no files mentioned.  This caused [...]]]></description>
		<link>http://news.freshports.org/2011/09/24/commits-without-files/</link>
			</item>
	<item>
		<title>svn coming soon&#8230;</title>
		<description><![CDATA[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&#8217;s time to start integrating things into the main websites.
The dev and beta websites have [...]]]></description>
		<link>http://news.freshports.org/2011/09/17/svn-coming-soon/</link>
			</item>
	<item>
		<title>Wrong prefix on some pathnames</title>
		<description><![CDATA[As mentioned in the comments of my previous post, some commits have been processed with an incorrect prefix.  That is, some pathnames are missing the src/ part of the path.
I just went looking&#8230;
I found interesting stuff.  1233 rows of interesting stuff.
For example:

SELECT *
  FROM element_pathname
 WHERE pathname NOT LIKE '/ports/%'
   [...]]]></description>
		<link>http://news.freshports.org/2011/08/08/wrong-prefix-on-some-pathnames/</link>
			</item>
	<item>
		<title>Missing src commits</title>
		<description><![CDATA[Alex wrote in to mention that FreshSource was missing some src commits.  In fact, he wrote twice. I&#8217;m glad he did.  I replied to his first post saying that I was seeing www commits&#8230;  He pointed out that no src commits were turning up.
OH!
I checked my local mailing list archive (i.e. a [...]]]></description>
		<link>http://news.freshports.org/2011/08/08/missing-src-commits/</link>
			</item>
	<item>
		<title>Doing commits in the correct order</title>
		<description><![CDATA[Lately, I&#8217;ve been thinking and writing about how to list ports that depend upon this port.  Today, another special situation arose: doing commits out of order.
Case in question: this commit support for databases/php5-sqlite3 to lang/php5-extensions.
The lang/php5-extensions commit was at 15:52:14.  However, databases/php5-sqlite3 was not created until 15:54:29.
I am not sure how to best [...]]]></description>
		<link>http://news.freshports.org/2011/04/15/doing-commits-in-the-correct-order/</link>
			</item>
</channel>
</rss>

