What’s in the pipeline, how it works, how it’s made…
x8dtu contains two jails for database servers: x8dtu-pg01 and x8dtu-pg02. At any given time, one is the production database server, and contains the IP address 127.1.54.32. Let’s assume x8dtu-pg02 is on PostgreSQL 10.6 and we are upgrading to PostgreSQL 11.1 on x8dtu-pg01 The new packages would be installed on x8dtu-pg01. pg_dump would be run on […]
Moving the production database server IP address Read More »
I originally documented this so I would have a reference while tracking down the problem. I have since solved the issue and you can jump to the bottom of this post to find the solution. What I do not know is why this was not an issue under PostgreSQL 10.6 but was under PostgreSQL 11.1.
procedure OK under 10.6 but starts acting up under 11.1 Read More »
From IRC: [Oct 05 22:41] zi: we have conflict matches: https://dev.freshports.org/security/openssl/ [Oct 06 09:08] dvl: cute. possible to add in a clickable link to take you to that matching port? :) [Oct 06 10:50] zi: That matching port, it’s just a package name, sometimes there is a matching port, sometimes there is not… But yeah,
Getting a link from a package name Read More »
Today I updated the fp-listen and freshports daemons. These are the scripts which invalidate the cache and process incoming commits, respectively. No code changes were made, just the installations directories. Previously, this code when into /var/service but now they go into /usr/local/libexec/freshports-service and I create a symlink from /var/service as as required. This confirms to
fp-listen and freshports daemons updated Read More »
This post serves two goals: document the CONFLICTS implementation within FreshPorts show how you can use triggers to update a secondary table The FreeBSD ports tree / package collection has a method for resolving conflicts. This feature allows a port maintainer to specify what, if any, packages conflict with a given port. The reasons why
Adding and populating CONFLICTS Read More »
Sorry, this is a placeholder. Or better put, a redirect. Please read Perl @INC – customizing it for FreeBSD for details.
Upgrading from Perl 5.24 to 5.26 causes FreshPorts scripts to fail Read More »
Jochen Neumeister noticed that FreshPorts no longer lists phpunit6. see also https://github.com/FreshPorts/freshports/issues/72. Sure enough, I went searching and failed to find it. It did not turn up. Then I checked Include deleted ports, then clicked on Search again. Ahh, there it it. Sure enough, it is marked as deleted. Look for the small icon at
Where did phpunit6 go? Read More »
For several weeks, FreshPorts had a vuxml processing problem. In this blog post, I will share what I found. Introduction Incoming events for FreshPorts are handled by a small Python script which checks for flags and incoming commits. This ensures that work is carried out serially because parallel work can have unintended consequences. After each
Details of the vuxml processing problem Read More »
The previous post on this blog was nearly 10 months ago. However, things have not stood still. There have been a few issues fixed and some are still in progress. The biggest thing underway is a major rework of the backend, the part that processes the incoming commits. There is nothing major; no huge code
Redesign of FreshPorts backend Read More »
Committing to a branch (e.g. 2016Q4) when the port in question has slave ports is getting tricky, especially if the port was added after the branch was created. Case in point, www/linux-c7-flashplugin11 was added to the tree on 19 Oct 2016. The 2016Q4 branch was created on 3 Oct, and therefore that port does not
Committing to a branch when there are slave ports Read More »