Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.python > #14502 > unrolled thread

python-werkzeug 2.2.2 and flask 2.2.2 transition

Back to article view | Back to linux.debian.maint.python

Contents

  python-werkzeug 2.2.2 and flask 2.2.2 transition Thomas Goirand <zigo@debian.org> - 2022-09-27 12:00 +0200
    Re: python-werkzeug 2.2.2 and flask 2.2.2 transition Carsten Schoenert <c.schoenert@t-online.de> - 2022-10-20 09:30 +0200
      Re: python-werkzeug 2.2.2 and flask 2.2.2 transition Carsten Schoenert <c.schoenert@t-online.de> - 2022-11-06 20:40 +0100
        Re: python-werkzeug 2.2.2 and flask 2.2.2 transition Carsten Schoenert <c.schoenert@t-online.de> - 2022-11-13 07:20 +0100
          Re: python-werkzeug 2.2.2 and flask 2.2.2 transition Carsten Schoenert <c.schoenert@t-online.de> - 2022-11-15 18:40 +0100

#14502 — python-werkzeug 2.2.2 and flask 2.2.2 transition

Hi,

I'd like Bookworm to be released with python-werkzeug 2.2.2 and flask 
2.2.2 (needed by Sahara).

So I've uploaded both to Experimental, and here's the result:
https://qa.debian.org/excuses.php?experimental=1&package=python-werkzeug
https://qa.debian.org/excuses.php?experimental=1&package=flask

So I filled bugs against the relevant packages:
pytest-httpbin: #1020728, #1020796
quart: #1020729
sentry-python: #1020730
flask-appbuilder: #1020739
flask-bcrypt: #1020824
flask-login: #1020794
pydevd: #1020795
python-flask-marshmallow: #1020822
searx-admin: #1020823

Please help fixing these.

Cheers,

Thomas Goirand (zigo)

[toc] | [next] | [standalone]

#14544

Hi,
Am 27.09.22 um 11:52 schrieb Thomas Goirand:
> Hi,
> 
> I'd like Bookworm to be released with python-werkzeug 2.2.2 and flask
> 2.2.2 (needed by Sahara).
> 
> So I've uploaded both to Experimental, and here's the result:
> https://qa.debian.org/excuses.php?experimental=1&package=python-werkzeug
> https://qa.debian.org/excuses.php?experimental=1&package=flask
> 
> So I filled bugs against the relevant packages:
> pytest-httpbin: #1020728, #1020796
> quart: #1020729
> sentry-python: #1020730
> flask-appbuilder: #1020739
> flask-bcrypt: #1020824
> flask-login: #1020794
> pydevd: #1020795
> python-flask-marshmallow: #1020822
> searx-admin: #1020823

I've looked at some of these issues and fixed also some of them, the 
following packages are left with build issues against the updated packages.

pytest-httpbin
flask-appbuilder
pydevd
searx-admin

-- 
Regards
Carsten

[toc] | [prev] | [next] | [standalone]

#14607

Hi again,

currently I still see the following packages are left with autopkgtest 
issues.

flask-appbuilder: #1020739
onionshare: #1023568
pydevd: #1020795
searx-admin: #1020823

I filed a new issue about the failing autopkgtest against onionshare 
minutes ago.
What about raising the severity for the other packages? Time flies and 
it's not that far away the first freeze date will come.

Am 20.10.22 um 09:23 schrieb Carsten Schoenert:
> Hi,
> Am 27.09.22 um 11:52 schrieb Thomas Goirand:
>> Hi,
>>
>> I'd like Bookworm to be released with python-werkzeug 2.2.2 and flask
>> 2.2.2 (needed by Sahara).
>>
>> So I've uploaded both to Experimental, and here's the result:
>> https://qa.debian.org/excuses.php?experimental=1&package=python-werkzeug
>> https://qa.debian.org/excuses.php?experimental=1&package=flask
>>
>> So I filled bugs against the relevant packages:
>> pytest-httpbin: #1020728, #1020796
>> quart: #1020729
>> sentry-python: #1020730
>> flask-appbuilder: #1020739
>> flask-bcrypt: #1020824
>> flask-login: #1020794
>> pydevd: #1020795
>> python-flask-marshmallow: #1020822
>> searx-admin: #1020823
> 
> I've looked at some of these issues and fixed also some of them, the
> following packages are left with build issues against the updated packages.
> 
> pytest-httpbin
> flask-appbuilder
> pydevd
> searx-admin
> 

-- 
Regards
Carsten

[toc] | [prev] | [next] | [standalone]

#14620

Hi,

Am 06.11.22 um 20:31 schrieb Carsten Schoenert:
> Hi again,
> 
> currently I still see the following packages are left with autopkgtest
> issues.
> 
> flask-appbuilder: #1020739
> onionshare: #1023568
> pydevd: #1020795
> searx-admin: #1020823
> 
> I filed a new issue about the failing autopkgtest against onionshare
> minutes ago.

it has shown, that onionshare isn't the problem for the breaking 
autopkgtest but flask-socketio is. The good news is that updating 
flask-socketio will be enough to solve the not working autopkgtest 
mainly. There is a small need to tune one of the remaining onionshare 
test calls.

> What about raising the severity for the other packages? Time flies and
> it's not that far away the first freeze date will come.

If there are no objections I will bump the severity of serious for the 
remaining three bug reports this week.

-- 
Regards
Carsten

[toc] | [prev] | [next] | [standalone]

#14622

Hi,

Am 13.11.22 um 07:18 schrieb Carsten Schoenert:
> If there are no objections I will bump the severity of serious for the
> remaining three bug reports this week.

currently I've raised the severity for only two remaining bug reports

flask-appbuilder: #1020739
searx-admin: #1020823

I've skipped #1023568 that was open against oninshare, but the main or 
first problem within the autopkgtest run is based on a outdated package 
flask-socketio.
And onionshare is currently not in testing and would not block a 
migration of flask and python-werkzeug.

@Thomas
I'd like to see flask and the required python-werkzeug in unstable soon 
so any outstanding issues after a first upload could get fixed before 
the hard freezes for bookworm will begin.

Do you have a timeline when any uploads of the two packages to unstable 
can happen?

-- 
Regards
Carsten

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.maint.python

csiph-web