Re: help me update dateparser to 1.0.0 in time for bullseye
On 2021-02-05 04:41:37, Stefano Rivera wrote: > Hi Antoine (2021.02.05_02:13:56_+) >> I can't figure out how to update dateparser to 1.0.0. I am battling >> pytest and deps and failing. Seems like we'd need to package >> hijri_converter as a dependency, and fix the build so it doesn't require >> network. > > Also probably a good idea to package that CLDR data and rebuild the > tables from source. > > I pushed some commits to get the build time test passing. The > autopkgtest still needs to be changed to use pytest too, etc. > I'll finish this up later, and upload. > > Instead of my patches, you could have used pytest's > --continue-on-collection-errors flag. thanks stefano, you rock! and sorry for the state of the package, i know it's not exactly in sync with the best practices... -- La propriété est un piège: ce que nous croyons posséder nous possède. - Alphonse Karr
Ressurrecting freevial as the new upstream
[Please, keep me in Cc since I'm not subscribed] Last month I learnt that freevial had been removed[1] from unstable last year because upstream was unresponsive and it wasn't ported to Python 3, thus not fit for bullseye. It turns out that I personally know the people behind freevial because it was born as a game for the Catalan Ubuntu LoCoTeam, which I was part of some time back. So I contacted the main developer and he agreed for me to take over the project and try[2] to port it to Python 3. My python3 branch[3] currently works fine, though the code still needs more refactoring to make it fit Python 3 style guides. I'm also trying to build the package myself but I've never packaged a Python program before and it doesn't build successfully so far. Now I'm wondering if your team would like to keep maintaining freevial or should I join your team and take care of it myself (I don't plan to maintain any other Python packages for now). My main goal is to have freevial back in stable the sooner the better (I know it may be too late before soft-freeze, so I'll explore other options when the time comes) and promote it as a tool for engaging people in Debian Local Groups. Thanks a lot! Alex [1] https://tracker.debian.org/news/1113896/removed-13-21-from-unstable/ [2] https://github.com/freevial/freevial/pull/2 [3] https://github.com/freevial/freevial/tree/python3 -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Alex Muntada ⢿⡄⠘⠷⠚⠋ Debian Developer 🍥 log.alexm.org ⠈⠳⣄ signature.asc Description: PGP signature
Re: Downgrading dnspython back to 1.16.0 to fix Eventlet
On Thursday, February 4, 2021 4:49:21 AM EST Thomas Goirand wrote: > On 2/2/21 7:46 PM, Thomas Goirand wrote: > > Both Eventlet and DNSPython are monkey patching the standard SSL library > > in potentially conflicting ways > > After checking, that's *NOT* the case. Though Eventlet is doing > monkey-patching of dnspython, in a possible not-compatible with 2.x. > > Anyways, looks like this small patch fixes Eventlet with dnspython 2: > > https://github.com/tipabu/eventlet/commit/2f9b7969f9a66a75e72908454246b88bf5 > 7fe58a > > I've uploaded Debian release 0.26.1-5, and when it reaches the mirrors, > I'll try again to make OpenStack work, and see how it goes. If it fixes > everything, then we're good to go. Otherwise, my questioning about > downgrading dnspython to 1.16.0 still stand. I'll let you know. > > Cheers, > > Thomas Goirand (zigo) > > P.S: Thanks to Tim Burke for this patch If Eventlet is monkey patching DNSPython and it doesn't work, I think that's totally Eventlet's problem. Hopefully your patch works. I do not think downgrading DNSPython for this is a good idea. Scott K signature.asc Description: This is a digitally signed message part.
