This is mostly for my own future reference. I was looking at /categories.php and didn’t see the new filesystems category. I also note it does not sort by what it says it will sort. I eventually found it was loading data from this table: That’s all from 2017… 7 years ago. Grepping for the table […]
CategoryStatsUpdate and the category_stats table Read More »
I’ve updated the code (look for pseduo code in Welcome to the new category: filesystems) and now I’m ready to test that code. I have a copy of the database from before the commit. I’ve configured my test environment I can rollback the filesystem and get to a known good point. Am I doing this
Rerunning the filesystems commit to create the new category Read More »
Following on from yesterday’s blog post about the new filesystems category, today I hope to fix the code and get the website up to date again. At present, the code is spinning, trying to fetch category information using outdate code which assumes subversion is still in use. [16:46 dvl-ingress01 dvl ~freshports/message-queues/spooling] % ps auwwx |
Fixing the category creation code Read More »
A recent commit to the FreeBSD ports tree brought in a new category: filesystems See also the followup to this blog post: Fixing the category creation code This commit has been processed by FreshPorts, the results are only partially good. For example, this screenshot shows the deleted ports (moved from their old categories to the
Welcome to the new category: filesystems Read More »
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 »
Overnight, these messages appeared in the dev.freshports logs. This is not the first time this has happened. EDIT: 2024-02-18 – it was ZFS snapshot related. These directories each have a ZFS file system behind them. The cache is cleared by zfs rollback. My solution: destroy the snapshot I was rolling back to, change the permissions,
cache permissions are wrong; they were correct 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 front page of FreshPorts is about to change, slightly. At present, the front page contains only the the commits to the main branch of the FreeBSD. More precisely, it does not include: Commits to Mk/ or other similar non-port entities within the ports tree Commits to the quarterly branch (whatever the latest quarter is;
Displaying all ports tree commits on the front page Read More »
A long-standing bug, perhaps dating back to April 2003, has been fixed. It was an optimization in a trigger: if the values in the trigger have not changed, let’s not run the trigger. Turns out, that was a bad idea. The table The ports_categories table documents the connections between a port and the categories in
missing ports_categories entries 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 »