Date: Wed, 07 Sep 2022 13:20:01 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 266270] freebsd-update cron corrupts freebsd-update upgrade's in progress Message-ID: <bug-266270-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D266270 Bug ID: 266270 Summary: freebsd-update cron corrupts freebsd-update upgrade's in progress Product: Base System Version: 12.3-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: misc Assignee: bugs@FreeBSD.org Reporter: pen@lysator.liu.se I've been running "freebsd-update cron" from cron every night at 23:10 to g= et notifications for needed updates for a long time. This is working fine. What isn't working fine is I've I initiate an OS upgrade using "freebsd-upd= ate upgrade -r <new version>" before the cron job runs, and then finalize the upgrade after the cron job has run... Which for me has happened multiple ti= mes now since that is a good time to perform the upgrades :-) This seems to cause a partially updated system that is very confused - which causes future pkg upgrade and "freebsd-update fetch install"-updates to bec= ome even more confused (sometimes starts to delete "random" files from the runn= ing system since it thinks they aren't needed anymore). One way I've noticed to detect this situation is to do a "file /usr/bin/una= me" and see what OS version the uname binary is from. Suggestion: Add some fail safe mechanism to "freebsd-update cron" that dete= cts an OS-upgrade in progress and stop it from downloading updates for the old = OS version and mix them up with the new OS updates. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-266270-227>