Hello intrigeri, Am 25.11.2017 um 16:06 schrieb intrigeri: .. > please review and merge the intrigeri/bugfix-882672-v2 branch (in > Vcs-Git). It would be great to include this change in the next upload > to sid, so that we stop breaking Thunderbird UX with AppArmor :) > > I'm now building a package to test my changes, but it'll take a while, > so please consider not blocking on this.
currently it looks like I'm impossible to catch up all the things that are needed to prepare a valid upload before starting my businesses trip tomorrow. :( Hopefully I've got some time next week to puzzle up all pieces. The Security people of Mozilla have collected for the first time all CVEs into the MFSA [1] for Thunderbird 52.5.0 right on time last night. In the past I need always to wait for that. Anyway, is there something else I need pick up from bug reports for next uploads? Sorry, I haven't had much time in the past days to stay on top of the changes and just tried to keep some tagging correctly. And, should we write something together in a file README.AppArmor which we can include also in the next upload? I was thinking about some detailed steps which users should do in case they need to do some debugging around the Thunderbird AppArmor profile. Or has the apparmor package already something like this we can point to? We could do that also in later upload. Unfortunately I wont have time to do that, sadly I have a heavy workload on my day job currently. > (BTW: sorry, I pushed crap to the intrigeri/bugfix-882672 branch by > mistake, and I'm not allowed to clean this up myself; feel free to > delete it.) Will take a look at this. You mean both branches are to delete later? Than I wont merge but do cherry-picking. I would suggest you push such non intrusive things directly to debian/sid. If one commit isn't fine or perfect enough just do a new one on top. [1] https://www.mozilla.org/en-US/security/advisories/mfsa2017-26/ -- Regards Carsten Schoenert
