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 »
I’m writing this post just to keep things straight in my head so I can decide how best to resolve this issue. FreshPorts uses /var/db/freshports/cache/spooling on both the ingress jail and the nginx jail. The nginx jail uses it for caching content. Page details are first spooled into /var/db/freshports/cache/spooling before moving it to /var/db/freshports/cache/ports. The
I have a spooling directory issue to fix Read More »
Yesterday I copied data from the old production server to the new production server. One thing I missed, but did think about at the time, was updating the sequence used by the table in question. Looking at the table definition: The report_log_id_seq value will be wrong. When the reports run, they will use values for
Fixing a sequence value Read More »
After enabling the report notifications yesterday, they failed to go out. Why? A hardcoded hostname in a Perl module. Here are the errors I found this morning. from=’FreshPorts Watch Daemon <FreshPorts-Watch@FreshPorts.org>’ to=’dvl@example.org’ subject=’FreshPorts daily new ports’ could not open Email::Sender. from=’FreshPorts Watch Daemon <FreshPorts-Watch@FreshPorts.org>’ to=’dvl@example.org’ subject=’FreshPorts daily new ports’ errorcode=’unable to establish SMTP connection to
Mail sending failures Read More »
Earlier today I copied data from the old server (supernews) to the new server (x8dtu). Now that the database has the correct information regarding when reports were last sent out, we can begin to enable those reports. The work has already been done to move the reports from cronjobs into periodic scripts. For our purposes,
Enabling report notifications on the new server Read More »
Ever since the new server went into production, sometime in 2017, the notification emails, which tell you what has changed, have been coming from the old server. I never did that changeover. The old server was still processing incoming commits, so the notifications were accurate. However, new accounts would not get notifications and changes to
Moving the email notifications to the new server Read More »