Shortly after moving the jail dvl-ingress01 from Python 3.11 to Python 3.12, I started seeing these messages: The code in question ( link to source) is This should be easy enough to replace, knowing python. First, reproduce the problem With any change to fix a problem, I must first be able to reproduce the problem. […]
This post is a work-in-progress. This paragraph will be removed when it is completed. This post is mostly for my own benefit. It will track the redesign of process_vuxml.pl which follows on from How FreshPorts processes vuxml entries. In that previous post, defects were identified and a proposed change put forth. In this post, I’ll
The new process_vuxml.pl Read More »
Yesterday, a Facebook memory reminded me of an old issue with FreshPorts: serial values which are about to overflow. This is where you may be thinking? serial? In this day? You might also think, why serial? Why not UUID. Keep thinking about that. Some of the tables we’re talking about were designed 20+ years ago.
Converting from int to bigint and from serial to identity Read More »
Just so you know, there is no conclusion to this story. The cause is still not known. However, I have some ideas to track it down and a follow-up blog post is underway. In short: All src commits gave errors – this was reproducible, and has been fixed When an error occurs, it’s not the
Updating to Perl 5.40 on FreeBSD 14.2 Read More »
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 »