Source: flask-dance
Version: 7.0.0-1
Severity: serious

flask-dance fails its tests when built with python3-werkzeug 2.3.8-1
(and also with version 3.0.x in experimental as well), and needs
updating to handle this.

Also reported upstream to https://github.com/singingwolfboy/flask-dance/issues/425

Best wishes,

Julian

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Control: tag -1 pending

Hello,

Bug #1060020 in flask-dance reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/python-team/packages/flask-dance/-/commit/8e14c38b796d0fff768fad95ac64fdf7a52b572a

------------------------------------------------------------------------
New upstream version (closes: #1060020) ------------------------------------------------------------------------

(this message was generated automatically)
--
Greetings

https://bugs.debian.org/1060020

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Processing control commands:

tag -1 pending

Bug #1060020 [src:flask-dance] flask-dance: FTBFS with python3-werkzeug >= 2.3.8
Added tag(s) pending.

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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

This is a multi-part message in MIME format...

Your message dated Fri, 05 Jan 2024 07:19:25 +0000
with message-id <E1rLeUH-002Yi2-S6@fasolo.debian.org>
and subject line Bug#1060020: fixed in flask-dance 7.0.1-1
has caused the Debian Bug report #1060020,
regarding flask-dance: FTBFS with python3-werkzeug >= 2.3.8
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


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

Received: (at submit) by bugs.debian.org; 4 Jan 2024 21:08:00 +0000 X-Spam-Checker-Version: SpamAssassin 3.4.6-bugs.debian.org_2005_01_02
(2021-04-09) on buxtehude.debian.org
X-Spam-Level:
X-Spam-Status: No, score=-111.9 required=4.0 tests=BAYES_00,DKIMWL_WL_HIGH,
DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FROMDEVELOPER,
SPF_HELO_NONE,SPF_NONE,T_SCC_BODY_TEXT_LINE,UNPARSEABLE_RELAY,
USER_IN_DKIM_WELCOMELIST,USER_IN_DKIM_WHITELIST,XMAILER_REPORTBUG
autolearn=ham autolearn_force=no
version=3.4.6-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 11; hammy, 100; neutral, 23; spammy,
0. spammytokens:
hammytokens:0.000-+--Hx-spam-relays-external:sk:stravin,
0.000-+--H*RT:sk:stravin, 0.000-+--Hx-spam-relays-external:311,
0.000-+--H*RT:108, 0.000-+--H*RT:311
Return-path: <jdg@debian.org>
Received: from stravinsky.debian.o