Le mer. 17 juil. 2024, 22:18, Tomasz Rybak <serp...@debian.org> a écrit :
> 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. > Hi, Problem is indeed to follow code switching to different repositories.... And the many api/abi breaks in library (with no major version upgrade) Upgrading would be a good thing, but before upgrading python-consul you need to check impacted packages as newer versions are not compatible. New package must specify it breaks older versions (just debian control spec), but will also break packages using old version. According to impacted packages, packages could upgrade if possible but a bit complex as mean updating some upstream code to handle change, or ask upstream to do so, but no guarantee.... Or adding a new python-consul3 package (or whatever major version), which will live next to other packages waiting for their removal (some day according to usage) Olivier > Best regards. > > -- > Tomasz Rybak, Debian Developer <serp...@debian.org> > GPG: A565 CE64 F866 A258 4DDC F9C7 ECB7 3E37 E887 AA8C >
