The original problem was explained and fixed however it seems to have resurfaced. Either that, or it was not fixed at all. In short: FreshPorts sees the first commit for a port on a branch the commit is deleting that port FreshPorts detects that the port has been deleted It forgets, somehow, that the port […]
When a port on a branch is deleted, FreshPorts tried, and fails, to refresh it Read More »
I’ve noticed a log of sanity test failures related to devel/binutils lately. Every single commit. Issue 133 deals with that. Here, I plan to document what happened. FreshPorts has, since inception, worked off the commit emails. The incoming email is parsed and XML created. The XML is then used to update the database. I started
The slave ports for devel/binutils did not get deleted Read More »
A mail error is breaking many things, including the daily reports and sanity test failures. This problem is only on production, not on dev. The error is: could not open Mail::Sender. from=’FreshPorts Sanity Daemon <FreshPorts@example.org>’ to=’kwm@example.org’ subject=’FreshPorts sanity checking’ errorcode=’-24′ errormsg=’IO::Socket::SSL- >start_SSL failed: SSL connect attempt failed with unknown error error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed’ I
mail error is breaking sanity test reporting Read More »
Every port has one primary category. This is the directory under which the port can be found. For example. the primary category for sysutils/bacula-server is sysutils. The primary category is always a physical directory on disk within the ports tree. A port can reside within more than one category. For example, net/pear-Net_SMTP has two secondary
CATEGORIES does not contain the primary category Read More »
A few days ago, I noticed portaudit telling me about a few things that needed to be updated: # portaudit Affected package: rubygem-rails-1.2.3 Type of problem: rubygem-rails — session-fixation vulnerability. Reference: <http://www.FreeBSD.org/ports/portaudit/30acb8ae-9d46-11dc-9114-001c2514716c.html> Affected package: rubygem-rails-1.2.3 Type of problem: rubygem-rails — JSON XSS vulnerability. Reference: <http://www.FreeBSD.org/ports/portaudit/44fb0302-9d38-11dc-9114-001c2514716c.html> Affected package: rubygem-activesupport-1.4.2 Type of problem: rubygem-rails — JSON XSS
vuxml issue – vulnx.txt did not contain UTF-8 Read More »
Late yesterday, I noticed a couple of sanity test failures. What was interesting about these reports was the lack of an error message. I emailed the committer to let them know I was looking into it. There were two failures. The first against devel/aunit; the second against devel/florist-gpl. By the time you read this, the
Sanity test failure reports no problem Read More »
The Search and Sanity Test Failure features are now in production. Enjoy.
Latest Search and Sanity Test Failures changes now in production Read More »
FreshPorts has a long history of Sanity Testing each commit to the FreeBSD Ports tree. It has been doing this for two main reasons: Ensure the integrity of the FreshPorts database Help correct obvious errors as soon as possible In 2002, FreshPorts allowed committers to opt in to receiving these notifications directly. Prior to this
Sanity Test Failures Read More »
I noticed this today. First, I apologise for highlighting the errors of others, but it is relevant to the topic. FreshPorts has a number of sanity tests that it performs on each commit to a port. It does simple things like: make -V PORTVERSION If an error occurs during any sanity test, FreshPorts records and
Broken ports cause vuln problems Read More »