Brad Davis wrote in to explain that the home page for net-mgmt/nagios-snmp-plugins-extras on beta is wrong. It is missing the hostname for the URL. Indeed it is. And it’s wrong on the dev box too. I looked. I found out the cause. Here is a brief version of the code which pulls back the hostname

When I went looking for commands to convert to the new jail strategy, I failed to find two. I have remedied that oversight now. make showconfig This command extracts the configuration items from the port. Like all the other scripts, it is fairly straight forward. The following is from make-showconfig.sh: make master-sites-all This command extracts

emmh wrote to mention that the vuxml posts on FreshPorts were out of date. I checked. Sure enough. They were. Checking the sites On the homepage, under Latest Vulnerabilities, the latest entry was dated Oct 17. And here it was, November. Something is wrong. The beta website showed Aug 14. And my dev website showed

FreshPorts processes commit emails, updates via svn, then extracts data via make -V. That’s the short of it. However, stuff goes wrong. And sometimes we can’t update. Or the extract fails. This leaves data in the database which does not reflect what is in the port. This query, which I was creating tonight, may help

Why can’t things be simple? The basic premise of FreshPorts is parse, an email, put it in the database. Sounds simple? Well, it is. Until you start dealing with the exceptions. Such as slave ports. Such as UTF-8…. I only just got used to dealing with base64-encoded messages when a real UTF-8 character shows up.

I think I have a solution for base64 emails. I emailed Matthew Seaman on Wednesday about this issue. He put me onto two very useful Perl modules: Email::MIME mail/p5-Email-MIME Email::Simple mail/p5-Email-Simple/ Email::Simple::Header The solution is coded below: sub myGetMessage { my ($message); my ($encoding); while () { $message .= $_; } $encoding = myGetMessage_ContentTransferEncoding($message); print