Carsten Schoenert wrote on 2/5/23 3:39 AM: > If you need your laptop or your workstation for mission critical > things than Debian unstable/sid isn't the right choice. If you do so > then you will need some knowledge to handle situations like happen > now.I'm not. The broken package has been released to testing already. In an ideal world I would have two separate computers but not everyone has ideal situations. testing release is good for my situation and have now added notifications of important bugs for apt-listbugs config as well, so thank you for mentioning that. However, that's not the default for users.
> Debian doesn't have any really resilient statistics as such > statistics bases on completely free choice. Debian doesn't collect > data from users without any confirmation. Then why are you making assumptions on who the majority of users are? Such assertions require evidence, such as statistics. > Most users of Thunderbird are not using M$ products or at least only > using a small set of features of Exchange or Outlook.com. Again, how do you know this? guts or feelings are not valid sources of statistics. >> Further, the actual bug in mozilla is #1814536 (OAuth2 authentication >> | 102.7.1. | Linux - fails) - still Open. This is an even broader >> than just o365 as Google uses OAuth2 as well, etc. That bug was >> reported here in Debian as grave under #1030112 but you closed it as >> a duplicate of this bug. That was perhaps mistaken. > No, it was not. > Having dozen of issues open that are about the same problem is really > not helpful to handle the issue. Okay then, as long as you are certain. > I don't really understand your problem. What is the problem here? I'm just voicing my support for keeping the severity at serious while you keep insisting it should merely be important. > Even right now the the broken package will not migrate to testing. Why do you think that? How do you determine such? Is your system configured correct? It is literally listed in testing on packages.debian.org and available to be upgraded from 102.6. > But it will > also trigger a remove of the version in testing. What do we win? Maybe less bug reports? You seem to like that ;) I'm sure we all do. > My GMail account is working with the current version in testing means > to me that Google doesn't has changed something on their side. > Obviously only MS has changed something. Okay then, that's good. Maybe the report on Mozilla is wrong then, I don't know, I am just putting out there what I've found. > So finally again as written in other answers: If you need to use > Thunderbird in a critical environment you shouldn't use unstable/sid and again as I've said and as you should know, I/we are not, Thunderbird 102.7.1 has already been released to testing. > as long you don't know how to handle the potential breakage of > packages. Debian is providing a stable release for productive use, if > you need newer version of software you can add the backport suite. Most of us should already know that. I too just want to help others not have to spend time fixing things that can be prevented with a good severity label. I have a system with stable, backports, testing, experimental, unstable, and snapshots repos working fine, for now... ;)
