Some updates that show up in the Web UI will go through the whole nine yards of downloading, extracting, and installing. It would appear that the updates were installed successfully. But when I click on "Check for updates" immediately after, the same set of components pops up that requires an update.... rinse and repeat.
I've found out that doing a "pkg update -f" then "pkg upgrade" in CLI would actually stop the cycle.... until the next time.
Right now, these are the usual suspects...
(https://i.imgur.com/SWTpGQP.png)
Is this just the nature of the beast or am I doing something wrong?
Anyone?
Do the fact that these components shows as "N/A" under Current version have something to do with it?
It's a known package manager incompatibility between the two third party repos you have set up on your end.
Cheers,
Franco
Quote from: franco on January 29, 2025, 05:18:44 PMIt's a known package manager incompatibility between the two third party repos you have set up on your end.
Cheers,
Franco
Appreciate the response.
So is this just cosmetic or am I setting myself up for a more serious problem down the road? Just saying, I'm fine doing the updates through CLI as long as these repos (which I need) play nice at the core.
Quote from: OrlyP on January 31, 2025, 02:05:41 AMas long as these repos (which I need) play nice at the core.
They don't. If it is just AdGuard Home you are after, there's a new repo by @mimugmail containing just that single plugin.
See: https://forum.opnsense.org/index.php?topic=44605.msg222740#msg222740