Librem 13v3 on PureOS with updates through 12/27. Firmware also updated.
I have sporadically returned to modifying the Firefox apparmor profile, which allows universal ‘read.’ I decided to run: aa-complain, but apparently apparmor-utils was uninstalled. When I tried to run sudo apt install apparmor-utils yesterday to see why, I got the following (truncated output):
Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: apparmor-utils : Depends: python3-apparmor (= 2.12-4pureos1) but it is not going to be installed E: Unable to correct problems, you have held broken packages.
Going down the dependency thread using commands yields:
python3-apparmor : Depends: python3-libapparmor (>= 2.12) but it is not going to be installed python3-libapparmor : Depends: python3 (< 3.7) but 3.7.1-3 is to be installed
Using the show option for apt, on python3-libapparmor yields:
Package: python3-libapparmor Version: 2.12-4pureos1 Priority: extra Section: python Source: apparmor Maintainer: PureOS Maintainers <firstname.lastname@example.org> Original-Maintainer: Debian AppArmor Team <email@example.com> Installed-Size: 206 kB Depends: python3 (<< 3.7), python3 (>= 3.6~), python3:any (>= 3.3.2-2~), libapparmor1 (>= 2.10.95), libc6 (>= 2.14) Homepage: http://apparmor.net/ Download-Size: 83.1 kB APT-Sources: https://repo.puri.sm/pureos green/main amd64 Packages Description: AppArmor library Python3 bindings python3-libapparmor provides the Python3 module that contains the language bindings for the AppArmor library, libapparmor, which were autogenerated via SWIG.
Note the "Depends" list. That update on 12/20, which uninstalled apparmor-utils, upgraded python3 to 3.7. I believe this dependency ultimately breaks apparmor-utils.
Isn't "dependencies" #1 on the list of promotion to green? Should that not work both ways? I must have been really unthinking and careless that morning to do this one.
I do not think it is relevant, but I am attaching the dpkg.log for 12/20.
I only have one other repository for the OpenCPN package, but there have been no updates to it in a long while. I do untar Firefox and Thunderbird to /opt. The latter has been in buster but not in green. I do not think these are contributing to the problem.
If one looks at python3-libapparmor in buster, one will see that the python dependency is <<3.8. Unfortunately, this package is modified in PureOS and belongs to Purism.