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 is a cheat sheet for FreshPorts behind-the-scenes administration. If you want one for users, please start with suggested content. Ingress Actions git-single-commit.sh – Take a commit from the repo and insert it into the database. Will fail if commit is already there. REPO is one of src, ports, doc. Hash is the git commit
FreshPorts cheat sheet Read More »
EDIT: update, I think I have solved this via help on IRC. See solution. I need help configuring Postfix. I am overwhelmed by the options available and I need to stay on track by working on the rest of the git changes. I have changed references to the FreshPorts domain. I’m using example.org instead. Background
Postfix help wanted Read More »
FreshPorts can display a single commit based upon commit id, which is based upon the Message-Id of the commit email (for subversion and cvs) or the commit hash (for git). Commit ids are specified in the URL. Cached entries are stored on disk and are named after the commit. It is because are are using
Changing cache file name for commits 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 »
My plan is to update the production website and database in place. To test this process, a copy of the production database has been copied to the pg02.int.unixathome.org PostgreSQL database server and is now available as freshports.dgnew. The first test was the database update process. I think I have that settled now. Pointing the devgit.freshports.org
Testing the database conversion process Read More »
The doc repo has moved from svn to git. This changeover occurred on 2020-12-09. The last svn commit was: 54737 The first git commit was: 3be01a475855e7511ad755b2defd2e0da5d58bbe To date, devgit.freshports.org has been using https://github.com/freebsd/freebsd-doc/ for processing commits. Today’s work will convert from that GitHub repo to https://cgit.freebsd.org/doc/ (actually, https://git.freebsd.org/). What changes are required The following changes
Moving devgit.freshports.org from GitHub to git.FreeBSD.org Read More »
Some blog posts serve to help me think through to a solution. This blog post is just for that. Today I realized the code needs to handle both git and svn. I thought I would have one cut-over date after which all commits would go through git. I see now that this isn’t the way
Processing git and svn on the same ingress node Read More »