Re: Asking for help Poetry
On Sat, May 8, 2021 at 9:56 PM Emmanuel Arias wrote: > On 5/8/21 10:37 PM, Sandro Tosi wrote: > > On Mon, Mar 15, 2021 at 10:29 AM Emmanuel Arias wrote: > >> On Mon, Mar 15, 2021 at 4:22 AM Sandro Tosi wrote: > * poetry-core failing https://ci.debian.net/packages/p/poetry-core/ > >>> are you handling this failure? > > looks like this is fixed in git: do you need a sponsor? > Yes, please. Thanks! sounds good, i'll have a look at this package soon and let you know > * python-cleo in review > https://salsa.debian.org/python-team/packages/cleo I hope finished this > week > > stefanor uploaded it a few days ago > Yes. > * poetry still in progress > https://salsa.debian.org/python-team/packages/poetry -> need help and > reviews > > for this one it looks like you imported a new upstream release a week > > ago: is there something we can help/check about poetry? > > I've just push some advances. Currently, I'm working on tests, if you > want to take a look. maybe just ask here (or directly to me) if you have questions and what's failing/needs work, so we dont duplicate work > We need new upstream release for python-httpretty (for tests), that I > upload to mentors [0]. @zigo ask me about test that this new upstream > release doesn't break > cloud-init and python3-scciclient (I would like to take a look to ratt > for that). ratt is pretty great, and rather simple to use: - setup a sbuild schroot for unstable - build a binary package from the source you're working on - `ratt _amd64.changes` and then you'll get on screen the results for each package + a directory with the build results and logs https://github.com/Debian/ratt keep in mind it rebuilds packages sequentially, so it can take some time if the number of reverse deps is high. > Perhaps a good help from a more experienced person would be check if all > is ok with DFSG,that's my biggest concern. for which package specifically? while it's boring and long work, it's also rather trivial: look at every single file (yep, all of them) from the upstream source, and document their copyright and license in d/copyright -- happy to answer questions if you have something specific in mind about this Regards, -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
Re: Joining the team request
Hi Anton (2021.04.07_21:07:15_+) > I want to update some packages (for example astral - sure, respecting the > release policy) and also add some newer ones. I have read [1] and accept it. > My > salsa-login is gladk. Added, welcome to the team. > Please give me maintainer-permissions, so I will be able to setup CI-pipelines > for packages which I touch. Yeah, that's the standard level for the python team. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Re: Joining Debian Python Team
Hi Robbi (2021.04.14_04:50:55_+) > My salsa login is: @robbinespu > > I have have read the policy[6] and I accept it. Added you. Welcome to the team. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Re: Access request Salsa python-team unkn0wn-user
Hi Janis (2021.04.08_07:08:20_+) > as my last email stated, I am one of the upstream maintainers of NESi > [1] and would like to become part of the debian-python-team. > > I have read the policy that can be found under > https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst > and accept it. Added, welcome. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Re: Joining the team
Hi Stephan (2021.05.06_21:27:11_+) > My Salsa login is stephanlachnit. > > I have read the policy and accept it. Added to the Salsa project. Welcome to the team. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Re: Remove trac from Debian 11?
On 2021-05-10 14:00, Andrius Merkys wrote: > I do not think that slowing down of development is reason serious enough > to remove a package which is otherwise fine. Or are there other reasons > that I am not aware of? I don't have a problem with slow development, but the current version is probably not good enough to maintain it for some years. I'm optimistic, that in some months or so 1.6.x will be released, which should be fine. I'm planning to backport it to Debian 11, so that users still can install trac easily.
Re: Remove trac from Debian 11?
On Mon, May 10, 2021 at 10:35:41AM +, Martin wrote: > Now, while Trac is still maintained upstream and has been ported > to Python 3 recently, development slowed down since long and the > current 1.5.x release series is not yet "there". > > I wonder, whether the package should be part of Debian 11, or > better miss one stable release and have it in better shape for > Debian 12. I don't object. Typically I am against releasing knowingly not ready-to-ship software. If one of the maintainers comes up with a reasonable argument against this view, then we should listen to it. -- Best regards, Barin signature.asc Description: PGP signature
Re: Remove trac from Debian 11?
Hi Martin, On 2021-05-10 13:35, Martin wrote: > trac is a long-time Debian package, uploaded first by Jesus > Climent in 2004. I like the traditional look of Trac and its > climate-friendly resource usage :-) > > Now, while Trac is still maintained upstream and has been ported > to Python 3 recently, development slowed down since long and the > current 1.5.x release series is not yet "there". > > I wonder, whether the package should be part of Debian 11, or > better miss one stable release and have it in better shape for > Debian 12. > > If nobody objects, I'll file a bug to keep it out of Debian 11. I do not think that slowing down of development is reason serious enough to remove a package which is otherwise fine. Or are there other reasons that I am not aware of? Best, Andrius
Remove trac from Debian 11?
Dears, trac is a long-time Debian package, uploaded first by Jesus Climent in 2004. I like the traditional look of Trac and its climate-friendly resource usage :-) Now, while Trac is still maintained upstream and has been ported to Python 3 recently, development slowed down since long and the current 1.5.x release series is not yet "there". I wonder, whether the package should be part of Debian 11, or better miss one stable release and have it in better shape for Debian 12. If nobody objects, I'll file a bug to keep it out of Debian 11. Comments welcome! Cheers
