freebsd-update loop 15.1-RELEASE-p6

J

joe81tx

I have freebsd-update cron run every day. I received an email yesterday about 15.1-RELEASE-p6 which I installed. Then today I got another email about the same patch:
src component not installed, skipped
Looking up update.FreeBSD.org mirrors... 3 mirrors found.
Fetching metadata signature for 15.1-RELEASE from update1.freebsd.org... done.
Fetching metadata index... done.
Inspecting system... done.
Preparing to download files... done.
The following files are affected by updates. No changes have
been downloaded, however, because the files have been modified
locally:
/etc/ssl/cert.pem
The following files will be removed as part of updating to
15.1-RELEASE-p6:
/etc/ssl/certs/406c9bb1.0
/etc/ssl/certs/4b718d9b.0

I deleted /etc/ssl/cert.pem, ran freebsd-update fetch, then freebsd-update install and everything succeeded without any errors. But running freebsd-update fetch again still prompts:
The following files are affected by updates. No changes have
been downloaded, however, because the files have been modified
locally:
/etc/ssl/cert.pem
(END)

The following files will be removed as part of updating to
15.1-RELEASE-p6:
/etc/ssl/certs/406c9bb1.0
/etc/ssl/certs/4b718d9b.0
(END)

I fear I will keep getting the same email every day.
 
Is /etc/ssl/cert.pem expected to remain static or is it something that may get updated as certs are added or removed? If one cat's it, it looks like a "bundle"
 
I am experiencing exactly the same thing. I receive updates via freebsd-update.

freebsd-version
15.1-RELEASE-p6

freebsd-version -kru
15.1-RELEASE-p5
15.1-RELEASE-p5
15.1-RELEASE-p6

uname -a
FreeBSD super.secret.hostname 15.1-RELEASE-p5 FreeBSD 15.1-RELEASE-p5 releng/15.1-n283639-893c7c99b60d GENERIC amd64

head -n1 /etc/motd
FreeBSD 15.1-RELEASE-p5 (GENERIC) releng/15.1-n283639-893c7c99b60d

head -n1 /var/run/motd
FreeBSD 15.1-RELEASE-p5 (GENERIC) releng/15.1-n283639-893c7c99b60d

uname and motd continue to show -p5 following reboot.
 
jaz85 said:
I am experiencing exactly the same thing. I receive updates via freebsd-update.

freebsd-version
15.1-RELEASE-p6

freebsd-version -kru
15.1-RELEASE-p5
15.1-RELEASE-p5
15.1-RELEASE-p6

uname -a
FreeBSD super.secret.hostname 15.1-RELEASE-p5 FreeBSD 15.1-RELEASE-p5 releng/15.1-n283639-893c7c99b60d GENERIC amd64

head -n1 /etc/motd
FreeBSD 15.1-RELEASE-p5 (GENERIC) releng/15.1-n283639-893c7c99b60d

head -n1 /var/run/motd
FreeBSD 15.1-RELEASE-p5 (GENERIC) releng/15.1-n283639-893c7c99b60d

uname and motd continue to show -p5 following reboot.
Click to expand...
Because patch 6 did not update the kernel uname and motd will not update. Only the userland (-u) was updated with p6, so the kernel (-k) and running kernel (-r) as reported by freebsd-version will not change.

I ran the command below and then freebsd-update cron did not send an email so hopefully manually removing those two files will help me avoid the daily loop.
mdo rm -f /etc/ssl/certs/406c9bb1.0 /etc/ssl/certs/4b718d9b.0
 
joe81tx said:
Because patch 6 did not update the kernel uname and motd will not update. Only the userland (-u) was updated with p6, so the kernel (-k) and running kernel (-r) as reported by freebsd-version will not change.

I ran the command below and then freebsd-update cron did not send an email so hopefully manually removing those two files will help me avoid the daily loop.
mdo rm -f /etc/ssl/certs/406c9bb1.0 /etc/ssl/certs/4b718d9b.0
Click to expand...
But problem with freebsd-update exist still. How long it will be not solved? It is the second time that we users of freebsd-update have a problem.
 
You must log in or register to reply here.
Back
Top