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 […]
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 »
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 »
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 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 »
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 »
With today’s work on Processing commits on branches with git, good progress was made. You can see commits on the quarterly branch (not up to date, because it’s not yet automated). You can see the port on the quarterly branch, if there’s a commit on the branch. Want to see a particular commit on a
Quarterly branches: what’s next? 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 »