This just came to my attention. The processing of pkg-descr since we moved to using a jail-based solution is wrong. The function which reads and processes the contents of pkg-descr is not using the jail to read the file. I’ll fix the bug soon, and refresh all commits which touched pkg-descr. Noted by koobs with […]
Problem with long descriptions Read More »
koobs mentioned I need to look at etag. See http://redbot.org/?uri=http%3A%2F%2Fwww.freshports.org%2Fsecurity%2Fpy-pycrypto%2F
The problem Sometimes the data in a field changes over time. Or rather, what you expect to appear in the field changes. Case in point, the committer field in a commit email is not always the user id of the committer. Sometimes it contains spurious characters. This is one of the classic problems associated with
committer isn’t always user name Read More »
Earlier today I run cvsup on the main website and pulled down the code for running make -V in a ‘jailed’ environment. It’s not actually a jail; it’s more of a chroot. You can read up on previous jail posts first, but the idea came from Ryan Steinmetz (zi@). I found the idea incredibly simple
Production now using chroot Read More »
If a vuxml entry is updated, and the ranges change, those changes are not recorded in FreshPorts. This came to my attention from the FreeBSD Security team. They noticed that for the recent Oracla Java vuln FreshPorts had all versions for > 7. It boiled down to this: http://www.freshports.org/vuxml.php?vid=16846d1e-f1de-11e1-8bd8-0022156e8794 [1] differs from this: http://www.vuxml.org/freebsd/16846d1e-f1de-11e1-8bd8-0022156e8794.html [2]
Updates to vuxml ranges fails Read More »
I have to say, FreshPorts would be a very simple piece of code if it wasn’t for all the exceptions to the rules. But then, that is true for most software. Case in point, I’ve seen three base64 encoded emails in the past week or so. Each one makes FreshPorts barf. It has no idea
base64 encoded emails Read More »
Hmmm, I thought with my recent changes to use ‘svn up -r XXX’ would solve the problem of repo-copies. Why are repo-copies a problem for FreshPorts? FreshPorts knows only about the files mentioned in a commit. With repo-copies, a whole directory is moved, but the files in that directory are not mentioned in the commit.
svn up creates conflicts Read More »
I recently discovered that for some pathnames, the URL is incorrect. For an example, look at http://www.freshports.org/japanese/im-ja/files/patch-src_xim_Makefile.in. Click on the first file listed there: devel/gdb6/files/patch-i386%nm-fbsd64.h The URL should be http://www.freshports.org/devel/gdb6/files/patch-i386%25nm-fbsd64.h. That is, the embedded % should appear in the URL as %25, which is the hexadecimal value for a percent-sign. A simple solution, using PHP,
non-standard file names Read More »
When is a port not a port? When it was deleted before the ports_categories table was introduced. I noticed that some long-deleted ports were not displaying correctly. For example: http://www.freshports.org/sysutils/cdrecord/ It was displaying as a non-port, but it clearly was a port, although deleted. I tracked the problem down to this stored procedure: CREATE OR
When is a port not a port? 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 »