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 »
These are the steps I’m following to add the ports_to_refresh table. This is a list of issues I will track through this upgrade. branch badge not populated for commits on branch #327 base/binutils page broken #328 Wrong info about hplip-plugin port when using search #322 Package message not presented for x11/nvidia-hybrid-graphics/files/pkg-message.in … #321 404: Warning:
Adding the ports_to_refresh table Read More »
This post is the latest in a series of posts documenting the process of converting from using a chroot to using a full proper jail. I spent about 2 hours of this fine Saturday morning writing this up and carrying out the steps. As a result, both dev and test are now using a FreeBSD
How to convert from ports-jail to /jails/freshports Read More »
I was asked: Why does FreshPorts have links to both git and subversion repos? The short answer is: because at the time, the commits were committed to those respective repos. The links to the other repo do not exist. FreeBSD moved from using subversion to git. During the transition, the subversion repo became read-only. All
Why does FreshPorts link to both git and subversion repos? Read More »
Right now, we have have: dev.freshports.org devgit.freshports.org test.freshports.org testgit.freshports.org stage.freshports.org stagegit.freshports.org The goal: three hosts: dev, test, stage. I’ll delete the existing: dev, test, stage I’ll rename: devgit -> dev testgit -> test stagegit -> stage I think this will be easier than moving content from one jail to another. Each of the three renamed
It’s time to rename some hosts 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 »
Following on from last weekend’s work, today I’m learning more about git, and the difference between Plumbing and Porcelain commands. The original intent was to use git tag -l freshports/$refname to detect if a tag exists. The problem there, it always returns 0. [dan@mydev:/var/db/ingress/repos/ports] $ git tag -l | head 10-eol 4-eol 5-eol 6-eol 7-eol
Processing commits on branches with git – part 2 Read More »
When upgrading packages on a FreshPorts ingress node (that is usually a jail which processes incoming commits and loads them into the database), I believe there is a possibility of interrupting commit processing. It’s a race condition between pkg removing a file and that file being required by the commit processing. This post serves to
The proper way to upgrade a FreshPorts ingress node Read More »
FreshPorts has three main daemons: ingress – waits for incoming commits and creates XML. freshports – processes the XML into the database. fp-listen – listens for events and clears cache The first two run on the backend (the ingress node, or jail), the last run runs on the webserver (nginx jail). The list of events
adding a new event to fp-listen Read More »