Re: Request to join DPT
Hi Jakob, Jakob Haufe wrote on 27/03/2024 at 11:43:55+0200: > Hi all, > > I recently adopted intelhex[1] and would like to continue maintaining > it in the repo under the DPT group. > > My salsa username is sur5r[2]. > > I have read the policy[3] and accept it. > > Cheers, > sur5r > > [1] https://bugs.debian.org/976074 > [2] https://salsa.debian.org/sur5r > [3] > https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst Sorry for the delay, invitation sent! -- PEB signature.asc Description: PGP signature
Request to join DPT
Hi all, I recently adopted intelhex[1] and would like to continue maintaining it in the repo under the DPT group. My salsa username is sur5r[2]. I have read the policy[3] and accept it. Cheers, sur5r [1] https://bugs.debian.org/976074 [2] https://salsa.debian.org/sur5r [3] https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst -- ceterum censeo microsoftem esse delendam. pgpNQaVE73H1Z.pgp Description: OpenPGP digital signature
Re: Request to Join DPT
Hi, sorry for waiting and welcome :) ne 21. 2. 2021 v 12:57 odesílatel Lorenz Schori napsal: > Hi, > > I am the author of Prometheus PVE Exporter[1]. I recently discovered > that there is only one somewhat exotic dependency left (proxmoxer[2]) > which needs some love before Prometheus PVE Exporter itself could be > packaged for Debian. I'd like to bring that dependency up-to-date in a > first step and then propose to include Prometheus PVE Exporter after > that. > > My salsa username is: znerol > > I did read and I do accept the Debian Python Team Policy: > > https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst > > Cheers, > Lorenz > > 1) https://github.com/prometheus-pve/prometheus-pve-exporter > 2) https://salsa.debian.org/python-team/packages/proxmoxer > 3) https://www.debian.org/doc/packaging-manuals/python-policy/index.html > > -- S pozdravem/Best regards Ondřej Nový
Re: Updating proxmoxer [Was: Re: Request to Join DPT]
Hi Elena, On Thu, 11 Mar 2021 09:41:41 +0100 Elena ``of Valhalla'' wrote: > Yes, please, a merge request would help: I've looked into it a few > times already and wasn't able to finish it in the time I had. > > But since it's going into experimental, wouldn't it be better to > package the latest released version (1.1.1), or possibly even 1.2.0b1 > (the very latest version on pypi)? I followed the docs in the wiki[1] and it looks like gbp does its thing across three branches (debian/master, upstream and pristine-tar). Thus I opened three MRs with the result: https://salsa.debian.org/python-team/packages/proxmoxer/-/merge_requests/2 https://salsa.debian.org/python-team/packages/proxmoxer/-/merge_requests/3 https://salsa.debian.org/python-team/packages/proxmoxer/-/merge_requests/4 I used tar files downloaded from github for the intermediate releases and `gbp import-orig --pristine-tar --uscan` for the most recent one. I guess that the entries in the changelog could be squashed (unless we'd like to release 1.1.1 separately from 1.2.0b1). 1) https://wiki.debian.org/Python/GitPackaging#New_upstream_release HTH Lorenz
Re: Updating proxmoxer [Was: Re: Request to Join DPT]
On 2021-02-24 at 18:53:19 +0100, Lorenz Schori wrote: > > Version 1.0.4 has some small fixes for the ssh backend and some > > improvements for the http backend. Nothing major though. If it is > > viable to include that in bullseye, then why not. Also note that > > upstream changed to proxmoxer/proxmoxer. > > Would it help if I open merge requests for that (one against > pristine-tar, one against upstream and one against debian/master for > changelog etc.). Yes, please, a merge request would help: I've looked into it a few times already and wasn't able to finish it in the time I had. But since it's going into experimental, wouldn't it be better to package the latest released version (1.1.1), or possibly even 1.2.0b1 (the very latest version on pypi)? -- Elena ``of Valhalla'' signature.asc Description: PGP signature
Re: Updating proxmoxer [Was: Re: Request to Join DPT]
Hi, On Sun, 21 Feb 2021 17:50:43 +0100 Lorenz Schori wrote: > Version 1.0.4 has some small fixes for the ssh backend and some > improvements for the http backend. Nothing major though. If it is > viable to include that in bullseye, then why not. Also note that > upstream changed to proxmoxer/proxmoxer. Would it help if I open merge requests for that (one against pristine-tar, one against upstream and one against debian/master for changelog etc.). Cheers, Lorenz
Re: Updating proxmoxer [Was: Re: Request to Join DPT]
Hi Elena, On Sun, 21 Feb 2021 16:37:54 +0100 Elena ``of Valhalla'' wrote: > [...] > Have you already checked how significant the difference is? I suspect > that the delta would be too much to be reasonable even under the > current freeze rules (and Prometheus PVE Exporter as a new package > would need to target bookworm anyway): Version 1.0.4 has some small fixes for the ssh backend and some improvements for the http backend. Nothing major though. If it is viable to include that in bullseye, then why not. Also note that upstream changed to proxmoxer/proxmoxer. $ git diff --stat upstream/1.0.3...upstream/1.0.4 | grep py proxmoxer/__init__.py | 2 +- proxmoxer/backends/base_ssh.py | 2 +- proxmoxer/backends/https.py | 5 +- proxmoxer/core.py | 25 ++- setup.py| 2 +- tests/base/base_ssh_suite.py| 8 +- Version 1.1.0/1.1.1 introduces token authentication. There is no reason to rush that into bullseye though. There is still the option to push it to backports if people like that feature. > what would you think about an upload of updated proxmoxer to > experimental? Sure! Any progress is very welcome! Cheers, Lorenz
Updating proxmoxer [Was: Re: Request to Join DPT]
On 2021-02-21 at 12:50:16 +0100, Lorenz Schori wrote: > I am the author of Prometheus PVE Exporter[1]. I recently discovered > that there is only one somewhat exotic dependency left (proxmoxer[2]) > which needs some love before Prometheus PVE Exporter itself could be > packaged for Debian. I'd like to bring that dependency up-to-date in a > first step and then propose to include Prometheus PVE Exporter after Uh, I missed the fact that there is a new upstream version of proxmoxer, thanks for letting me notice. Have you already checked how significant the difference is? I suspect that the delta would be too much to be reasonable even under the current freeze rules (and Prometheus PVE Exporter as a new package would need to target bookworm anyway): what would you think about an upload of updated proxmoxer to experimental? -- Elena ``of Valhalla''
Request to Join DPT
Hi, I am the author of Prometheus PVE Exporter[1]. I recently discovered that there is only one somewhat exotic dependency left (proxmoxer[2]) which needs some love before Prometheus PVE Exporter itself could be packaged for Debian. I'd like to bring that dependency up-to-date in a first step and then propose to include Prometheus PVE Exporter after that. My salsa username is: znerol I did read and I do accept the Debian Python Team Policy: https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst Cheers, Lorenz 1) https://github.com/prometheus-pve/prometheus-pve-exporter 2) https://salsa.debian.org/python-team/packages/proxmoxer 3) https://www.debian.org/doc/packaging-manuals/python-policy/index.html
