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

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

Rayforge packaging effort – request for guidance and team maintenance

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

Contents

  Rayforge packaging effort – request for guidance and team maintenance Michele Cane <michele.cane@proton.me> - 2026-05-29 15:10 +0200
    Re: Rayforge packaging effort – request for guidance and team maintenance Michele Cane <michele.cane@proton.me> - 2026-05-30 11:30 +0200

#17505 — Rayforge packaging effort – request for guidance and team maintenance

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

Hello Rust and Python teams,

I am reaching out because I have started working on packaging Rayforge for Debian.

For details about the project, please see the ITP:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1137607

I previously reached out to mentors.debian.net and was advised to upload my repositories to Salsa and contact the relevant teams to seek guidance, review, and potential inclusion under the appropriate team-maintained namespaces.

The current packaging repositories are available on Salsa:

-   rayforge: https://salsa.debian.org/heiserhorn/rayforge
    

-   raygeo: https://salsa.debian.org/heiserhorn/raygeo
    

-   pyvips: https://salsa.debian.org/heiserhorn/pyvips
    

-   vtracer: https://salsa.debian.org/heiserhorn/vtracer
    

-   visioncortex: https://salsa.debian.org/heiserhorn/visioncortex
    

-   flo_curves: https://salsa.debian.org/heiserhorn/flo_curves
    

-   clipper2: https://salsa.debian.org/heiserhorn/clipper2
    

-   rstar: https://salsa.debian.org/heiserhorn/rstar
    

-   pyo3-stub-gen: https://salsa.debian.org/heiserhorn/pyo3-stub-gen
    

-   setuptools-git-versioning: https://salsa.debian.org/heiserhorn/setuptools-git-versioning
    

-   clipper2c-sys: https://salsa.debian.org/heiserhorn/clipper2c-sys
    

-   Clipper2C: https://salsa.debian.org/heiserhorn/Clipper2C
    

-   arduino-asyncudp: https://salsa.debian.org/heiserhorn/arduino-asyncudp
    


The following packages have been identified as direct or indirect dependencies of Rayforge (the list may not yet be exhaustive):

Rust:

-   raygeo
    

-   vtracer
    

-   visioncortex
    

-   flo_curves
    

-   clipper2
    

-   rstar
    

-   pyo3-stub-gen
    

-   clipper2c-sys
    


Python:

-   pyvips
    

-   setuptools-git-versioning
    


C++:

-   Clipper2C
    

-   arduino-asyncudp
    


Current status:

The following packages are lintian-clean and build successfully with sbuild using only dependencies already available in Debian:

-   flo_curves (Rust)
    

-   rstar (Rust)
    

-   setuptools-git-versioning (Python)
    

-   Clipper2C (C++)
    

-   arduino-asyncudp (C++)
    


For the remaining packages, I have already started preparing the packaging repositories and Debian branches, but some depend on packages that are not yet available in Debian or require updates before they can be completed.

In particular, pyo3-stub-gen currently depends on packages that are already present in Debian but require updates:

-   librust-inventory-dev
    

-   librust-rustpython-parser-dev
    

-   librust-ordered-float-dev
    


For these, I have already opened or updated the relevant bug reports.

I would appreciate guidance on the following points:

-   Should the Rust packages be maintained under the Debian Rust Team?
    

-   Should the Python packages be maintained under the Debian Python Team?
    

-   What would be the preferred maintenance model for the two C++ packages?
    

-   Should the main Rayforge package be maintained under the Python Team, the Debian Science Team, or another team?
    


For context, I have some previous Debian packaging experience dating back 10–15 years, but this is my first packaging effort involving a dependency tree of this size and complexity.

Any guidance, review, or suggestions would be greatly appreciated.

Many thanks,

Mike

Michele Cane,PhD

[toc] | [next] | [standalone]

#17507

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

Thank Alexandre,

This is very useful. I will drop the packaging of setuptools-git-versioning and replace the dependency by a patch like the ones you shared.

Cheers

Mike


Michele Cane, PhD

On Friday, 29 May 2026 at 23:22, Alexandre Detiste <alexandre.detiste@gmail.com> wrote:

> Hi,
> 

> Nobody answered yet, so I'll answer on the only one package I know
> about: setuptools-git-versioning
> 

> I've been annoyed several times by package who don't return version
> info through importlib.metadata;
> enough to check the problem more deeply and fix what I could  (by
> adding python3-setuptools-scm most of the time)
> 

> The cases boil down to this:
>      apt-file search --filter-suites unstable,experimental --
> '-0.0.0.' | grep -e egg-info -e dist-info | cut -d: -f1 | sort -u >
> liste
> 

> Many of those will document an optional dependency on
> setuptools-git-versioning and do fine without.
> 

> Some are patched out, see
> https://codesearch.debian.net/search?q=setuptools-git-versioning&literal=1
> - toolz
> - the patch is needed becaue upstream depends on
> setuptools-git-versioning, which is not available in Debian.
>      https://sources.debian.org/src/python-logistro/2.0.1+dfsg1-2/tests/test_version.py?hl=13#L13
> 

> So it seems a nice addition; but I'm not sure it would so much useful
> as-is for regular packages.
> 

> We would most likely need glue similar to the "export
> SETUPTOOLS_SCM_PRETEND_VERSION"
> thing done by dh-python
> 

> Greetings
> 

> Alexandre
> 

> PS: theres is also this lintian request worth checking:
>        https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034588
> 

> 

> Le ven. 29 mai 2026 à 15:03, Michele Cane <michele.cane@proton.me> a écrit :
> > setuptools-git-versioning: https://salsa.debian.org/heiserhorn/setuptools-git-versioning
> >
> > The following packages have been identified as direct or indirect dependencies of Rayforge (the list may not yet be exhaustive):
> > Python:
> > setuptools-git-versioning
> 

[toc] | [prev] | [standalone]

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

csiph-web