Python3.8 as default final status
The python3-defaults with python3.8 as the default python3 has migrated to Testing thanks to the release team hammering things around until it went. Most of the outstanding autipkgtest failures with python3.8 were fixed either in unstable or in git/BTS. Here are the remaining issues that someone (who isn't me) should have a look at: celery/4.2.1-5: #952217 autorm 4/13 circlator/1.5.6-1: 954403 against joblib fades/8.1-1: #950858 autorm 3/29 fdroidserver/1.1.6-1: #954395 meson/0.52.1-1: #952610 natsort/6.0.0-1.2: #950221 new upstream needs packaging autorm 4/13 python-icecream/1.3.1-1: #950847 needs new upstream autorm 3/29 qiime/2019.10.0-1: #950842 autorm 4/13 spades/3.13.1+dfsg-2: 954403 against joblib vulture/0.21-1.1: #950861 needs new upstream autorm 4/13 xapers/0.8.2-1.1: #954805 Scott K signature.asc Description: This is a digitally signed message part.
python3-openvdb: build against the default python3 version
Hi all, Could anyone point me at a Debian package (possibly using dh) where multiple compilation are done (one against python3.7 and one against python3.8). I'd like to avoid re-inventing the wheel for building a cmake package (c++) which ships a single python module (so I need to do one configure+build+install per python version). Thanks, On Fri, Mar 27, 2020 at 12:57 PM Emilio Pozuelo Monfort wrote: > > Control: reopen -1 7.0.0-1 > Control: retitle -1 python3-openvdb: build against the default python3 version > > On Mon, 24 Feb 2020 11:10:49 +0100 Mathieu Malaterre wrote: > > Control: tags -1 + patch > > Control: retitle -1 replace python3-all-dev with python3.7-dev > > Err, that's not really the solution. > > The not ideal solution was to build for the default python version, i.e. > build-depend on python3-dev and use python3. That would have built against > python3.7 when that was the default, and against python3.8 now that it has > changed. And with a binNMU from the release team, you wouldn't have even > noticed. > > The ideal solution is to build against python3-all-dev and build for *all* > supported python versions. So that when python3.7 and python3.8 are both > supported, you build the python extension for both of them. > > Cheers, > Emilio
Re: python3-openvdb: build against the default python3 version
Pybuild has a cmake plugin that I think is relatively new. It may handle the complexity for you, but I've never tried it. We used to do this with pykde4, which is available on snapshot..d.o. Scott K On Friday, March 27, 2020 8:48:33 AM EDT Mathieu Malaterre wrote: > Hi all, > > Could anyone point me at a Debian package (possibly using dh) where > multiple compilation are done (one against python3.7 and one against > python3.8). I'd like to avoid re-inventing the wheel for building a > cmake package (c++) which ships a single python module (so I need to > do one configure+build+install per python version). > > Thanks, > > On Fri, Mar 27, 2020 at 12:57 PM Emilio Pozuelo Monfort > > wrote: > > Control: reopen -1 7.0.0-1 > > Control: retitle -1 python3-openvdb: build against the default python3 > > version> > > On Mon, 24 Feb 2020 11:10:49 +0100 Mathieu Malaterre wrote: > > > Control: tags -1 + patch > > > Control: retitle -1 replace python3-all-dev with python3.7-dev > > > > Err, that's not really the solution. > > > > The not ideal solution was to build for the default python version, i.e. > > build-depend on python3-dev and use python3. That would have built against > > python3.7 when that was the default, and against python3.8 now that it has > > changed. And with a binNMU from the release team, you wouldn't have even > > noticed. > > > > The ideal solution is to build against python3-all-dev and build for *all* > > supported python versions. So that when python3.7 and python3.8 are both > > supported, you build the python extension for both of them. > > > > Cheers, > > Emilio signature.asc Description: This is a digitally signed message part.
Re: Python3.8 as default final status
On 27.03.2020 20:44, Scott Kitterman wrote: > On Friday, March 27, 2020 3:39:30 PM EDT Scott Kitterman wrote: >> On Friday, March 27, 2020 3:21:38 PM EDT Håvard Flaget Aasen wrote: >>> On 27.03.2020 20:09, Sergio Durigan Junior wrote: On Friday, March 27 2020, Scott Kitterman wrote: > The python3-defaults with python3.8 as the default python3 has migrated > to > Testing thanks to the release team hammering things around until it > went. Thanks for this. > Most of the outstanding autipkgtest failures with python3.8 were fixed > either in unstable or in git/BTS. Here are the remaining issues that > someone (who isn't me) should have a look at: > > celery/4.2.1-5: #952217 autorm 4/13 FWIW, I looked at this a little bit, but could not make much progress. I'm very interested in fixing this since it impacts pagure. I'll try to investigate more this weekend, but if someone else wants to take a look (and let me know), you're more than welcome! >>> >>> I believe I already fixed that package, it's waiting for someone to >>> review and upload it. Did you look at the repository in salsa? >>> >>> >>> Håvard >> >> I didn't. The ones I knew about having fixed in git or patches in the BTS, >> I didn't include. I didn't go through and check them all. >> >> Scott K > > I should read more carefully. I failed to note that this wasn't directed at > me. Nevermind. > > Scott K > Yet, I probably could have communicated better. I just placed it in the subject line on IRC, and assumed it would be found. Håvard
Re: Python3.8 as default final status
On Friday, March 27 2020, Scott Kitterman wrote: > The python3-defaults with python3.8 as the default python3 has migrated to > Testing thanks to the release team hammering things around until it went. Thanks for this. > Most of the outstanding autipkgtest failures with python3.8 were fixed either > in unstable or in git/BTS. Here are the remaining issues that someone (who > isn't me) should have a look at: > > celery/4.2.1-5: #952217 autorm 4/13 FWIW, I looked at this a little bit, but could not make much progress. I'm very interested in fixing this since it impacts pagure. I'll try to investigate more this weekend, but if someone else wants to take a look (and let me know), you're more than welcome! Thanks, -- Sergio GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36 Please send encrypted e-mail if possible http://sergiodj.net/ signature.asc Description: PGP signature
Re: Python3.8 as default final status
On 27.03.2020 20:09, Sergio Durigan Junior wrote: > On Friday, March 27 2020, Scott Kitterman wrote: > >> The python3-defaults with python3.8 as the default python3 has migrated to >> Testing thanks to the release team hammering things around until it went. > > Thanks for this. > >> Most of the outstanding autipkgtest failures with python3.8 were fixed >> either >> in unstable or in git/BTS. Here are the remaining issues that someone (who >> isn't me) should have a look at: >> >> celery/4.2.1-5: #952217 autorm 4/13 > > FWIW, I looked at this a little bit, but could not make much progress. > I'm very interested in fixing this since it impacts pagure. I'll try to > investigate more this weekend, but if someone else wants to take a look > (and let me know), you're more than welcome! > I believe I already fixed that package, it's waiting for someone to review and upload it. Did you look at the repository in salsa? Håvard
Re: Python3.8 as default final status
On Friday, March 27, 2020 3:21:38 PM EDT Håvard Flaget Aasen wrote: > On 27.03.2020 20:09, Sergio Durigan Junior wrote: > > On Friday, March 27 2020, Scott Kitterman wrote: > >> The python3-defaults with python3.8 as the default python3 has migrated > >> to > >> Testing thanks to the release team hammering things around until it went. > > > > Thanks for this. > > > >> Most of the outstanding autipkgtest failures with python3.8 were fixed > >> either in unstable or in git/BTS. Here are the remaining issues that > >> someone (who isn't me) should have a look at: > >> > >> celery/4.2.1-5: #952217 autorm 4/13 > > > > FWIW, I looked at this a little bit, but could not make much progress. > > I'm very interested in fixing this since it impacts pagure. I'll try to > > investigate more this weekend, but if someone else wants to take a look > > (and let me know), you're more than welcome! > > I believe I already fixed that package, it's waiting for someone to > review and upload it. Did you look at the repository in salsa? > > > Håvard I didn't. The ones I knew about having fixed in git or patches in the BTS, I didn't include. I didn't go through and check them all. Scott K signature.asc Description: This is a digitally signed message part.
Re: Python3.8 as default final status
On Fri, 27 Mar 2020 at 11:12:35 -0400, Scott Kitterman wrote: > meson/0.52.1-1: #952610 This is fixed in experimental. The version in experimental is an unrelated new upstream release candidate, but the relevant packaging change seems readily backportable. smcv
Re: Python3.8 as default final status
On Friday, March 27, 2020 3:39:30 PM EDT Scott Kitterman wrote: > On Friday, March 27, 2020 3:21:38 PM EDT Håvard Flaget Aasen wrote: > > On 27.03.2020 20:09, Sergio Durigan Junior wrote: > > > On Friday, March 27 2020, Scott Kitterman wrote: > > >> The python3-defaults with python3.8 as the default python3 has migrated > > >> to > > >> Testing thanks to the release team hammering things around until it > > >> went. > > > > > > Thanks for this. > > > > > >> Most of the outstanding autipkgtest failures with python3.8 were fixed > > >> either in unstable or in git/BTS. Here are the remaining issues that > > >> someone (who isn't me) should have a look at: > > >> > > >> celery/4.2.1-5: #952217 autorm 4/13 > > > > > > FWIW, I looked at this a little bit, but could not make much progress. > > > I'm very interested in fixing this since it impacts pagure. I'll try to > > > investigate more this weekend, but if someone else wants to take a look > > > (and let me know), you're more than welcome! > > > > I believe I already fixed that package, it's waiting for someone to > > review and upload it. Did you look at the repository in salsa? > > > > > > Håvard > > I didn't. The ones I knew about having fixed in git or patches in the BTS, > I didn't include. I didn't go through and check them all. > > Scott K I should read more carefully. I failed to note that this wasn't directed at me. Nevermind. Scott K signature.asc Description: This is a digitally signed message part.
Re: Python3.8 as default final status
On Friday, March 27 2020, Håvard Flaget Aasen wrote: > On 27.03.2020 20:09, Sergio Durigan Junior wrote: >> On Friday, March 27 2020, Scott Kitterman wrote: >> >>> The python3-defaults with python3.8 as the default python3 has migrated to >>> Testing thanks to the release team hammering things around until it went. >> >> Thanks for this. >> >>> Most of the outstanding autipkgtest failures with python3.8 were fixed >>> either >>> in unstable or in git/BTS. Here are the remaining issues that someone (who >>> isn't me) should have a look at: >>> >>> celery/4.2.1-5: #952217 autorm 4/13 >> >> FWIW, I looked at this a little bit, but could not make much progress. >> I'm very interested in fixing this since it impacts pagure. I'll try to >> investigate more this weekend, but if someone else wants to take a look >> (and let me know), you're more than welcome! >> > > I believe I already fixed that package, it's waiting for someone to > review and upload it. Did you look at the repository in salsa? I had looked at the repository when I was working with the package. I see you pushed your changes 2 days ago, but the last time I looked at the package was at least 7 days ago. Anyhow, I thank you for letting me know, but I am not sure I am satisfied with the solution. You basically disabled the test on Python 3.8, which obviously works, but doesn't really tell me whether there was indeed a problem with the package/testcase or not. My approach (failed, so far) was to try and figure out what was happening, and then devise a proper fix for it. My next step was going to be to involve upstream in this. Would you like to follow up with them and check if they're are aware of the failure? Maybe they already have a proper solution for it. Thanks, -- Sergio GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36 Please send encrypted e-mail if possible http://sergiodj.net/ signature.asc Description: PGP signature
