Am 26.11.2017 um 21:38 schrieb j.wuttke: > On 11/26/2017 08:33 PM, Carsten Schoenert wrote: >> is this issue still exsitimg if you use the version 1:52.4.0-2~exp1 from >> experimental? > > Sorry: this I can only try out if you kindly point me to instructions how > try out a package from 'experimental' without ruining my 'testing' > installation.
Well, that's not that difficult as it's sound. 1. Add a additional sources.list file for experimental and fill in the right content > $ echo "echo deb http://deb.debian.org/debian/ experimental main non-free > contrib > /etc/apt/sources.list.d/experimental.list" | sudo sh 2. Update the sources > $ sudo apt update 3. Install thunderbird from experimental > $ sudo apt install -t experimental thunderbird 4. Deactivate the experimental repository again by renaming the additionalsources.list file > $ sudo mv /etc/apt/sources.list.d/experimental.list > /etc/apt/sources.list.d/experimental.list.inactive 5. Refresh the source to get the experimental repository out of the lists > $ sudo apt update That's all. As long as you *don't* use a apt upgrade or dist-upgrade after point 2 you are save. Always install only the specific package from the desired repository with the option '-t'. The repository experimental isn't different to unstable, except it's a stand alone repository. To get back to the package(s) from testing you would need to remove the packages first and then reinstall them after you have run 'apt update' with inactive experimental or unstable repositories. The next upload of thunderbird will have included all changes from 1:52.4.0-2~exp1 which have many AppArmor related fixes. But I'd like to know if your bug report is something different problem. The next version will also have a deactivated AppArmor profile due the huge problems we have to deal with after the default enabling of AppArmor. -- Regards Carsten Schoenert
