Today I updated the test ingress node of FreshPorts. Not long after, I was told by Nagios monitoring: I had a similar message comparing test to stage. Soon after, I saw this error in the logs: Oct 19 12:18:04 test-ingress01 dvl[12403]: FATAL eror with git-to-freshports-xml.py result: 1 – check git-delta.sh logs for more detail Looking […]
Based on the Add links to GitHub and GitLab mirrors for ports and commits request, the website has some new links arriving soon. Link to GitHub from each commit A similar link to GitLab Use the one you like. Each git web interface has it’s own followers. Also, while there, the commit hash at the
New links to GitLab and GitHub, in addition to the exist cgit.freebsd.org 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 »
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 »
Transitioning from subversion to git was both technically and personally challenging. During the COVID-19 pandemic there was a lot of work to carry out. A new server was created on AWS with a new layout and structure. For a few months it was nothing but my day job and FreshPorts in all my non-working hours.
Processing commits on branches with git Read More »
Hello, The changeover from subversion to git for the FreeBSD project enters it’s final stage about three hours from now (as I type this). At 3:01 UTC on Mar 31 2021, the repository will become read-only. The full schedule for that process is in the FreeBSD wiki. The first git commit is not expected until
FreshPorts will disable user login/updates on March 31 as part of transition to git Read More »
This documents the git specific code which I need to package and deploy. /usr/local/libexec/freshports This is installed by freshports-scripts-git, and I have the directory symlinked to ~/scripts on devgit.freshports.org for convenience. In this directory, we have the following symlinks to other directories: Ignoring lines 2 and 4 which are not relevant, we have this list
packaging up the git-specific code Read More »
This post documents the database upgrade process. Issues encountered during initial attempts There are permission issues on the database. Not everything is owned by the postgres super-user. In fact, many of them are owned by dan – this database is 20+ years old. To easily resolve the ownership issue, I take the database dump (named
git: database upgrade process Read More »
Just like I moved devgit.freshports.org from github to git.freebsd.org for the doc repo on Thursday, today (Monday), I’m doing the same thing for the src repo. The jail uses storage on an nvd-based zpool. First, create a new filesystem: [dan@slocum:~] $ sudo zfs create nvd/freshports/devgit/ingress/repos/src You can see it appear here in the jail, but
Moving to the FreeBSD git repo for src Read More »