glib missing dependency after update to 26.1.3

[julsssark]

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.

[newsense]

Mimugmail repo items installed?

If the answer is yes then things will be fixed once Michael rebuilds everything against the new python version.

[julsssark]

Yes, that is it. Thanks.

[franco]

Already reached out to him.


Cheers,
Franco

[julsssark]

Thanks Franco.

[emmitt]

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

[Patrick M. Hausen]

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.

[emmitt]

Thanks Patrick. Yeah, I only use AdGuard. Can I just add the new repository, or do I need to uninstall AdGuard first?

[emmitt]

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

[newsense]

The 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

[newsense]

Works 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 (?)

[newsense]

I 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

[emmitt]

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

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

[emmitt]

This 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?

[Patrick M. Hausen]

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