Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.python > #16041 > unrolled thread

Consul library packaging

Back to article view | Back to linux.debian.maint.python

Contents

  Consul library packaging Tomasz Rybak <serpent@debian.org> - 2024-07-17 22:20 +0200
    Re: Consul library packaging Alexandre Detiste <alexandre.detiste@gmail.com> - 2024-07-17 22:40 +0200
    Re: Consul library packaging olivier sallou <olivier.sallou@gmail.com> - 2024-07-17 22:50 +0200
      Re: Consul library packaging Alexandre Detiste <alexandre.detiste@gmail.com> - 2024-07-17 23:00 +0200

#16041 — Consul library packaging

[Multipart message — attachments visible in raw view] — view raw

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.

-- 
Tomasz Rybak, Debian Developer <serpent@debian.org>
GPG: A565 CE64 F866 A258 4DDC F9C7 ECB7 3E37 E887 AA8C

[toc] | [next] | [standalone]

#16043

Le mer. 17 juil. 2024 à 22:18, Tomasz Rybak <serpent@debian.org> a écrit :
> I'm interested in Python Consul package, as I'm using it at work.
> Alexandre - do you need help with packaging?
Yes I need help with this one. I won't be available for two more weeks

> 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.

If I ask "ben", it says nothing needs python3-consul2 anymore;
I'd propose to file the RM bug right away.

ben query '.build-depends ~ "python3-consul2"' $Sources -s Package,Maintainer
ben query '.build-depends-indep ~ "python3-consul2"' $Sources -s
Package,Maintainer
ben query '.depends ~ "python3-consul2"' $Packages -s Package,Maintainer

[toc] | [prev] | [next] | [standalone]

#16044

[Multipart message — attachments visible in raw view] — view raw

Le mer. 17 juil. 2024, 22:18, Tomasz Rybak <serpent@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 <serpent@debian.org>
> GPG: A565 CE64 F866 A258 4DDC F9C7 ECB7 3E37 E887 AA8C
>

[toc] | [prev] | [next] | [standalone]

#16045

Le mer. 17 juil. 2024 à 22:43, olivier sallou
<olivier.sallou@gmail.com> a écrit :
> Or adding a new python-consul3 package
Please no

There are not so many reverse dependencies to begin with
(and 0 for python3-consul2) a new version of consul would be first uploaded
to experimental.


Debian Med Packaging Team <debian-med-packaging@lists.alioth.debian.org>
  biomaj3-daemon
  biomaj3-download
  biomaj3-process
  biomaj3-user

Debian OpenStack <team+openstack@tracker.debian.org>
  masakari-monitors
  python-tooz

Debian PostgreSQL Maintainers <team+postgresql@tracker.debian.org>
  patroni

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.maint.python

csiph-web