This is another post in the FreshPorts-git series. Yesterday was good progress. This morning (at Sat Jul 4 13:05:10 UTC 2020) I manually initiated another import of commits from git. It looked like this: This created one XML file for each git commit. The files are dropped into the ~freshports/messages-queues/incoming directory. The freshports-git daemon (well, […]
Manual initiation of git commit processing Read More »
I’m documenting this as a go along because I’m sure I’ll be doing something that I later wish I had written down. Create the repo This creates a FreeBSD git-based port repo. echo git clone https://github.com/freebsd/freebsd-ports.git /var/db/freshports/ports-jail/var/db/repos/PORTS-head-git | sudo su -l freshports The latest local commit This tells us the hash of the latest commit
Setting up a FreeBSD ports git repo for FreshPorts usage Read More »
Recently, a new use of ZFS snapshots was introduced for a cache on FreshPorts. This approach involves creating a snapshot on the empty cache, then rolling back to that snapshot when the cache needs to be cleared. This idea came from this Tweet after much discussion on how to properly and safely delete directory contents
ZFS when you’re not doing ZFS Read More »
git is coming to FreeBSD. The initial FreshPorts work for git started in September, then was abandoned for unknown reasons. It just fell off the RADAR. This week, it came back to my attention. References Some of the initial research was over Twitter. I’m saving those references here for future reference. The Tweet about the
git – the next FreshPorts project Read More »
How long does it take for a new repo to come online. FreshPorts does not have a lot of stats yet, but here is what we have today: Roughly, it’s every two days. The value in repo_date is taken from packagesite.txz as found at https://pkg.freebsd.org/FreeBSD:12:amd64/latest/ for example. What are inserts, updates, deletes? inserts: The number
How often is a new repo available? Read More »
I noticed this today: root 58697 0.0 0.0 10680 2180 – IJ 12May20 0:00.00 /usr/local/bin/readproctitle service errors: …/site_perl/FreshPorts/vuxml_parsing.pm line 232, chunk 1.\nWide character in print at /usr/local/lib/perl5/site_perl/FreshPorts/vuxml_parsing.pm line 232, chunk 1.\nWide character in print at /usr/local/lib/perl5/site_perl/FreshPorts/vuxml_parsing.pm line 232, chunk 1.\nUndefined subroutine &FreshPorts::CommitterOptIn::RecordErrorDetails called at ./process_vuxml.pl line 124, chunk 1.\n I should monitor that process better.
On Sunday, the packages project was moved into production. This project was both fun and challenging. The goal: within 1 hour of the repo being updated, FreshPorts has the packages imported and updated for your viewing pleasure. Today, I went checking to see if a repo update had occurred. An issue was found and corrected.
Packages – now in production Read More »
When a new repo is imported, the packages cache needs to be deleted. The cache is on the front-end, the web server. Cache clearing on the web server is handled by the fp-listen daemon. It does this by using the LISTEN command. The list of channels it listens to is controlled by the listen_for table:
Clearing the packages cache Read More »
Today, while I wasn’t looking, both dev and test located and imported new package information for: FreeBSD:11:amd64 FreeBSD:11:i386 FreeBSD:12:amd64 FreeBSD:12:i386 FreeBSD:13:amd64 FreeBSD:13:i386 However, the packages table was not correctly updated. Why? Because I lost some function code I wrote. This is the code which was in use, as mentioned in Using DEFERRABLE INITIALLY DEFERRED on
Found new repo release – automatically imported it Read More »
A new FreshPorts features is being developed. I’m trying to determine if packages for a port can be cached separately from the port itself. I will explain. When you visit a port page, if it’s not cached, the page is built and then cached. Not the whole page, just the parts pertaining to that port.