[pkg-apparmor] Bug#742829: closed by intrigeri <intrigeri at debian.org> (Bug#742829: fixed in apparmor 2.10.95-8)

Guido Günther agx at sigxcpu.org
Thu Sep 28 09:21:33 UTC 2017


Hi,
On Wed, Sep 27, 2017 at 04:47:27PM -0400, Daniel Richard G. wrote:
> On Wed, 2017 Sep 27 22:26+0200, Guido Günther wrote:
> >
> > Great! I'm a big fan of doing things upstream but from my pov I'd
> > consider apparmor or chromium to be upstream not Ubuntu. What about
> > filing a bug against the Debian chromium package with an updated
> > profile as a start? We can then take it from there and file another
> > one against apparor once it proves working for more people.
> 
> That would amount to the Debian Chromium maintainers becoming the new
> upstream for the profile. (Apparmor is basically maintained by

Or maybe people caring about the chromium profile like you, me and
others in this thread.

> Canonical, so also Ubuntu, and Google pretty surely will never touch
> this.) If they're willing, I can hardly see how they could do worse
> than Ubuntu.
> 
> And if it does work out, then that would be a basis to have Ubuntu ship
> the Debian profile instead of its own (neglected) version.
> 
> I don't know any of the Debian-Chromium folks to have a sense of what
> they're open to; would you?

Unfortunately not.

> I'll be happy to provide that updated Chromium profile if you want it.

Could you attach this to new bug against Chromium. If you'd be willing to
maintain the profile longterm I'd add that to the report too.

Cheers,
 -- Guido



More information about the pkg-apparmor-team mailing list