Re: Requesting membership in Debian Python team for Taavi Väänänen
On 2024-08-10 2 h 34 a.m., Taavi Väänänen wrote: Hi, I'm requesting membership in the Debian Python team in order to adopt[0] the mwclient package[1] which seems like a good fit for the team. I have read and accept the Python team policy. My Salsa username is 'taavi'. [0]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068659 [1]: https://tracker.debian.org/pkg/mwclient thanks in advance, Taavi Access granted. Welcome to the team! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ OpenPGP_0xE1E5457C8BAD4113.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Re: Alternative libraries for PEP-594
On 2024-08-03 4 h 02 a.m., Matthias Klose wrote: On 03.08.24 07:25, Louis-Philippe Véronneau wrote: On 2024-08-02 20:40, Blair Noctis wrote: to scale it out in an external source package which is effectively going against Python upstream, allowing the thing to live on, and people to say "it's still alive in Debian!" Also, even python3.11 is still there. Sure someone needing something expunged from 3.13 would be fine staying with 3.12? The idea of having these libraries around for Trixie (and to remove them after the release) is to ease the 3.13 transition. From my preliminary analysis, there are more than 600 packages that use one of the stdlib that'll be removed in 3.13. There's also the option to remove packages from testing and/or unstable. I assume, we'll see a lot of packages still using old modules getting removed from testing, once 3.13 becomes the default. It's also an option to remove those completely, if they are not maintained. That is a lot of work and I doubt we'll have a successful transition without this temporary measure. can we agree on a naming for the packaging, e.g. python3-zombie- , so that we make it clear, that people are using obsolete code? we do that for python3-zombie-imp already. I like this a lot and I support this naming scheme. -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ OpenPGP_0xE1E5457C8BAD4113.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Re: new dependencies for python-pint
kind reminder Il 09/08/24 21:08, Antonio Valentino ha scritto: Dear Thomas, dear all, a new version (0.24.3) of python-pint is available upstream. It introduces two additional dependencies: flexcache and flexparser. I have files two ITP bugs: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1078258 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1078260 and prepared the debian packages in salsa: https://salsa.debian.org/python-team/packages/flexparser https://salsa.debian.org/python-team/packages/flexcache If you agree I would like to maintain them under the debian-python team. I'm a DM so I can take in charge of the maintenance and normal uploads, but I cannot upload new packages. I kindly a DD to review and sponsor the initial upload of flexcache and flexparser. kind regards -- Antonio Valentino
Re: Moving default branch after project creation
Am 10.08.24 um 00:01 schrieb Alexandru Mihail: Thanks everyone for chiming in ! Debates around the branch name aside, I still can't find out how to access the Gitlab settings button to change the default to anything. It's a permissions thing I think. When I access a project under my personal namespace I see the settings button, all is well. Here, it's just missing. I was able to create the project, of course. The structure of the tree hasn't changed since the last time i was looking into, did you read my previous email in detail? $ git logg * commit 4c0b559c9f60321be2fa412d73555ab38c517f16 (origin/pristine-tar) Author: Alexandru Mihail Date: Wed Aug 7 19:11:03 2024 +0300 pristine-tar data for psrecord_1.4.orig.tar.gz * commit 1443d1a19aeed367f2f2131757f01e2b9eafcfb4 (tag: upstream/1.4, origin/upstream, origin/debian/master, upstream) | Author: Alexandru Mihail | Date: Wed Aug 7 18:46:41 2024 +0300 | | New upstream version 1.4 | * commit 4c41bddf5c750a5c694aaba42c8252b444856ff7 (HEAD -> main, origin/main, origin/HEAD) Author: Alexandru Mihail Date: Wed Aug 7 15:21:38 2024 + Initial commit The structure of the tree is simply wrong, given you are at the beginning I suggest to drop the current tree and restart from scratch within your namespace. For me it makes no sense to work further on that base. It make things unnecessary harder. Once it's working on your side it's easy to push then the tree to the repo on the DPT in Salsa again. -- Regards Carsten
