github ivan-hc/AM 8.3.2
"AM" 8.3.2

latest releases: 9.9.2, 9.9.1, 9.9...
15 months ago

Stop pretending that Ubuntu is a "canonical" GNU/Linux distro!

The recent changes that Canonical has imposed on Ubuntu, leads to the failure of some applications, and not only those supported by "AM"/"AppMan", even Flatpaks are affected! The more efficient and flexible Bubblewrap in the first place, being an essential resource for all these projects, fails because of the restrictions imposed in AppArmor in Ubuntu 23.10+.

They say that "Ubuntu Desktop firmly places security at the forefront, and adheres to the principles of security by default" (source), when in fact all they do is force the use of Snaps, "inexplicably" breaking the normal functioning of other alternative package formats!

For this release, @Samueru-sama added a warning in case your distribution adds restrictions to Linux namespaces.

Istantanea_2024-10-14_03-52-21

Unlike the previous release, the message will not block the use of "AM"/"AppMan", but the message will always be shown to remind you that, in case you have problems running programs, and in particular for those that use Bubblewrap, the fault is Ubuntu, or rather, the way the permissions have been set.

Instructions for working around this problem are available in this section of the README https://github.com/ivan-hc/AM#ubuntu-mess

See also this interesting discussion at linuxmint/mint22-beta#82.


Personal considerations

Spoiler

Again, a release that aims to suppress the wrongs of others. Today in particular, the github actions workflows based on "ubuntu-latest" on about 50 AppImage packages managed and distributed by me have all failed because of this change (see screenshots below).

Istantanea_2024-10-13_18-51-24 png Istantanea_2024-10-13_18-58-23 png

I had to downgrade the runners to "ubuntu-22.04" in all my repositories dedicated to "Archimage" packages to bypass the problem, also because setting up containers did not work.

The "releases" section is becoming the "blog on a developer's discomfort" rather than a section where to expose short tutorials on how to deal with new versions. I'm sorry for that.

If on the one hand adding warning messages does not make this a release, on the other hand there is the danger that other people's projects on which many other projects are based, risk being demolished, both work-wise and media-wise.

What should an amateur developer do to work peacefully? I don't know.


What's Changed

Full Changelog: 8.3.1...8.3.2

Don't miss a new AM release

NewReleases is sending notifications on new releases.