I’m so very happy about recent changes to the website. It’s been a great day. I was volunteering at a flu shot clinic. A new coffee shop has opened up, and I was there before the clinic. After the clinic, it was walking the dog, then some serious changes to the the PostgreSQL queries which […]
Great changes to the websites Read More »
The front page of FreshPorts is about to change, slightly. At present, the front page contains only the the commits to the main branch of the FreeBSD. More precisely, it does not include: Commits to Mk/ or other similar non-port entities within the ports tree Commits to the quarterly branch (whatever the latest quarter is;
Displaying all ports tree commits on the front page Read More »
When setting up a new FreshPorts ingress node, the repositories must be configured with tags so FreshPorts knows the last commit it has processed. This is the starting point each time FreshPorts goes to search for new commits. This post about Processing commits on branches with git might help with background. Those tags must be
Configuring the repo for a new ingress node Read More »
One of the primary uses for FreshPorts is searching various characteristics of the ports. One highly used search feature is pkg-messages (background at pkg-message). A problem which has been vexing me for about 2 months was the lack of results on prod, but results which worked on dev. The issue was raised on GitHub. Initially,
When tsvector was working as expected on most hosts, but not one Read More »
The Libreoffice homepages seem wrong. dev and test do not show a homepage for arabic/libreoffice, but stage and prod do. Could this be a commit which corrected something after dev and test were corrected? I think so. I think this commit did that. Let’s check from the command line. I’m doing this in my empty
What’s up with libreoffice homepages Read More »
The July 4th tweet announced “dev, test, and stage .freshports.org are now running Python 3.9”. Three days later, “Is it coincidental that dev, test, and stage are all stuck on commits from July 4?” I took notes as I explored the problem. The first clue was: 2022.07.07 00:12:03 git-delta.sh /usr/local/libexec/freshports/git-to-freshports-xml.py –repo ports –path /var/db/ingress/repos/ports –branch
Update to Python 3.9 broke commit processing Read More »
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
Help needed with shell scripting Read More »
This is the first of a series of posts which provide sample queries. Sometimes you need a starting point. This particular query will be used for showing the recent commits on a branch.
query: Latest 100 commits on a branch Read More »
Ports come and go. Sometimes they come back. Take a recent commit on 1 July against editors/ved (and others). This port was created on 01 Jan 2001 and removed on 15 May 2014 because it used the deprecated smake. The 1 July 2021 commit brought it back. There was a problem. Here is the page
When a deleted port is resurrected Read More »
This outlines the steps for putting the new git-delta.sh script into use. These steps will be required on each ingress node. stop ingress commit processing Look at the output of sudo tail /var/log/freshports/git.log and you should see something like this: [dan@devgit-ingress01:~] $ sudo tail /var/log/freshports/git.log 2021.06.27 17:21:05 git-delta.sh Repodir is /var/db/ingress/repos/src 2021.06.27 17:21:05 git-delta.sh Running:
Putting the new git-delta.sh into use on devgit.freshports.org Read More »