On 2019-07-27 12:12:25, intrigeri wrote: > Roger Shimizu: >> Buster is released, so I guess it's okay to reduce the severity to let >> it migrate to testing again. > > Thanks a lot for caring about torbrowser-launcher! > > FTR, I'm not enthusiastic at the idea of seeing it in testing and > backports (I suspect the reasons why torbrowser-launcher was not > suitable for Buster will still apply for Bullseye) but I can live with > it and I don't care enough about this topic to argue further. > > Anyhow, maybe we can simply close this bug then? What's the value in > keeping it open at normal severity?
If anything, this bug provides a continuous track record of our attempts at keeping this package alive in Debian. It is referenced upstream, for example, in: https://trac.torproject.org/projects/tor/ticket/3994 intrigeri: how does Tails ship TBB nowadays? The above bug report says something about an Iceweasel package 6 years ago, but surely that can't be up to date anymore... ;) Earlier in May you mentioned a "weird way" without going into details... It seems to me we have a common problem across distributions (and upstream) that we should figure out how to tackle. It would be too bad if this problem would just disappear under the rug while it's a real issue for our users still... A. -- A ballot is like a bullet. You don't throw your ballots until you see a target, and if that target is not within your reach, keep your ballot in your pocket. - Malcom X
