Path: csiph.com!weretis.net!feeder8.news.weretis.net!news.samoylyk.net!gothmog.csi.it!bofh.it!news.nic.it!robomod From: Tomasz Rybak Newsgroups: linux.debian.maint.python Subject: Consul library packaging Date: Wed, 17 Jul 2024 22:20:02 +0200 Message-ID: X-Original-To: debian-python@lists.debian.org X-Mailbox-Line: From debian-python-request@lists.debian.org Wed Jul 17 20:18:39 2024 Old-Return-Path: X-Amavis-Spam-Status: No, score=-113.873 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HEXHASH_WORD=1, LDO_WHITELIST=-5, MD5_SHA1_SUM=-1, PGPSIGNATURE=-5, RCVD_IN_DNSWL_MED=-2.3, SARE_MSGID_LONG40=0.637, UNPARSEABLE_RELAY=0.001, USER_IN_DKIM_WELCOMELIST=-0.01, USER_IN_DKIM_WHITELIST=-100] autolearn=ham autolearn_force=no Reply-To: debian-python@lists.debian.org Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="=-nu0zIvLaSpI8K1YKndBf" User-Agent: Evolution 3.52.3-1 MIME-Version: 1.0 X-Debian-User: serpent X-Mailing-List: archive/latest/22078 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/86f9b5439cfbb02b3f29c587ef54382c9f82d47b.camel@debian.org Approved: robomod@news.nic.it Lines: 83 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: osallou@debian.org, lolando@debian.org, tchet@debian.org X-Original-Date: Wed, 17 Jul 2024 22:18:08 +0200 X-Original-Message-ID: <86f9b5439cfbb02b3f29c587ef54382c9f82d47b.camel@debian.org> Xref: csiph.com linux.debian.maint.python:16041 --=-nu0zIvLaSpI8K1YKndBf Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello. I'm writing trying to understand current status of Consul-related packages. Therefore I put all people who were involved in packaging them into CC. Currently we have 2 packages in the team: * python-consul, packaged by Olivier Sallou in 2017-08-30 * python-consul2, packaged by Roland Mas in 2021-09-19 Unfortunately both packages are in quite old versions and haven't seen new versions uploaded to Debian since initial upload. python-consul got two additional uploads by Holger Levsen and Sandro Tossi - both were Debian releases, fixing problems with package but not updating it to the new version. Therefore package is still in original version 0.7.1 from 2017. python-consul2 is in similar state: it also had few additional uploads but also stays in version 0.1.5 from 2021. I guess the problem is caused by mess with upstream repositories. python-consul was packaged from https://github.com/cablehead/python-consul tag v0.7.1, commit a343f96d0b755407dfbb07d9efdc8b2b977bcc41 from Mon Aug 7 16:21:10 2017 +0530 There were some other commits, but development stopped in August of 2018. python-consul2 was packaged from https://github.com/poppyred/python-consul2.git, most probably from latest commit 7aa1ff4103f6c8e6e79d614bbcd554b6e835a6f9 from Thu Feb 18 18:29:16 2021 +0800. This repository was fork of cablehead repository, but changed versioning (from 0.7.1 to 0.1.5); it had some activity between September 2019 and November 2020. It looks like currently development occurs at https://github.com/criteo/py-consul.git. It's forked from latest commit from cablehead repository, 53eb41c4760b983aec878ef73e72c11e0af501bb. Looks like development from poppyred repository was not copied. Alexandre Detiste started working on updating python-consul packaging: he updated upstream to 1.5.0 and worked on dependencies. Unfortunately looks like nothing happened since May. I'm interested in Python Consul package, as I'm using it at work. Alexandre - do you need help with packaging? Question to DPT - what are we doing with python-consul2? I'd propose to RM it after uploading newest version pf python-consul, but wanted to discuss it first. Best regards. --=20 Tomasz Rybak, Debian Developer GPG: A565 CE64 F866 A258 4DDC=C2=A0F9C7 ECB7 3E37 E887 AA8C --=-nu0zIvLaSpI8K1YKndBf Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- iQJHBAABCgAxFiEE1bhtbqZEgXjcK9cyggqgxGY3jWkFAmaYJwATHHNlcnBlbnRA ZGViaWFuLm9yZwAKCRCCCqDEZjeNafxwD/9NbxdN/tDb33JpEGFLQsNGbKn4w0Oj Pkv/JRWI8x5p/ix04PSIw2+3ivZ1yikrw1Qo8HsV7gKJw3bjlF0jOzp6YF+CQLdd Swy2V3qlcAGXD4veEuLra0hJz/l9Na1TCebaIf8cLoc4go9ItbRbk/ttlF7ynAMz l9gMclFmNrsk2YwpVYpKYdLvosZ8xICy5tYmLLhJ3Ner5os0YQavb1WJuRPlJ+Ew k286eNcpNz3OJ05/5mA38jUP1PiybPDxFC5QdghWHZten9HCribG3qe0772Jt6TL bh66THWH5975qtq/2LpVCajOYOk84BTlciAz6WpKKLZno4PFfrFIe3FtyZeGA5sI T8CX2W0e3BPoiiF07Ebe7/cfb3sXujQNfwMAZ4KxmoOTrbpLyzHZqvGek5Sbo6LQ jzZnexfgxHivlb3Zrh63OAg7Yi8lNbb8o5fm1Dka3naJFl+sHIQUnpa/sNuMoxNV WD4NGYt1H2HhFVKbNGCgOExQHGEsho7kzd2uzfen7R815aWcldD/bPl0kpBWrjTA vGneRHMj4qXBLzYsKmgFymgdV7ZVJMzQ/6E9OxWsomKN9ZRp5j90WnHjOo3Nuw99 J+/Mp7oySG1b5sytjE+IzrTqWGOJKZXEdEdd6Y1oSOFwjmCsxaQJ9RIIyIDQhvic mPL+NL5cU2O92w== =KFwS -----END PGP SIGNATURE----- --=-nu0zIvLaSpI8K1YKndBf--