I need some help with the git processing shell script. Look at line 82 in this script please. See those hardcoded branch names? That’s my problem. Let’s reduce the shell script to a simple proof of concept. % cat ~/tmp/poc.sh #!/bin/sh git for-each-ref –format ‘%(objecttype) %(refname)’ \ | sed -n ‘s/^commit refs\/remotes\///p’ \ | while […]
I need some help from time to time. This is where you can contribute.
The FreshPorts server died on Friday night. I drove up on Sunday morning to retrieve it. I have not yet investigated the breakage. It might be the M/B. It was suggested on IRC that replace instead of repair might be a better approach. The existing X8DTU m/b has some unresolved IPMI vulnerability issues. A newer
Bjoern A. Zeeb pointed out a problem today. On the following URL, there should be more commits per page. Only three are shown (at the time of writing). http://www.freshports.org/search.php?stype=committer&method=exact&query=jb&num=100&orderby=category&orderbyupdown=asc&search=Search&include_src_commits=include_src_commits The page is showing 100 results per page. This should be 100 commits, but the result set is showing only 100 files. The SQL query has
The FreshPorts server is moving from San Jose to Austin. The server has been kindly and expertly hosted by Supernews since it arrived there in November 2006. However, Supernews has been bought by Giganews, who have kindly offerred to take over the hosting and sponsorship of FreshPorts. Here’s a map showing the source and destination.
FreshPorts is pretty good about not missing commits. It depends exclusively upon the cvs-all mailing list. If the message doesn’t arrive, it doesn’t get into FreshPorts. In the interests of increasing the complexity of FreshPorts, I’d like to validate the database against the cvs-all archives. Each commit generates one email message. Each email has a
FreshPorts often tries to help by creating HTML links. Most of the time, it gets this right. But for a recent port, it got it very wrong. Have a look at the PostgreSQL 8.2 page. Note the commits for 05 Feb 2007 and 09 Jan 2007. The code is taking what it thinks is a
A drill down refers to moving from summary information to detailed data by focusing in on something. On a ports commit, you can drill down in several ways. Take this commit for example. You can the following ways to drill down: takes you to the FreeBSD email archive takes you to the commit details 
In the previous post I showed how I found out it was the ports-deleted page that was causing httpd to die. Since then, I finished my coding to introduce pagination into that URL What was once on one page, is now on 32 pages. As a added bonus, because the changes were made to the