Bug#1070772: ITP: python-mutf8 -- encoders and decoders for the MUTF-8 character encoding
Package: wnpp Severity: wishlist Owner: Alexandre Detiste X-Debbugs-Cc: debian-de...@lists.debian.org, debian-python@lists.debian.org * Package name: python-mutf8 Version : 1.0.0 Upstream Contact: Tyler Kennedy * URL : https://pypi.org/project/mutf8/ * License : MIT Programming Lang: Python Description : encoders and decoders for the MUTF-8 character encoding This package contains simple pure-python as well as C encoders and decoders for the MUTF-8 character encoding. In most cases, it can also parse the even-rarer CESU-8. These days, you'll most likely encounter MUTF-8 when working on files or protocols related to the JVM. Strings in a Java .class file are encoded using MUTF-8, strings passed by the JNI, as well as strings exported by the object serializer. This library was extracted from Lawu, a Python library for working with JVM class files. I will maintain this inside DPT. This is a new dependency of androguard
Re: please be more careful about your team uploads
It is now in the NEW queue. https://salsa.debian.org/python-team/packages/python-pytest-relaxed/-/pipelines/675307 Le mer. 8 mai 2024 à 16:19, Antoine Beaupré a écrit : > On 2024-05-08 16:11:46, Alexandre Detiste wrote: > > Ok I guess you want to do this one: > > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008768 > > Not really! It's a RFP, if I was going to do it, I would have renamed > that package to "ITP" and reassigned it... > > a.
Bug#1070759: new upstream release
Package: fabric Version: 2.6.0-1 Severity: wishlist X-Debbugs-Cc: debian-python@lists.debian.org A new upstream release is available for Fabric (3.2.2 at the time of writing). It depends on the new pytest-relaxed package, missing from Debian, itself blocked on upstream upgrading their pytest support (#1008768). -- System Information: Debian Release: 12.5 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable-debug'), (500, 'stable'), (1, 'experimental'), (1, 'unstable'), (1, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.6.13+bpo-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages fabric depends on: ii libjs-sphinxdoc5.3.0-4 ii python33.11.2-1+b1 ii python3-fabric 2.6.0-1 ii python3-pkg-resources 66.1.1-1 fabric recommends no packages. fabric suggests no packages. -- no debconf information
Bug#1070758: new upstream release (2.2.0)
Package: python3-invoke Version: 2.0.0-1 Severity: wishlist X-Debbugs-Cc: debian-python@lists.debian.org, Alexandre Detiste Invoke has had several releases that are not included yet in Debian. I had started working on updating to 2.2.0 but got blocked on pytest-relaxed missing from Debian, itself blocked on upstream upgrading their pytest support (#1008768). Right now, the git repository is in bad shape, as it has some blobs from 2.2.0 but not the latest changes from unstable, so that needs to be fixed first. I tried to do it myself but failed, so I'm hoping the uploader (tchet, in cc) can handle this first. -- System Information: Debian Release: 12.5 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable-debug'), (500, 'stable'), (1, 'experimental'), (1, 'unstable'), (1, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.6.13+bpo-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-invoke depends on: ii python33.11.2-1+b1 ii python3-pkg-resources 66.1.1-1 ii python3-six1.16.0-4 ii python3-yaml 6.0-3+b2 python3-invoke recommends no packages. Versions of packages python3-invoke suggests: pn python-invoke-doc -- no debconf information
Re: please be more careful about your team uploads
On 2024-05-08 10:18:27, Antoine Beaupré wrote: > On 2024-05-08 16:08:07, Alexandre Detiste wrote: >> Hi, >> >> That was the very first day I got to work on DPT packages; >> so well yes, I did some mistakes at first; >> and having been DM for far too long (~10 years) I needed to retrain; >> I had so many things stuck in my queue at first. >> >> https://lists.debian.org/debian-python/2023/12/msg00012.html >> >> >> I'm now going through the ITP's >> needed for stalled package updates. > > Great to have you onboard, just don't forget to push next time. :) Actually, now that I look at the git history, you *did* push changes to that repository, they're just different from what was uploaded. I can't make heads or tails out of this. Could you make sure the python-invoke git repository is in sync with the archive now please? A.
Re: please be more careful about your team uploads
On 2024-05-08 10:18:27, Antoine Beaupré wrote: > On 2024-05-08 16:08:07, Alexandre Detiste wrote: >> Hi, >> >> That was the very first day I got to work on DPT packages; >> so well yes, I did some mistakes at first; >> and having been DM for far too long (~10 years) I needed to retrain; >> I had so many things stuck in my queue at first. >> >> https://lists.debian.org/debian-python/2023/12/msg00012.html >> >> >> I'm now going through the ITP's >> needed for stalled package updates. > > Great to have you onboard, just don't forget to push next time. :) Actually, now that I look at the git history, you *did* push changes to that repository, they're just different from what was uploaded. I can't make heads or tails out of this. Could you make sure the python-invoke git repository is in sync with the archive now please? A.
Re: please be more careful about your team uploads
On 2024-05-08 16:08:07, Alexandre Detiste wrote: > Hi, > > That was the very first day I got to work on DPT packages; > so well yes, I did some mistakes at first; > and having been DM for far too long (~10 years) I needed to retrain; > I had so many things stuck in my queue at first. > > https://lists.debian.org/debian-python/2023/12/msg00012.html > > > I'm now going through the ITP's > needed for stalled package updates. Great to have you onboard, just don't forget to push next time. :) For what it's worth, my trick for this is i register my local git repos in myrepos and run "mr status" from time to time, which tells me when i forget to push. I do try to be particularly more careful when i work on team packages, especially if i'm not an uploader... A. -- Only after disaster can we be resurrected. It's only after you've lost everything that you're free to doanything. Nothing is static, everything is evolving, everything is falling apart. - Chuck Palahniuk, Fight Club
Re: please be more careful about your team uploads
On 2024-05-08 16:11:46, Alexandre Detiste wrote: > Ok I guess you want to do this one: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008768 Not really! It's a RFP, if I was going to do it, I would have renamed that package to "ITP" and reassigned it... a. -- I would defend the liberty of consenting adult creationists to practice whatever intellectual perversions they like in the privacy of their own homes; but it is also necessary to protect the young and innocent. - Arthur C. Clarke
Re: please be more careful about your team uploads
On 2024-05-08 16:08:07, Alexandre Detiste wrote: > Hi, > > That was the very first day I got to work on DPT packages; > so well yes, I did some mistakes at first; > and having been DM for far too long (~10 years) I needed to retrain; > I had so many things stuck in my queue at first. > > https://lists.debian.org/debian-python/2023/12/msg00012.html > > > I'm now going through the ITP's > needed for stalled package updates. Great to have you onboard, just don't forget to push next time. :) For what it's worth, my trick for this is i register my local git repos in myrepos and run "mr status" from time to time, which tells me when i forget to push. I do try to be particularly more careful when i work on team packages, especially if i'm not an uploader... A. -- Only after disaster can we be resurrected. It's only after you've lost everything that you're free to doanything. Nothing is static, everything is evolving, everything is falling apart. - Chuck Palahniuk, Fight Club
Re: please be more careful about your team uploads
On 2024-05-08 16:11:46, Alexandre Detiste wrote: > Ok I guess you want to do this one: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008768 Not really! It's a RFP, if I was going to do it, I would have renamed that package to "ITP" and reassigned it... a. -- I would defend the liberty of consenting adult creationists to practice whatever intellectual perversions they like in the privacy of their own homes; but it is also necessary to protect the young and innocent. - Arthur C. Clarke
Re: please be more careful about your team uploads
Ok I guess you want to do this one: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008768
Re: please be more careful about your team uploads
Hi, That was the very first day I got to work on DPT packages; so well yes, I did some mistakes at first; and having been DM for far too long (~10 years) I needed to retrain; I had so many things stuck in my queue at first. https://lists.debian.org/debian-python/2023/12/msg00012.html I'm now going through the ITP's needed for stalled package updates. Greetings Le mer. 8 mai 2024 à 15:58, Antoine Beaupré a écrit : > > Hi, > > I'm working on updating the python-invoke package and see you've done > two uploads on the package: > > https://tracker.debian.org/news/1491303/accepted-python-invoke-200-11-source-into-unstable/ > https://tracker.debian.org/news/1491393/accepted-python-invoke-200-12-source-into-unstable/ > > So, first off: thanks for fixing those issues! :) > > But, second, could you be a little more careful about how you do those? > Normally, I would have expected those changes to be pushed to salsa so > that I can build on top of. > > Or, at the very least, you should have sent a debdiff... The uploads are > a little bizarre too, because they have a NMU-like versionn number > (e.g. 2.0.0-1.1) yet they say "Team upload" on the changelog. Clearly > that should have yielded lintian warnings, did you ignore those? > > In any case, i'm now in the rather unfortunate position of having to > retrofit that stuff back in the package, and it's making my life a > little harder than it should... > > So please be a little more careful next time around, thanks! > > a.
please be more careful about your team uploads
Hi, I'm working on updating the python-invoke package and see you've done two uploads on the package: https://tracker.debian.org/news/1491303/accepted-python-invoke-200-11-source-into-unstable/ https://tracker.debian.org/news/1491393/accepted-python-invoke-200-12-source-into-unstable/ So, first off: thanks for fixing those issues! :) But, second, could you be a little more careful about how you do those? Normally, I would have expected those changes to be pushed to salsa so that I can build on top of. Or, at the very least, you should have sent a debdiff... The uploads are a little bizarre too, because they have a NMU-like versionn number (e.g. 2.0.0-1.1) yet they say "Team upload" on the changelog. Clearly that should have yielded lintian warnings, did you ignore those? In any case, i'm now in the rather unfortunate position of having to retrofit that stuff back in the package, and it's making my life a little harder than it should... So please be a little more careful next time around, thanks! a. -- I know where I am going, and I know the truth, and I do not have to be what you want me to be. I am free to be what I want. - Muhammad Ali
