On 2026-06-18 04:18, Michele Cane wrote:
Hello Debian Python Team,
I would like to request access to the Debian Python Team Salsa namespace.
My Salsa login is: heiserhorn
I am working on packaging Rayforge for Debian. The related ITP is:
#1137607 ITP: rayforge
https://bugs.debian.org/1137607
Rayforge is a Python desktop application for laser cutting and engraving. I
would like to maintain the Python parts of this dependency chain in a
team-maintainable way under the Debian Python Team, following the team workflow.
Current Python packaging work includes:
* python-asyncudp
- Salsa repo currently under my namespace:
https://salsa.debian.org/heiserhorn/python-asyncudp
- Imported from the PyPI release tarball using gbp/pristine-tar.
- Branches: debian/sid, upstream, pristine-tar.
- Builds successfully with sbuild.
- Deep lintian has no errors.
* python-pyvips
- Salsa repo currently under my namespace:
https://salsa.debian.org/heiserhorn/pyvips
- Imported/maintained with upstream, pristine-tar, and debian/sid
branches.
- Updated packaging for current Debian sid libvips transition.
- Builds successfully with sbuild.
- Upstream tests pass for supported Python versions.
- Deep lintian currently only reports the expected
initial-upload-closes-no-bugs warning.
Remaining Python packages in the Rayforge chain are:
* raygeo / python3-raygeo
- Needed by Rayforge.
- Packaging is blocked on the Clipper2 chain:
Clipper2C -> clipper2c-sys -> clipper2 -> raygeo.
- rstar is already available in Debian, but raygeo still needs clipper2.
* vtracer / python3-vtracer
- Needed by Rayforge.
- Python package is blocked on the Rust vtracer/visioncortex chain.
- The Rust vtracer packaging has already been prepared and built locally
against local visioncortex packages.
* rayforge
- Final application package.
- Current Debian packaging already tracks dependencies on
python3-asyncudp, python3-pyvips, python3-raygeo, and python3-vtracer.
- Upload-readiness depends on the above Python/Rust/C++ dependency chain
becoming available in Debian.
Related Rust/C++ progress already done in support of this Python packaging
work:
* rstar: accepted in Debian unstable.
* source-location: packaged, merged in the Debian Rust Team repository,
and accepted in Debian unstable.
* flo_curves: accepted in Debian unstable. Follow-up i386 test fix MR
prepared.
* visioncortex: packaged, MR opened, CI passed.
* vtracer: packaging prepared and successfully built locally against local
visioncortex packages.
* Clipper2C: standalone C++ packaging prepared and pushed.
* clipper2c-sys and clipper2: Rust packaging prepared and locally
validated against local Clipper2C packages, waiting for the C++ dependency to
be available in Debian.
I have read the Debian Python Team policy:
https://salsa.debian.org/python-team/tools/python-modules/-/blob/master/policy.rst
and I accept it. I intend to follow the team workflow, including using
upstream release tarballs, pristine-tar, and team-maintainable packaging
suitable for transfer into python-team/packages.
Thank you,
Mike
Michele Cane, PhD
Welcome to the team!
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau
⢿⡄⠘⠷⠚⠋ [email protected] / veronneau.org
⠈⠳⣄
