Bug#1029594: Fails to authenticate mit o365

2023-02-12 Thread Chandler Sobel-Sorenson
On Sun, 5 Feb 2023 23:36:38 +0100 Carsten Schoenert
 wrote:
> I don't understand what you want from me.
Well, I think it was clear in my messages but it seems you like to gloss
over everything and reduce it all to nothing.  For one you can stop
stating things as if they are facts when you have no evidence to support
them, that's a general rule for anything in life.

> Did you use stable for your daily work as Debian is suggesting? I don't
> think so. Would you be affected by this issue if you use stable? No!
Fortunately I was never affected by it because, by the time apt was
running, the bug was classified with a proper severity level that Nicola
had set.  Had you reduced the severity like you had been advocating for,
then I and many others would have been affected by this issue.

> Does your emails help preventing others? Also here I don't think so.
I think countering incorrect information posted and voicing my support
for certain severity levels is helpful.  It was certainly more helpful
than your message here which is just attacking me and reducing
everything I wrote to nothing.  I understand you don't like any
disagreements, but that happens in life when we make incorrect
statements and decisions.

> you still do nothing more than complaining
> how bad the situation is.
Sorry you think there was nothing more than complaining, but that is due
more to your attitude than the reality.  Lighten up!



Bug#1029594: Fails to authenticate mit o365

2023-02-07 Thread Ryan

Me three.  Please do push the new version!


Relevant outside links:

https://blog.thunderbird.net/2023/01/important-message-for-microsoft-office-365-enterprise-users/

https://bugzilla.mozilla.org/show_bug.cgi?id=1814536



On Tue, 7 Feb 2023 08:43:33 +0100 Antonio  wrote:

> The proposed fix works for me too.
>
>
>



Bug#1029594: Fails to authenticate mit o365

2023-02-06 Thread Antonio

The proposed fix works for me too.



Bug#1029594: Fails to authenticate mit o365

2023-02-06 Thread Harshula

Hi Carsten,

Authentication successfully completed with your test build:
https://people.debian.org/~tijuca/thunderbird-102.7.1+1/

Thanks,
Harshula

On 6/2/23 14:05, Harshula wrote:

Hi Carsten,

1) Did you use Thunderbird's Release Candidate Build 1 instead of 
Release Candidate Build 2 for the Debian 102.7.1 release [1]? It appears 
you uploaded the Debian package on the "2023-01-24" [2]. Build 2 was 
only released on the 31st of January.


$ diff -rq build1/thunderbird-102.7.1/comm/mailnews/base/src/ 
debian/thunderbird-102.7.1/comm/mailnews/base/src/


$ diff -rq build2/thunderbird-102.7.1/comm/mailnews/base/src/ 
debian/thunderbird-102.7.1/comm/mailnews/base/src/
Files build2/thunderbird-102.7.1/comm/mailnews/base/src/OAuth2.jsm and 
debian/thunderbird-102.7.1/comm/mailnews/base/src/OAuth2.jsm differ
Files 
build2/thunderbird-102.7.1/comm/mailnews/base/src/OAuth2Providers.jsm 
and 
debian/thunderbird-102.7.1/comm/mailnews/base/src/OAuth2Providers.jsm 
differ


2) The authentication successfully completed with the upstream build of 
Thunderbird 102.7.1 [3], whereas the authentication was in an infinite 
loop with the Debian build of Thunderbird 102.7.1.


Regards,
Harshula

[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1814536
[2] 
https://tracker.debian.org/news/1413005/accepted-thunderbird-110271-1-source-into-unstable/
[3] 
https://download-origin.cdn.mozilla.net/pub/thunderbird/releases/102.7.1/linux-x86_64/en-US/thunderbird-102.7.1.tar.bz2




Bug#1029594: Fails to authenticate mit o365

2023-02-06 Thread Terry Watt
I was also impacted by this bug, and the test build solves the problem once I 
refreshed my login cookie.


Thanks,
Terry

On Mon, 6 Feb 2023 18:37:12 +0100 Carsten Schoenert wrote:
> Dear bug submitters,
>
> I've build a test version amd64 of the current Mozilla upstream version
> for Thunderbird 102.7.1 which was push onto the release folder on
> 01-Feb-2023.
>
> 
https://download-origin.cdn.mozilla.net/pub/thunderbird/releases/102.7.1/source/
>
> The previous used version 102.7.1 which was uploaded as Debian version
> 1:102.7.1-1 was taken from the upstream candidates folder build1 dated
> to 24-Jan-2023.
>
> 
https://download-origin.cdn.mozilla.net/pub/thunderbird/candidates/102.7.1-candidates/build1/source/

>
> The test build can be found here
>
> https://people.debian.org/~tijuca/thunderbird-102.7.1+1/
>
> Please test if the issue of broken OAuth authetification on Outlook365
> is now fixed and Thunderbird is working again and give please some feedback.
>
> If the original issues is fixed I will preprare a final upload to the
> archive.
>
> Regards
> Carsten
>
> Am Wed, Jan 25, 2023 at 09:48:51AM +0100 schrieb Carsten Schoenert:
> > Control: tags -1 serious
> >
> > Hello Klaus,
> >
> > Am 25.01.23 um 08:38 schrieb Klaus Ethgen:
> > > After upgrading from 1:102.6.0-1 this morning, thunderbird fails to
> > > login into microsoft o365, making it impossible to access mails from
> > > that account.
> >
> > the current version 102.7.1 should normally fix exact this regression about
> > MS Outlook 365 that was introduced by 102.7.0.
> >
> > Upstream did announce that problem for the version 102.7.1 but unfortunately
> > too late as the the upload to unstable was already done.
> >
> > I've no estimated time line about a fixed version.
> >
> > --
> > Regards
> > Carsten
>
>


Bug#1029594: Fails to authenticate mit o365

2023-02-06 Thread Rann Bar-On
I can confirm that this test build fixes the issue for me. Thunderbird
asked me to log into my O365 account upon launch, and logged into it
correctly.

On Mon, Feb 6, 2023 at 12:51 PM Carsten Schoenert 
wrote:

> Dear bug submitters,
>
> I've build a test version amd64 of the current Mozilla upstream version
> for Thunderbird 102.7.1 which was push onto the release folder on
> 01-Feb-2023.
>
>
> https://download-origin.cdn.mozilla.net/pub/thunderbird/releases/102.7.1/source/
>
> The previous used version 102.7.1 which was uploaded as Debian version
> 1:102.7.1-1 was taken from the upstream candidates folder build1 dated
> to 24-Jan-2023.
>
>
> https://download-origin.cdn.mozilla.net/pub/thunderbird/candidates/102.7.1-candidates/build1/source/
>
> The test build can be found here
>
> https://people.debian.org/~tijuca/thunderbird-102.7.1+1/
>
> Please test if the issue of broken OAuth authetification on Outlook365
> is now fixed and Thunderbird is working again and give please some
> feedback.
>
> If the original issues is fixed I will preprare a final upload to the
> archive.
>
> Regards
> Carsten
>
> Am Wed, Jan 25, 2023 at 09:48:51AM +0100 schrieb Carsten Schoenert:
> > Control: tags -1 serious
> >
> > Hello Klaus,
> >
> > Am 25.01.23 um 08:38 schrieb Klaus Ethgen:
> > > After upgrading from 1:102.6.0-1 this morning, thunderbird fails to
> > > login into microsoft o365, making it impossible to access mails from
> > > that account.
> >
> > the current version 102.7.1 should normally fix exact this regression
> about
> > MS Outlook 365 that was introduced by 102.7.0.
> >
> > Upstream did announce that problem for the version 102.7.1 but
> unfortunately
> > too late as the the upload to unstable was already done.
> >
> > I've no estimated time line about a fixed version.
> >
> > --
> > Regards
> > Carsten
>
> --
> To unsubscribe, send mail to 1029594-unsubscr...@bugs.debian.org.
>


-- 
Rann Bar-On
he/him/his


Bug#1029594: Fails to authenticate mit o365

2023-02-06 Thread Carsten Schoenert
Dear bug submitters,

I've build a test version amd64 of the current Mozilla upstream version
for Thunderbird 102.7.1 which was push onto the release folder on
01-Feb-2023.

https://download-origin.cdn.mozilla.net/pub/thunderbird/releases/102.7.1/source/

The previous used version 102.7.1 which was uploaded as Debian version
1:102.7.1-1 was taken from the upstream candidates folder build1 dated
to 24-Jan-2023.

https://download-origin.cdn.mozilla.net/pub/thunderbird/candidates/102.7.1-candidates/build1/source/

The test build can be found here

https://people.debian.org/~tijuca/thunderbird-102.7.1+1/

Please test if the issue of broken OAuth authetification on Outlook365
is now fixed and Thunderbird is working again and give please some feedback.

If the original issues is fixed I will preprare a final upload to the
archive.

Regards
Carsten

Am Wed, Jan 25, 2023 at 09:48:51AM +0100 schrieb Carsten Schoenert:
> Control: tags -1 serious
> 
> Hello Klaus,
> 
> Am 25.01.23 um 08:38 schrieb Klaus Ethgen:
> > After upgrading from 1:102.6.0-1 this morning, thunderbird fails to
> > login into microsoft o365, making it impossible to access mails from
> > that account.
> 
> the current version 102.7.1 should normally fix exact this regression about
> MS Outlook 365 that was introduced by 102.7.0.
> 
> Upstream did announce that problem for the version 102.7.1 but unfortunately
> too late as the the upload to unstable was already done.
> 
> I've no estimated time line about a fixed version.
> 
> -- 
> Regards
> Carsten



Bug#1029594: Fails to authenticate mit o365

2023-02-05 Thread Harshula

Hi Carsten,

1) Did you use Thunderbird's Release Candidate Build 1 instead of 
Release Candidate Build 2 for the Debian 102.7.1 release [1]? It appears 
you uploaded the Debian package on the "2023-01-24" [2]. Build 2 was 
only released on the 31st of January.


$ diff -rq build1/thunderbird-102.7.1/comm/mailnews/base/src/ 
debian/thunderbird-102.7.1/comm/mailnews/base/src/


$ diff -rq build2/thunderbird-102.7.1/comm/mailnews/base/src/ 
debian/thunderbird-102.7.1/comm/mailnews/base/src/
Files build2/thunderbird-102.7.1/comm/mailnews/base/src/OAuth2.jsm and 
debian/thunderbird-102.7.1/comm/mailnews/base/src/OAuth2.jsm differ
Files 
build2/thunderbird-102.7.1/comm/mailnews/base/src/OAuth2Providers.jsm 
and 
debian/thunderbird-102.7.1/comm/mailnews/base/src/OAuth2Providers.jsm differ


2) The authentication successfully completed with the upstream build of 
Thunderbird 102.7.1 [3], whereas the authentication was in an infinite 
loop with the Debian build of Thunderbird 102.7.1.


Regards,
Harshula

[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1814536
[2] 
https://tracker.debian.org/news/1413005/accepted-thunderbird-110271-1-source-into-unstable/
[3] 
https://download-origin.cdn.mozilla.net/pub/thunderbird/releases/102.7.1/linux-x86_64/en-US/thunderbird-102.7.1.tar.bz2



https://download-origin.cdn.mozilla.net/pub/thunderbird/candidates/102.7.1-candidates/build1/source/

Filethunderbird-102.7.1.source.tar.xz   477M24-Jan-2023 03:33
Filethunderbird-102.7.1.source.tar.xz.asc   833 24-Jan-2023 03:33

$ sha256sum thunderbird-102.7.1.source.tar.xz
74cbf32140cbbd7954093f7adc1a1d0cf8a9b0f77dfd9d344540a111fed9ac20 
thunderbird-102.7.1.source.tar.xz



https://download-origin.cdn.mozilla.net/pub/thunderbird/candidates/102.7.1-candidates/build2/source/

Filethunderbird-102.7.1.source.tar.xz   487M31-Jan-2023 15:46
Filethunderbird-102.7.1.source.tar.xz.asc   833 31-Jan-2023 15:46

$ sha256sum thunderbird-102.7.1.source.tar.xz
00c9a215ec99b4ce1683c8581b5bb44759ad31cb1303bdec173c053fcee27c91 
thunderbird-102.7.1.source.tar.xz



https://download-origin.cdn.mozilla.net/pub/thunderbird/releases/102.7.1/source/

Filethunderbird-102.7.1.source.tar.xz   487M01-Feb-2023 02:10
Filethunderbird-102.7.1.source.tar.xz.asc   833 01-Feb-2023 02:10

$ sha256sum thunderbird-102.7.1.source.tar.xz
00c9a215ec99b4ce1683c8581b5bb44759ad31cb1303bdec173c053fcee27c91 
thunderbird-102.7.1.source.tar.xz

$ diff -rq build1/thunderbird-102.7.1/ build2/thunderbird-102.7.1
Files build1/thunderbird-102.7.1/comm/chat/protocols/xmpp/xmpp-base.jsm and 
build2/thunderbird-102.7.1/comm/chat/protocols/xmpp/xmpp-base.jsm differ
Files build1/thunderbird-102.7.1/comm/mail/base/content/mailContextMenus.js and 
build2/thunderbird-102.7.1/comm/mail/base/content/mailContextMenus.js differ
Files build1/thunderbird-102.7.1/comm/mail/base/content/utilityOverlay.js and 
build2/thunderbird-102.7.1/comm/mail/base/content/utilityOverlay.js differ
Files 
build1/thunderbird-102.7.1/comm/mail/components/compose/content/MsgComposeCommands.js
 and 
build2/thunderbird-102.7.1/comm/mail/components/compose/content/MsgComposeCommands.js
 differ
Only in 
build2/thunderbird-102.7.1/comm/mail/components/extensions/test/browser: 
browser_ext_compose_bug1804796.js
Files 
build1/thunderbird-102.7.1/comm/mail/components/extensions/test/browser/browser.ini
 and 
build2/thunderbird-102.7.1/comm/mail/components/extensions/test/browser/browser.ini
 differ
Files build1/thunderbird-102.7.1/comm/mail/themes/windows/mail/mailWindow1.css 
and build2/thunderbird-102.7.1/comm/mail/themes/windows/mail/mailWindow1.css 
differ
Files build1/thunderbird-102.7.1/comm/mailnews/base/src/OAuth2.jsm and 
build2/thunderbird-102.7.1/comm/mailnews/base/src/OAuth2.jsm differ
Files build1/thunderbird-102.7.1/comm/mailnews/base/src/OAuth2Providers.jsm and 
build2/thunderbird-102.7.1/comm/mailnews/base/src/OAuth2Providers.jsm differ
Files build1/thunderbird-102.7.1/comm/mailnews/compose/src/nsMsgCompose.cpp and 
build2/thunderbird-102.7.1/comm/mailnews/compose/src/nsMsgCompose.cpp differ
Files 
build1/thunderbird-102.7.1/comm/mailnews/import/modules/AddrBookFileImporter.jsm
 and 
build2/thunderbird-102.7.1/comm/mailnews/import/modules/AddrBookFileImporter.jsm
 differ
Files 
build1/thunderbird-102.7.1/comm/mailnews/import/test/unit/resources/addressbook.json
 and 
build2/thunderbird-102.7.1/comm/mailnews/import/test/unit/resources/addressbook.json
 differ
Only in build2/thunderbird-102.7.1/comm/mailnews/import/test/unit/resources: 
dos_vcard_addressbook.vcf
Files 
build1/thunderbird-102.7.1/comm/mailnews/import/test/unit/test_AddrBookFileImporter.js
 and 
build2/thunderbird-102.7.1/comm/mailnews/import/test/unit/test_AddrBookFileImporter.js
 differ
Files build1/thunderbird-102.7.1/sourcestamp.txt and 

Bug#1029594: Fails to authenticate mit o365

2023-02-05 Thread Carsten Schoenert

Am 05.02.23 um 19:56 schrieb Chandler Sobel-Sorenson:

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.

I don't understand what you want from me.

Is the world going down now? For sure not!

Did such situations did happen in the past? Yes, several times while I 
maintaining Thunderbird.


Do I have a life beside Debian? Yes I have.

Did you use stable for your daily work as Debian is suggesting? I don't 
think so. Would you be affected by this issue if you use stable? No!


Does your emails help preventing others? Also here I don't think so.
You even don't have tried to use some pre-compiled version from Mozilla 
and did give some feedback, you still do nothing more than complaining 
how bad the situation is.


So, live with the situation like I do. We are all volunteers and do the 
work in our free time. Once I got time I will try to look at situation.


--
Regards
Carsten



Bug#1029594: Fails to authenticate mit o365

2023-02-05 Thread Chandler Sobel-Sorenson
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... ;)



Bug#1029594: Fails to authenticate mit o365

2023-02-05 Thread Carsten Schoenert

Am 04.02.23 um 23:25 schrieb Chandler Sobel-Sorenson:

Frankly, I'm glad it was increased to serious because otherwise
listbugs wouldn't have let me stop it, then I have to spend more time
figuring out why I suddenly can't retrieve my e-mail and tracking
down a solution, downgrading packages, etc.  There is only so much
time in the day and so much coffee I can drink. ;-)  We use O365 at
the University and I have enough issues maintaining our Linux systems
there. ;-)  Last thing I need is problems with workstation to get in
the way of my work.
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.



  > Quoting https://www.debian.org/Bugs/Developer.en.html
  > important
  > a bug which has a major effect on the usability of a package, without 
rendering it completely unusable to everyone
  > And that's what this issue is about, most of the users can use
  > Thunderbird without problems.

Do you have statistics for that?  What is "most"?


The majority of users. :-)
And these are obviously not users of Microsoft Cloud products. We haven 
got reports from GMail user e.g.


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.



I'm pretty sure many Universities and other large organizations
across the world are using Office however, if it's anything like our
University, "most" of those users are using Windows version of
Outlook or Outlook Online.  Still, I could not be sure what "most"
Thunderbird users are using.
Sure the world is mostly owned by Microsoft Desktop systems, and using 
Exchange or now Outlook 365 is also decreasing the the free choice of a 
client to interact with the server instance.


Most users of Thunderbird are not using M$ products or at least only 
using a small set of features of Exchange or Outlook.com.



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.



  > serious
  >     is a severe violation of Debian policy (roughly, it violates a "must" or 
"required" directive),
  > or, in the package maintainer's or release manager's opinion, makes the 
package unsuitable for release.

I don't have the time to currently review the 609 instances of "must"
or "required" in the policy, but I believe this makes the package
unsuitable for release.

I don't really understand your problem.
What is the problem here?
What does it help if we increase the severity even more? Even right now 
the the broken package will not migrate to testing. But it will also 
trigger a remove of the version in testing. What do we win?



  > grave
  >     makes the package in question unusable or mostly so, or causes data 
loss,
  > or introduces a security hole allowing access to the accounts of users who 
use the package.

I think #1030112 should be reopened and/or merged with this bug, with
the title being updated to reflect broader issue with OAuth2. As the
bug is much broader than is implied here, severity should be
maintained at a minimum of serious.


And what we get from doing so?
The closed issue has added information that further talking is happen here.


 Since many these days are using
Gmail as their only e-mail then could even be argued that thunderbird
is now unusable or mostly so, therefore severity of grave is not out
of the question either.


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.



So finally again as written in other answers:
If you need to use Thunderbird in a critical environment you shouldn't 
use unstable/sid 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. Or if you are 
more experienced switch to testing.


--
Regards
Carsten



Bug#1029594: Fails to authenticate mit o365

2023-02-04 Thread Chandler Sobel-Sorenson

On Wed, 1 Feb 2023 19:50:15 -0300 Carsten Schoenert  
wrote:
> Am Wed, Feb 01, 2023 at 03:24:14PM + schrieb Nicola Chiapolini:
> > Control: severity -1 serious
> > Hi Carsten
> > I am increasing the severity again. This bit me today.
> > I rely on apt-listbugs to protect me from such problems and with the default settings 
"normal" is not sufficient to trigger listbugs.
> > Yesterday, #1030112 triggered listbugs, so today I was happy to see that 
the problem is fixed and upgraded. So I try to help others...
> > (Since the only reason I use Thunderbird in the first place is to access 
o365, this bug might even be considered grave ;-)
>
> I'm considering this issue is normaly just of severity important.

Frankly, I'm glad it was increased to serious because otherwise listbugs 
wouldn't have let me stop it, then I have to spend more time figuring out why I 
suddenly can't retrieve my e-mail and tracking down a solution, downgrading 
packages, etc.  There is only so much time in the day and so much coffee I can 
drink. ;-)  We use O365 at the University and I have enough issues maintaining 
our Linux systems there. ;-)  Last thing I need is problems with workstation to 
get in the way of my work.

> Quoting https://www.debian.org/Bugs/Developer.en.html
> important
> a bug which has a major effect on the usability of a package, without 
rendering it completely unusable to everyone
> And that's what this issue is about, most of the users can use
> Thunderbird without problems.

Do you have statistics for that?  What is "most"?

I'm pretty sure many Universities and other large organizations across the world are using Office 
however, if it's anything like our University, "most" of those users are using Windows 
version of Outlook or Outlook Online.  Still, I could not be sure what "most" Thunderbird 
users are using.

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.

> serious
>     is a severe violation of Debian policy (roughly, it violates a "must" or 
"required" directive),
> or, in the package maintainer's or release manager's opinion, makes the 
package unsuitable for release.

I don't have the time to currently review the 609 instances of "must" or 
"required" in the policy, but I believe this makes the package unsuitable for release.

> grave
>     makes the package in question unusable or mostly so, or causes data loss,
> or introduces a security hole allowing access to the accounts of users who 
use the package.

I think #1030112 should be reopened and/or merged with this bug, with the title 
being updated to reflect broader issue with OAuth2. As the bug is much broader 
than is implied here, severity should be maintained at a minimum of serious.  
Since many these days are using Gmail as their only e-mail then could even be 
argued that thunderbird is now unusable or mostly so, therefore severity of 
grave is not out of the question either.

Best Regards,
Chandler



Bug#1029594: Fails to authenticate mit o365

2023-02-02 Thread Nicola Chiapolini

Hi Carsten

Thanks for your reply.

I'm considering this issue is normaly just of severity important.
[...]

I agree.

As explained, I choose the higher one to make sure it triggers 
apt-listbugs. I was not aware that "a major effect on the usability" is 
not enough to trigger listbugs until now. I adjusted the config 
accordingly, but I assume a lot of users still have the default set.



But, using severity important would allow to migrate the package to > testing 
and more users would be affected by the issue.

The package already migrated to testing. That's why it hit me.

$ aptitude versions thunderbird
i  1:102.6.0-1
p  1:102.7.1-1  testing,unstable
p  1:104.0~b2-1 experimental

so listbugs is currently the remaining line of defence.

best
Nicola



Bug#1029594: Fails to authenticate mit o365

2023-02-01 Thread Carsten Schoenert
Am Wed, Feb 01, 2023 at 03:24:14PM + schrieb Nicola Chiapolini:
> Control: severity -1 serious
> 
> Hi Carsten
> 
> I am increasing the severity again. This bit me today. 
> I rely on apt-listbugs to protect me from such problems and with the default 
> settings "normal" is not sufficient to trigger listbugs. 
> Yesterday, #1030112 triggered listbugs, so today I was happy to see that the 
> problem is fixed and upgraded. So I try to help others...
> (Since the only reason I use Thunderbird in the first place is to access 
> o365, this bug might even be considered grave ;-)

I'm considering this issue is normaly just of severity important.

Quoting https://www.debian.org/Bugs/Developer.en.html

important
a bug which has a major effect on the usability of a package, without 
rendering it completely unusable to everyone

And that's what this issue is about, most of the users can use
Thunderbird without problems.

But, using severity important would allow to migrate the package to
testing and more users would be affected by the issue. So I'm fine with
keeping the current severity.

On the other hand you should consider to not use unstable as prefered
Debian release in case you are depening an always usable packages.

Currently I still don't have an idea when a fixed version will be
available.

Regards
Carsten



Bug#1029594: Fails to authenticate mit o365

2023-02-01 Thread Enrico Tröger
Hi,

> (Since the only reason I use Thunderbird in the first place is to
> access o365, this bug might even be considered grave ;-)

upstream is handling this bug in
https://bugzilla.mozilla.org/show_bug.cgi?id=1810760 and it seems a
working fix is available and so we will hopefully see a new release in
the next few days.

Regards,
Enrico



Processed: Re: Bug#1029594: Fails to authenticate mit o365

2023-02-01 Thread Debian Bug Tracking System
Processing control commands:

> severity -1 serious
Bug #1029594 [thunderbird] Fails to authenticate mit o365
Bug #1029606 [thunderbird] thunderbird: After updating the package I cannot 
access the Exchange account
Severity set to 'serious' from 'normal'
Severity set to 'serious' from 'normal'

-- 
1029594: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029594
1029606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029606
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems