What’s in the pipeline, how it works, how it’s made…
The plan for today was not decided until after I got out of bed. I sat down with coffee and looked through the list of tasks. I found one which appealed: monitor the cache_clearing_ports & cache_clearing_dates tables This is part one of a two-part story. The first part deals with fixing a database table before […]
Changing a column type Read More »
FreshPorts had a cache clearing issue recently. It lingered. For a long time. It took me a while to figure it out. It turned out to be a Python 3 compatibility issue. In this post: PostgreSQL 12.1 FreeBSD 12.1 I will outline how database changes invoke external scripts asynchronously which then clear the cache. I
Cache clearing issue Read More »
I’ve noticed a log of sanity test failures related to devel/binutils lately. Every single commit. Issue 133 deals with that. Here, I plan to document what happened. FreshPorts has, since inception, worked off the commit emails. The incoming email is parsed and XML created. The XML is then used to update the database. I started
The slave ports for devel/binutils did not get deleted Read More »
The website has been slow for some time. I think it is because of increased disk-io. In this post: FreeBSD 12.0 PostgreSQL 11.5 LibreNMS does the graphs via SNMP The diskio overall By increased, I mean it has gone from about 0.1k to about 1.6k, peaking to 140-150. This is steady and persistent. This graphs
Website slowness – the investigation Read More »
I was just creating a new jail for working on git & FreshPorts. I was intrigued to see that iocage uses send | receive to create the new jail: [dan@slocum:~] $ ps auwwx | grep iocage root 64166 3.7 0.0 12788 4036 1 D+ 21:16 0:06.10 zfs send system/iocage/releases/12.0-RELEASE/root@git-dev root 64167 2.8 0.0 12752 4036
Creating the first FreshPorts git-specific jail Read More »
We have the first commit process via git into FreshPorts. Details in this git comment. Work remaining: check out that commit into the working copy of the files run make -V on the working copy to get the refreshed values for the port[s] affected by this commit The 2nd part – very little code change.
first commit process via git Read More »
I want to move FreshPorts towards using commit hooks and away from depending upon incoming emails for processing new commits. Much of the following came from a recent Twitter post. You might think: why are we using emails? Why? Because we can. They were the easiest and most simple approach. It is a time-proven solution.
Moving towards commit hooks Read More »
I’m trying to think of a list of things that FreshPorts can do which might be useful. I can think of these: provides example dependency line. e.g. p5-XML-RSS>0:textproc/p5-XML-RSS list of dependencies for a port list of ports depending upon this port Default configuration options what packages install a given file (e.g. bin/unzip) what ports does
Things you didn’t know FreshPorts can do Read More »
When the time comes, and the FreeBSD project is using git, there will be work to be done on FreshPorts. If the commit emails are similar to those under cvs and svn, it should be straight forward to parse the email and convert it to XML. Once the data is in XML, the commit can
git and FreshPorts Read More »
Today I updated the test website with two changes: use of dd, dt, and dl tags in the details section of the ports page Three new graphs: doc ports src The tags part was all the result of me reading up on them and concluding they could be useful. The graphs were swills’ fault. They
HTML and graph changes Read More »