After updating to 26.1.3, I see the following errors when I check for updates:
pkg: glib-bootstrap has a missing dependency: python311
pkg: glib has a missing dependency: python311
Everything is working correctly but I am not using IPS/IDS.
Mimugmail repo items installed?
If the answer is yes then things will be fixed once Michael rebuilds everything against the new python version.
Yes, that is it. Thanks.
Already reached out to him.
Cheers,
Franco
Thanks Franco.
Hej Franco,
have you heard anything from Michael yet? The new version of Python is still not supported.
I don't know if that has anything to do with it: The update check for Adguard Home is no longer working...
Thanx Emmitt
Works like a charm here. Are you running anything but AGH from Michael's repo? If you don't, consider switching to his newer "Just AGH" repo instead of the full one.
Thanks Patrick. Yeah, I only use AdGuard. Can I just add the new repository, or do I need to uninstall AdGuard first?
After doing a little research, I managed to fix it. Just remove the old repo and install the new one.
The error (python311) is now gone — though the update check error remains.
And another oddity: I already have version
v0.107.73 installed. But the plugin changelog says
1.16
* Update to 0.107.67
Quote from: emmitt on April 14, 2026, 08:19:06 PMThe update check for Adguard Home is no longer working...
Probably a temporary network issue, unrelated to python 3.11.
There's nothing to check for really as long as there's no new release on GitHub
Quote from: Patrick M. Hausen on April 14, 2026, 08:51:28 PMWorks like a charm here.
This is weird...for how long exactly is it working without the py311 warning Patrick?
Heard late last week that mongo was fighting python3.13 via Franco — and I'm wondering if Michael's found a solution and only published it for the dedicated AGH repo only——as there could be other python3.13 issues to fix or waiting to be fixed in the full repo (?)
Quote from: emmitt on April 14, 2026, 11:09:16 PMI already have version
v0.107.73 installed. But the plugin changelog says
1.16
* Update to 0.107.67
That's expected. Michael only updates AGH once in a while. From that moment onwards you'll rely on the AGH update feature until lightning strikes again
Quote from: newsense on April 15, 2026, 09:25:33 AMThat's expected. Michael only updates AGH once in a while. From that moment onwards you'll rely on the AGH update feature until lightning strikes again
Hej, and thanks for your reaction. But under the "old" repository, the changelog showed the latest update (the one I have installed). So there are differing changelogs. Of course, that's not a problem, but it's interesting
Quote from: newsense on April 15, 2026, 09:22:00 AMThis is weird...for how long exactly is it working without the py311 warning Patrick?
I feel the same way. On the one hand, I'm glad the message no longer appears, but what exactly has changed with the installation of the new repo?
You don't pull in packages from a third party repo that conflict with OPNsense's. The FreeBSD pkg framework is not well suited to dealing with multiple inconsistent repositories. But to be fair, neither is apt. Configuring a third party PHP repo on your Debian or Ubuntu is a good way to disaster hitting you at the next major version upgrade.
So there are packages depending on python and (at least) one of the packages is in both - Michael's and OPNsense's - repository. And in the OPNsense repo that package depends on python 3.13 and in Michael's it depends on python 3.11 - kaboom!
The "just AGH" repo by Michael solves that problem because it contains only a single package, namely AdGuard Home, which is a statically linked binary written in golang without any other dependencies that could cause a conflict.
HTH,
Patrick
I have only AGH and htop from mimugmail repo, and as far as I remember htop was a clean install with no other dependencies...
In any case, thanks for the hint about the dedicated repo. I'll try it over the weekend and see if there are any issues come 26.1.7 if htop is orphaned for a while
Michael is strugging with updating his repos with a newer Python version because his build also needs mongodb80 and since that particular FreeBSD version in the ports tree wasn't updated in half a year it doesn't build with Python 3.13 at all. The latest versions of 8.0 don't even need Python (to build) anymore. Bummer.
Cheers,
Franco
MongoDB and Python are not the greatest things to have a dependency on to be honest...
I wish him all the luck in the world with the fixing process !!! :)