Request to join the DPT
Hi, I'd like to join the Debian Python Team. My salsa handle: gracinet I have read the team policy [1] and agree with it. My immediate concern would be to package the Evolve Mercurial extension [2], which is an important piece in many recent Mercurial workflows. I see there is an old RFP about hg-evolve [3], and perhaps will I file an ITP, if that is the right place to ask general questions to start in the right direction, given there's some history to clarify. More generally, I can help with other Mercurial extensions or related stuff, as I can work closely with upstream on that. I have been on the verge of doing Debian packaging for a very long time, but never had the opportunity to go all the way before now. All the best, [1] https://salsa.debian.org/python-team/tools/python-modules/-/blob/master/policy.rst (currently at e9b10b44c4ec737922b08bc43d7437c593da6183) [2] https://pypi.org/project/hg-evolve/ [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926398 -- Georges Racinet https://octobus.net, https://about.heptapod.host, https://heptapod.net GPG: BF5456F4DC625443849B6E58EE20CA44EF691D39, sur serveurs publics OpenPGP_signature Description: OpenPGP digital signature
Bug#1008744: ITP: mercurial-evolve -- This package provides the "evolve" extension for the Mercurial DVCS.
Package: wnpp Severity: wishlist Owner: Georges Racinet X-Debbugs-Cc: debian-de...@lists.debian.org, debian-python@lists.debian.org * Package name: mercurial-evolve Version : 10.5.0 Upstream Author : Pierre-Yves David * URL : https://www.mercurial-scm.org/doc/evolution/ * License : GPLv2+ Programming Lang: Python Description : evolve extension for Mercurial This package provides the experimental "evolve" extension for the Mercurial DVCS. . This extension provides several commands to mutate history and deal with issues it may raise. There is an old RFP about this: #926398 The "evolve" and "topic" extensions have become central in many modern Mercurial usages. The first exposes the core primitives for history mutation (aka changeset obsolescence) in an user-friendly way, the second provides volatile feature branches and handle them with evolve. The upstream source repository already contains a debian/ subdirectory, which various people have been using to generate a mercurial-evolve package. It would probably be a good idea to provide the same content, if the policy allows it. The above long description is the one given in this existing packaging effort. The corresponding project name on PyPI is hg-evolve, and also contains the "topic", "pullbundles" and "serverminitopic" extensions. The latter two are made of a single file. I plan to maintain this package under the umbrella of the Debian Python Team. As long as this is a pure Python package, upgrades should be fairly simple. I have a working prototype at https://salsa.debian.org/gracinet/mercurial-evolve (feedback most welcome). As far as I understand, I have enough rights to move it directly under python-team/packages, but I will need a sponsor for the actual uploading. This is my first actual packaging attempt, I would appreciate mentorship and especially indications about the next steps.
Re: RFS: mercurial-evolve
On 07/09/2022 09:12, Andrej Shadura wrote: Hi, On Tue, 6 Sep 2022, at 14:53, Andrej Shadura wrote: On Tue, 6 Sep 2022, at 14:45, Georges Racinet wrote: I'm looking for a sponsor for my package "mercurial-evolve". I’ve made some changes and uploaded evolve to NEW. In one commit I made a "typo" and wrote a wrong word: "Drop unnecessary variable names". What I meant was, of course, "variables" :) Anyway, DH_VERBOSE=1 is better set by the maintainer rather than directly in debian/rules, as it’s a bit too verbose, and this package is not too tricky to require it at all times. I can’t remember right now how exactly PYBUILD_NAME works, but I don’t think you were using it correctly here, and it didn’t make any visible difference anyway (likely because there’s only one binary package), so I dropped it. I'll look into it. Other than that, the rest of the commits are minor nitpicks and are, hopefully, self-descriptive. Thank you for the fixes / improvements, and for the upload, this is great! Thanks, you did a good job on your first Debian package :) :-) I still have some rookie questions, don't worry :-) -- Georges Racinet https://octobus.net, https://heptapod.net GPG: BF5456F4DC625443849B6E58EE20CA44EF691D39, sur serveurs publics OpenPGP_signature Description: OpenPGP digital signature
Re: RFS: mercurial-evolve
On 07/09/2022 11:41, Nicolas Chauvat wrote: Hi List, Le Wed, Sep 07, 2022 at 09:12:05AM +0200, Andrej Shadura a écrit : Thanks, you did a good job on your first Debian package :) Nice to this the progress made for this package. I look forward to using it ! Well, thank you and Logilab for supporting the effort! -- Georges Racinet https://octobus.net, https://heptapod.net GPG: BF5456F4DC625443849B6E58EE20CA44EF691D39, sur serveurs publics OpenPGP_signature Description: OpenPGP digital signature
RFS: mercurial-evolve
Dear Python Maintainers, I'm looking for a sponsor for my package "mercurial-evolve". The salsa project is https://salsa.debian.org/python-team/packages/mercurial-evolve/ My own ITP is https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008744 (don't hesitate to tell if I should file an RFS in the bugs.debian.org as well) (Cc-ing DDs I've spoken about it in the past) Many thanks! -- Georges Racinet https://octobus.net, https://heptapod.net GPG: BF5456F4DC625443849B6E58EE20CA44EF691D39, sur serveurs publics
Re: RFS: mercurial-evolve
Hi, I just made a new version of the mercurial-evolve package, following the new upstream 10.5.3. It's still at https://salsa.debian.org/python-team/packages/mercurial-evolve. Andrej, would you be so kind to take a look at it, I hope the package can make it before the freeze. On the technical side, this new upsteam version provides compatibility with Mercurial 6.3 (which I see has come up since last attempt) and Python 3.11, according to the changelog, I didn't follow details myself. I believe I had formerly addressed the ftpmaster reservations about the copyright statements, but feel free to tell me if there is something else to be done. Best, On 9/7/22 09:12, Andrej Shadura wrote: Hi, On Tue, 6 Sep 2022, at 14:53, Andrej Shadura wrote: On Tue, 6 Sep 2022, at 14:45, Georges Racinet wrote: I'm looking for a sponsor for my package "mercurial-evolve". (Cc-ing DDs I've spoken about it in the past) Cool. I'm a little bit busy right now packing for the trip, but I will have a look at it a bit later this afternoon. I’ve made some changes and uploaded evolve to NEW. In one commit I made a "typo" and wrote a wrong word: "Drop unnecessary variable names". What I meant was, of course, "variables" :) Anyway, DH_VERBOSE=1 is better set by the maintainer rather than directly in debian/rules, as it’s a bit too verbose, and this package is not too tricky to require it at all times. I can’t remember right now how exactly PYBUILD_NAME works, but I don’t think you were using it correctly here, and it didn’t make any visible difference anyway (likely because there’s only one binary package), so I dropped it. Other than that, the rest of the commits are minor nitpicks and are, hopefully, self-descriptive. Thanks, you did a good job on your first Debian package :) -- Georges Racinet https://octobus.net, https://about.heptapod.host, https://heptapod.net GPG: BF5456F4DC625443849B6E58EE20CA44EF691D39, sur serveurs publics OpenPGP_signature Description: OpenPGP digital signature
Re: RFS: mercurial-evolve
Hello, On 1/16/23 23:44, Georges Racinet wrote: Hi, I just made a new version of the mercurial-evolve package, following the new upstream 10.5.3. It's still at https://salsa.debian.org/python-team/packages/mercurial-evolve. Andrej, would you be so kind to take a look at it, I hope the package can make it before the freeze. Is there something I should do to help make this happen? If I read it right, soft freeze is on 2023-03-12 Andrej, Julien maybe ? Best, On the technical side, this new upsteam version provides compatibility with Mercurial 6.3 (which I see has come up since last attempt) and Python 3.11, according to the changelog, I didn't follow details myself. I believe I had formerly addressed the ftpmaster reservations about the copyright statements, but feel free to tell me if there is something else to be done. Best, On 9/7/22 09:12, Andrej Shadura wrote: Hi, On Tue, 6 Sep 2022, at 14:53, Andrej Shadura wrote: On Tue, 6 Sep 2022, at 14:45, Georges Racinet wrote: I'm looking for a sponsor for my package "mercurial-evolve". (Cc-ing DDs I've spoken about it in the past) Cool. I'm a little bit busy right now packing for the trip, but I will have a look at it a bit later this afternoon. I’ve made some changes and uploaded evolve to NEW. In one commit I made a "typo" and wrote a wrong word: "Drop unnecessary variable names". What I meant was, of course, "variables" :) Anyway, DH_VERBOSE=1 is better set by the maintainer rather than directly in debian/rules, as it’s a bit too verbose, and this package is not too tricky to require it at all times. I can’t remember right now how exactly PYBUILD_NAME works, but I don’t think you were using it correctly here, and it didn’t make any visible difference anyway (likely because there’s only one binary package), so I dropped it. Other than that, the rest of the commits are minor nitpicks and are, hopefully, self-descriptive. Thanks, you did a good job on your first Debian package :) -- Georges Racinet https://octobus.net, https://about.heptapod.host, https://heptapod.net GPG: BF5456F4DC625443849B6E58EE20CA44EF691D39, sur serveurs publics OpenPGP_signature Description: OpenPGP digital signature
Re: RFS: mercurial-evolve
On 2/6/23 10:26, Andrej Shadura wrote: Hi, On Mon, 6 Feb 2023, at 10:05, Georges Racinet wrote: Hello, On 1/16/23 23:44, Georges Racinet wrote: Hi, I just made a new version of the mercurial-evolve package, following the new upstream 10.5.3. It's still at https://salsa.debian.org/python-team/packages/mercurial-evolve. Andrej, would you be so kind to take a look at it, I hope the package can make it before the freeze. Is there something I should do to help make this happen? If I read it right, soft freeze is on 2023-03-12 Andrej, Julien maybe ? Did you get the rejection email? Apparently a few more copyright entries are missing. No, sorry I haven't noticed. Just to be sure, you're talking of one for 10.5.3 ? -- Georges Racinet https://octobus.net, https://about.heptapod.host, https://heptapod.net GPG: BF5456F4DC625443849B6E58EE20CA44EF691D39, sur serveurs publics OpenPGP_signature Description: OpenPGP digital signature
Re: RFS: mercurial-evolve
On 2/6/23 12:07, Georges Racinet wrote: On 2/6/23 10:26, Andrej Shadura wrote: Hi, On Mon, 6 Feb 2023, at 10:05, Georges Racinet wrote: Hello, On 1/16/23 23:44, Georges Racinet wrote: Hi, I just made a new version of the mercurial-evolve package, following the new upstream 10.5.3. It's still at https://salsa.debian.org/python-team/packages/mercurial-evolve. Andrej, would you be so kind to take a look at it, I hope the package can make it before the freeze. Is there something I should do to help make this happen? If I read it right, soft freeze is on 2023-03-12 Andrej, Julien maybe ? Did you get the rejection email? Apparently a few more copyright entries are missing. No, sorry I haven't noticed. Just to be sure, you're talking of one for 10.5.3 ? Got it now, sorry. I'm on it, will push again today -- Georges Racinet https://octobus.net, https://about.heptapod.host, https://heptapod.net GPG: BF5456F4DC625443849B6E58EE20CA44EF691D39, sur serveurs publics OpenPGP_signature Description: OpenPGP digital signature
