[Touch-packages] [Bug 1734038] Re: utils don't understand «include "/where/ever"» (was: Potential regression found with apparmor test on Xenial/Zesty)

Since snapd is using this bug for its SRU blocker and we have bug #1733700 that is the same issue, I'm going to use this bug as the snapd one and for the apparmor one. ** Summary changed: - utils don't understand «include "/where/ever"» (was: Potential regression found with apparmor test on

[Touch-packages] [Bug 1734038] Re: utils don't understand «include "/where/ever"» (was: Potential regression found with apparmor test on Xenial/Zesty)

We merged https://github.com/snapcore/snapd/pull/4306 which fixes this. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1734038 Title: utils don't understand «include

[Touch-packages] [Bug 1734038] Re: utils don't understand «include "/where/ever"» (was: Potential regression found with apparmor test on Xenial/Zesty)

@mvo - this is probably obvious, but if you used '#include' instead of 'include', it would side-step the issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1734038

[Touch-packages] [Bug 1734038] Re: utils don't understand «include "/where/ever"» (was: Potential regression found with apparmor test on Xenial/Zesty)

Yes, the split parser has been a issue for a long time. There has been a plan to make the flex/yacc/C parser code available as a lib for the other tools but its one of those things that never gets resources allocated. The short term fix for this is probably a backport of a newer version of the