packages

No repos need importing. How did this happen? This should never happen.

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 »

Adding FreeBSD14 to the list of build packages

By request FreeBSD 14 is being added to the list of build packages. Looking at the main freebsd pkg mirror, we can see FreeBSD:14 is listed. These are the items in question: FreeBSD:14:i386 FreeBSD:14:amd64 FreeBSD:14:aarch64 FreeBSD:14:armv6 FreeBSD:14:armv7 FreeBSD:14:mips FreeBSD:14:mips64 FreeBSD:14:powerpc64 The SQL is: But why type all this, code it. Which produces: [dan@pg02:~/bin] $ sh

Adding FreeBSD14 to the list of build packages Read More »

Found new repo release – automatically imported it

Today, while I wasn’t looking, both dev and test located and imported new package information for: FreeBSD:11:amd64 FreeBSD:11:i386 FreeBSD:12:amd64 FreeBSD:12:i386 FreeBSD:13:amd64 FreeBSD:13:i386 However, the packages table was not correctly updated. Why? Because I lost some function code I wrote. This is the code which was in use, as mentioned in Using DEFERRABLE INITIALLY DEFERRED on

Found new repo release – automatically imported it Read More »

If packages and ports are cached separately, how is one included in the middle of the other?

A new FreshPorts features is being developed. I’m trying to determine if packages for a port can be cached separately from the port itself. I will explain. When you visit a port page, if it’s not cached, the page is built and then cached. Not the whole page, just the parts pertaining to that port.

If packages and ports are cached separately, how is one included in the middle of the other? Read More »

Scroll to Top