This morning I was created with 6 emails, all announcing FAILED: MASTER_PORT, one for each FreshPorts node. Each was sent at 5AM (1000 UTC). Something happened which upset every one of them. I have no idea why. However, I’m writing this down for future reference. This announcement came from one of the many system checks […]
FAILED: MASTER_PORT Read More »
I used to think branches were simple when it came to FreshPorts, but I was wrong. Consider slave ports for example. If we get a commit for databases/mariadb100-server, we have to update the slave ports, but only the slave ports on the branch, not the slave ports on head. That sounds easy enough, but keep
Branches are simple, but more complex than head Read More »
Recently, I wrote about using a jail to get better results. Today, I’m altering the scripts so they make use of this jail. For the most part, this will involve the creation of scripts that will run in the jail and duplicate the functionality of the existing FreshPorts code. What needs to be changed? I’m
Altering scripts to use the jail Read More »
Today I noticed a problem with my development machine. It has been in storage for about a month. Yesterday it started processing FreshPorts emails again. Overnight, I noticed a strange error which I could not follow: Unusual System Events =-=-=-=-=-=-=-=-=-=-= Dec 31 20:33:11 ngaio FreshPorts[93781]: error executing make command for sysutils/rsyslog-mysql: This command (FreshPorts code
Out of date ports tree Read More »
Back in August, I wrote about patching the ports tree to cater for master/slave relationships. I am happy to report that this patch is no longer required. Instead of MASTERPORT, as provided by that patch, I can use MASTER_PORT, which is now part of the stock ports/Mk/bsd.port.mk. \o/ No more patching.
No more patching for MASTERPORT Read More »
At present, master/slave relationships in FreshPorts are not stored optimally. Each port has a field, master_port, which contains the category/port of its master_port, otherwise, it is an empty string. The ideal situation would be a table such as this: create table master_slave ( master_port_id integer not null, slave_port_id integer not null, primary key (master_port_id, slave_port_id)
Master/slave relationships Read More »
MASTERPORT is a tool Mark Linimon and I have used for a while. It seems to have entered into common usage now. freshports.org=# select master_port, category, name from ports_active where master_port like ‘/%’ order by category, name; master_port | category | name ———————————————–+————–+————————— /usr/home/dan/ports/devel/ocaml-camlidl | archivers | ocaml-zip /usr/home/dan/ports/devel/ocaml-camlidl | graphics | ocaml-lablgl /usr/home/dan/ports/japanese/kinput2-freewnn/ |
MASTERPORT : who uses it? Read More »
As reported by sem@, there is a problem with the display of master/slave relationships within FreshPorts. The relationship is stored in the ports table, with the master_port attribute being a pointer to the master port. This text field typically has values such as this: freshports.org=# SELECT DISTINCT(master_port) freshports.org-# FROM ports_active freshports.org-# where master_port ” freshports.org-#
master / slave relationships Read More »
Caching to disk, at least for ports, is now implemented. I didn’t plan to moved a new feature into production on the day before I leave for a conference, but it happened. If you notice that the website has not been updated after a port has been committed, please let me know. That will indicate
Caching To Disk – implemented Read More »
A user recently asked if we could show the size of the port/package. Getting the size of the distfiles is relatively easy. It’s in the distinfo file. For slave ports, we already know the master port, so we get the information from there. It might also be nice to show the size of the package.
How much is that distfile in the port? Read More »