This post is mostly me putting thoughts down as I work through this problem. As part of fixing a recent issue, I want to manually trigger the importing of a new package repo into FreshPorts. The check for new repos is performed by this periodic script: Aug 17 01:00:06 dvl-ingress01 FreshPorts[80429]: into /usr/local/etc/periodic/hourly/900.freshports-check-repos-for-new-builds That shell […]
Manually triggering a package import Read More »
There is no solution here. I’m documenting for future such events. From time to time, I’ve been seeing this message in the logs: Today, I decided to look into why. In /var/log/freshports/freshports.log, I found: OK, so those are the repos which it thinks needs importing. Let’s pick one ABI and research FreeBSD:12:aarch64. Above that entry,
No repos need importing. How did this happen? This should never happen. Read More »
The packages_raw gets reloaded. A lot. Every time a new set of packages is available from the FreeBSD packages table, data gets deleted and reloaded. So I manually vacuum the table. Well, it’s automated, as part of the code, but it doesn’t wait for the daily scripts. I was seeing these errors on server r720-02:
Fixing permissions on the packages_raw table Read More »
This post is related to a recent tweet. It was months ago that I wondered why one port installed another as a dependency. I could see no link. Since it FreshPorts ports, earlier this week I did some testing: I removed the package, and it’s own dependencies from dev, then test, and finally stage. Monitoring
Removing unneeded packages Read More »
By request FreeBSD 14 is being added to the list of build packages. Looking at the main freebsd pkg mirror, we can see FreeBSD:14 is listed. These are the items in question: FreeBSD:14:i386 FreeBSD:14:amd64 FreeBSD:14:aarch64 FreeBSD:14:armv6 FreeBSD:14:armv7 FreeBSD:14:mips FreeBSD:14:mips64 FreeBSD:14:powerpc64 The SQL is: But why type all this, code it. Which produces: [dan@pg02:~/bin] $ sh
Adding FreeBSD14 to the list of build packages 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 »
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 »
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 »