Hi, Carsten Schoenert: > 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. :(
Take care of yourself. I trust you'll do you the best you can :) > Anyway, is there something else I need pick up from bug reports for next > uploads? Nothing for you wrt. AppArmor: I've pushed all existing fixes to Vcs-Git already, and the branch I'm proposing here will "fix" the remaining ones… by disabling the AppArmor profile by default. This should substantially decrease the added workload caused by AppArmor for you. Everything is tracked closely by Simon, Vincas and myself (many thanks to Simon and Vincas BTW!). So once my branch is merged we should be good :) > And, should we write something together in a file README.AppArmor which > we can include also in the next upload? FWIW my branch adds a new paragraph to README.Debian, that documents how to opt-in for the AppArmor profile, and where to contribute to the profile upstream. > I was thinking about some > detailed steps which users should do in case they need to do some > debugging around the Thunderbird AppArmor profile. Good idea! I've added a link to the corresponding doc on wiki.d.o (commit d8dcde6daa on my branch). > You mean both branches are to delete later? Yes. You can delete intrigeri/bugfix-882672 right away, and delete intrigeri/bugfix-882672-v2 after you've merged or cherry-picked its commits. > 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. OK, I'll do that in the future. Thanks a lot for your trust, it does mean something to me. So I'll merge my branch myself once I've tested a package built from it :) Cheers, -- intrigeri
