Extend apparmor policy for org.gtk.vfs

Signed-off-by: Pulluri Shirija Pulluri.Shirija@in.bosch.com

infrastructure/apertis-issues#26 (closed)

added 1 commit

• 140cb0ae - Extend apparmor policy for org.gtk.vfs

Compare with previous version

requested review from @sudarshan

requested review from @refi64 and removed review request for @sudarshan

I'm sure that @refi64 will review this and provide his feedback. While checking this I just noticed that the MR is targeting v2021-updates, which is a bit odd, I would expect that they target v2024dev1 since it is the current development release, and then when this gets merged a backport MR is created to target de desired releases.

Hi Walter

This MR is the possible fix for the bug reported which is failing on AMD64 target infrastructure/apertis-issues#26 (comment 69144), As the newport functionality works on apparmor context till apertis v2021 i.e. the reason we have asked this MR to be merged as part of v2021 releases.

Thanks for clarifying. Could you please explain why this change in not needed in newer releases? From a high level perspective I would expect that this fix will land first in a development release. Is there a difference that makes this change not suitable for the newer releases?

This issue is happening only on the older version Newport (with legacy canterbury changes) and this issue is not observed on latest version of Newport (without canterbury changes), hence v2021 release is already moved to EOL, so this changes are not applicable to latest development release to add it under ongoing development release. could we add this changes on v2021-update branch ? or will simply drop this MR.

I think we can simply drop this changes since as you mentioned v2021 reached its EOL. If you agree please close this MR.

resolved all threads

added 1 commit

• bee4921e - Extend apparmor policy for org.gtk.vfs

Compare with previous version

changed the description

mentioned in issue infrastructure/apertis-issues#26 (closed)

changed the description

closed