Last night I discovered a caching bug related to vuxml processing. I fixed it. Today I realized the same issue affects processing of MOVED and UPDATING. Coded both of them today as well. Anyone got a MOVED or UPDATING commit just waiting to happen? ;) Ideally, I’d be able to find somewhere in the database […]
MOVED & UPDATING need cache removal code Read More »
Today I discovered and fixed two problems with VUXML processing. The cronjob that processed VUXML changes was commented out. The last time it had run was July 9th. Uncommenting the entry fixed that issue. The VUXML processing did not clear the cache. I wrote and testing that code just now. It’ll run in BETA for
Royce Williams wrote in with a good suggestion about the watch list interface. When I read it, I immediately new it was a good idea. Royce said the existing icons for adding and removing a port from the watch list were not intuitive. He suggesting using as a base, and putting either a plus (+)
Watch list interface changes Read More »
You may have seen this in your new port report recently: 16 Jul 2006 http://www.FreshPorts.org/devel/p5-Class-Multimethods-Pure/ http://www.FreshPorts.org/devel/p5-Luka/ Exception handling and reporting framework What is missing is a description for devel/p5-Class-Multimethods-Pure. It should be there. And if you click on the link provided, you’ll see it. So why doesn’t the description appear in the report? It’s all
No more blank descriptions Read More »
I’ve fixed the cache problem. Reading the last few posts here, you’d know there have been a few cache problems. I’m hesitant to say it’s now all fixed, but well, I hope so. The latest problem related to clearing cache entries. It was a permissions issue. The script which removes the cache entries runs as
Cache problem fixed Read More »
I found out exactly why the cache was not being cleared. Incorrect code. < my $CachingFile = $FreshPorts::Config::CachingRoot . '/cache/' . $category_name . '.' . $port_name; --- > my $CachingFile = $FreshPorts::Config::CachingRoot . ‘/cache/ports/’ . $category_name . ‘/’ . $port_name . ‘.*.html’; The first line is the existing production code. It refers to the old
Cache removal problems Read More »
I know we have a caching problem. I suspect I know the cause. The symptoms of the problem are: a commit has been processed by the system. the commit can be viewed via the URL /commit.php?message_id=MESSAGEID the commit can be seen via index.php or date.php the commit cannot be view on the port page I
Florent Thoumie mentioned today that FreshPorts should not supply package installation instructions for Restricted ports. Why? This extract from /usr/ports/Mk/bsd.port.mk indicates why # RESTRICTED – Prevent the distribution of distfiles and packages to # the FTP sites or on CDROM (e.g. forbidden by license # considerations). If we are not allowed to distribution the package,
Yes, we have no packages Read More »
Shaun Amott wrote in to tell me of a bug with the /usr/ports/UPDATING code. FreshPorts parses this file each time it is committed and loads the data into a table. When a port is displayed, any notes from UPDATING are displayed with that port. The purpose is to alert the reader to any potential instructions
Improving the parsing of /usr/ports/UPDATING 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 »