Hi Georg, On Freitag, 20. November 2015, [email protected] wrote: > There are multiple points involved, running into this problem depends > for example on the content of ~./config/torbrowser/ and the last time, > torbrowser-launcher checked for the version to be installed:
thanks for your detailed analysis! not sure what to do with it though, as upstream has addressed them in 0.2.2 already, so probably the best is to just cherry-pick those commits… > So...not really sure how to go on here. Some thoughts for the future: > > - It's not possible to delete ~./config/torbrowser/ if doing apt-get > dist-upgrade, because touching files / directories in user home > directories is a no-go (and forbidden by policy), right? that's correct. > - Maybe a note to the user if doing apt-get dist-upgrade would be > sufficient (not sure what this technique is called, but if important > changed are being made, the user gets a note sometimes.) apt-get update is run by root, not the user(s). > - Another possibility: Force a version check if apt-get dist-upgrade was > run at the next start (not sure how to check and implement this). see above. > @Holger: If you need any support / tests / etc., let me know. as explained in more detail in a private mail to Georg: identifying the commits between debian/0.1.9-1..debian/0.2.2-1 would be helpful. There's https://jenkins.debian.net/view/torbrowser/job/torbrowser-launcher_test_on_jessie_amd64_from_git_branch_debian_jessie/lastBuild/ now too ;-) cheers, Holger
signature.asc
Description: This is a digitally signed message part.
