I went to work on a brilliant new idea for a FreshPorts feature and I immediately hit a snag on my dev system. I noticed that the package importing system had not run anything recently. The reason why was in the logs: In this post: FreeBSD 14.0 PostgresQL 16.1 py39-psycopg2-2.9.9 Python 3.9.18 First, why did […]
could not open certificate file “/root/.postgresql/postgresql.crt”: Permission denied 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 »
There is no solution here. I’m documenting for future such events. From time to time, I’ve been seeing this message in the logs: Today, I decided to look into why. In /var/log/freshports/freshports.log, I found: OK, so those are the repos which it thinks needs importing. Let’s pick one ABI and research FreeBSD:12:aarch64. Above that entry,
No repos need importing. How did this happen? This should never happen. Read More »
Today, the UI on the website was updated. The primary changes are to the home page and the date pages (i.e. lists of commits). I have purposely not cleared the cache. This should help you see the before and after images. For comparison, see today’s commits and the commits from Dec 16. This latest work
My thanks go out the AWS team who deal with the credits for open source projects. FreshPorts hit a big problem in Sep/Oct and I thought the project was going to have a non-trivial bill to pay. The main FreshPorts nodes are hosted on AWS – there are other nodes. Despite my own shortcomings (see
This was originally written in September 2018, but never published (for unknown reasons). I found it in the drafts section of the website today. In this post, you will see me change approach and not use a secondary table in one instance, but use multiple secondary tables in another. In one case, you will also
Using triggers to update a table with calculated values Read More »
I’m so very happy about recent changes to the website. It’s been a great day. I was volunteering at a flu shot clinic. A new coffee shop has opened up, and I was there before the clinic. After the clinic, it was walking the dog, then some serious changes to the the PostgreSQL queries which
Great changes to the websites Read More »
The front page of FreshPorts is about to change, slightly. At present, the front page contains only the the commits to the main branch of the FreeBSD. More precisely, it does not include: Commits to Mk/ or other similar non-port entities within the ports tree Commits to the quarterly branch (whatever the latest quarter is;
Displaying all ports tree commits on the front page Read More »
The SQL injection issues, at least all that I could find, are fixed. The first alert was on March 18th. That went out via: Twitter account status page a notice on the top of each page of the website See also FreshSource code fixes. Short version everything we know about is fixed we saw no
SQL injection issues fixed Read More »
In this post, I’ll talk about how someone was able to use SQL injection to spin up the database server to 100% utilization. I found the queries in the logs, duplicated the situation on dev, patched the code, and updated the website. See also SQL inejection issues fixed. In this post: FreeBSD 13.1 PostgreSQL server
FreshSource code fixes Read More »