FreeBSD13, pkg quarterly to latest then "expat: 2.4.3 -> 2.4.2"

  • Thread starter Thread starter Deleted member 65380
  • Start date Start date
D

Deleted member 65380

Guest
FreeBSD13, I changed pkg from quarterly to latest then had a package downgrade "expat: 2.4.3 -> 2.4.2"

Seems peculiar, anyone noticed this before?
 
This would currently only be possible if either your pkg databases are broken (pkg update -f to fix) or you're on aarch64, where the "latest" pkg repo isn't rebuilt yet (which is pretty transparent from freshports).
 
Code:
-rw-r--r--  1 root  wheel  436 Feb 10 22:23 /usr/local/etc/pkg/repos/FreeBSD.conf

pkg: Repository FreeBSD has a wrong packagesite, need to re-create database

because of the stupid "candidates" number:

pkg install -f ca_root_nss checkrestart expat libevent libnghttp2 pkg unbound


messages:Feb 10 22:33:11 freebsd-dns pkg[71119]: expat downgraded: 2.4.3 -> 2.4.2
messages:Feb 10 22:33:12 freebsd-dns pkg[71119]: libevent reinstalled: 2.1.12 -> 2.1.12
messages:Feb 10 22:33:12 freebsd-dns pkg[71119]: libnghttp2 reinstalled: 1.46.0 -> 1.46.0
messages:Feb 10 22:33:17 freebsd-dns pkg[71119]: pkg reinstalled: 1.17.5 -> 1.17.5
messages:Feb 10 22:33:18 freebsd-dns pkg[71119]: ca_root_nss reinstalled: 3.74 -> 3.74
messages:Feb 10 22:33:18 freebsd-dns pkg[71119]: checkrestart reinstalled: 0.5.0_1 -> 0.5.0_1
messages:Feb 10 22:33:20 freebsd-dns pkg[71119]: unbound reinstalled: 1.14.0 -> 1.14.0

it's now 11pm
 
raspberry pi

pkg repo isn't rebuilt yet (which is pretty transparent from freshports).

(which is pretty transparent from freshports)

What do you mean? It doesn't make sense that it (expat) would be a lower version than it's older self.
 
Look at the "packages" table on freshposts, hover over the individual cells for more info. So, yes, you're on aarch64. Then just wait until the "latest" repo is rebuilt.
 
I recommend to use quarterly on aarch64 rather than latest.
There are a lot of packages in latest which are actually a lower version than in quarterly.

Since aarch64 is officially Tier 1, this is not acceptable.
This should only be a very short-term situation on any architecture. But a repo build date of 2022-01-26 for "latest" looks like there might be a problem right now...
 
I recommend to use quarterly on aarch64 rather than latest.
I literally just wanted to try FreeBSD latest on something... wasn't expecting it to be messy. I don't literally need latest and can revert to quarterly easily enough.
 
It was built when 13.0-RELEASE came out and hasn't been updated since.
That's pretty much impossible, e.g. expat 2.4.2 (which is currently in that repo) hit the ports tree on 2021-12-27, so long after release of FreeBSD 13.

But still, the repo is pretty old currently (2022-01-26). Something seems to be "stuck".
 
Ok, so it's a recurring problem, but it isn't "completely stuck", see above (repo creation date is now 2022-01-26).

Looks like *some* technical problem with the builders?
 
If I recall correctly it's due to failing hardware. But I'm not sure if that's still the case, it was in the past.
 
it is quite possible some technical issues, but I only judge by observing no updates in 13:amd64/latest for last 8 days, which is longer than usually observed before ( longest in my recollection )
 
Back
Top