packaging rfc3161-client

[Simon Josefsson]

Hi Rust & Python teams,

I would like to package:

https://github.com/trailofbits/rfc3161-client

It is a Python library that ships with and needs a Rust crate to work,
the separation is best explained by upstream:

It is composed of three subprojects:

🊀 tsp-asn1: A Rust crate using rust-asn1 to create the types used by
the Time-Stamp protocol. This crate depends on rust-asn1 and
cryptography to minimize the amount of duplicated code. While it is
usable as a standalone crate, this is not officially supported. Drop
us a message if you are interested in using it.

🊀 rfc3161-client: Another Rust crate that provides Python bindings
to the tsp-asn1 crate using PyO3.

🐍 rfc3161-client A Python library using the crate above to provide a
usable API to create Timestamp Request and read Timestamp Response.

Are there similar projects that are packaged in Debian that I look at
for inspiration?

Any thoughts on if this be split up into two separate Debian source
packages, one maintained by the rust team following their policies and
ship the crates - and one source package maintained by the python team
following their policies that ship the library and depend on the rust
packages -- or just one source package with a more complicated
maintainership and build process?

I have started python-like packaging here:

https://salsa.debian.org/python-team/packages/python-rfc3161-client/

However it lacks the Rust part. Would someone who knows Rust want to
join me working on this package? I'm still learning Python packaging so
I hope to help on that, but I haven't done any Rust packaging at all...
forks, merge requests, commits etc appreciated.

/Simon

[weepingclown]

Hi,

Top of my head, there is src:pendulum and src:python-orjson. *Probably* anything with a python3-maturin build-dep can be of help.

Best,
Ananthu

Post by Simon Josefsson
Are there similar projects that are packaged in Debian that I look at
for inspiration?

[Alexander Kjäll]

Hi

As long as the Rust crates are published on crates.io then I think it would
be easiest to package them in the rust team :)

Post by Simon Josefsson
Hi Rust & Python teams,
https://github.com/trailofbits/rfc3161-client
It is a Python library that ships with and needs a Rust crate to work,
🊀 tsp-asn1: A Rust crate using rust-asn1 to create the types used by
the Time-Stamp protocol. This crate depends on rust-asn1 and
cryptography to minimize the amount of duplicated code. While it is
usable as a standalone crate, this is not officially supported. Drop
us a message if you are interested in using it.
🊀 rfc3161-client: Another Rust crate that provides Python bindings
to the tsp-asn1 crate using PyO3.
🐍 rfc3161-client A Python library using the crate above to provide a
usable API to create Timestamp Request and read Timestamp Response.
Are there similar projects that are packaged in Debian that I look at
for inspiration?
Any thoughts on if this be split up into two separate Debian source
packages, one maintained by the rust team following their policies and
ship the crates - and one source package maintained by the python team
following their policies that ship the library and depend on the rust
packages -- or just one source package with a more complicated
maintainership and build process?
https://salsa.debian.org/python-team/packages/python-rfc3161-client/
However it lacks the Rust part. Would someone who knows Rust want to
join me working on this package? I'm still learning Python packaging so
I hope to help on that, but I haven't done any Rust packaging at all...
forks, merge requests, commits etc appreciated.
/Simon

[Simon Josefsson]

* dulwich
* python-upstream-ontologist
* ruff

Thanks!

As long as the Rust crates are published on crates.io then I think it would
be easiest to package them in the rust team :)

They aren't on creates.io. Since the need arose from a python library,
I'll see if I can complete this within the python team, but if the Rust
part of this package turns out to be heavy I think that is a bad idea
and it should be split up or moved to Rust team. Maybe upstream could
publish the Rust crate on crates.io and separate the project into two
parts eventually.

Hi,
Top of my head, there is src:pendulum and src:python-orjson. *Probably* anything with a python3-maturin build-dep can be of help.

Thank you!

I will try to learn from python-upstream-ontologist and python-orjson
which looks closest to this package.

/Simon

[Jelmer Vernooij]

Post by Simon Josefsson
Hi Rust & Python teams,
https://github.com/trailofbits/rfc3161-client
It is a Python library that ships with and needs a Rust crate to work,
🦀 tsp-asn1: A Rust crate using rust-asn1 to create the types used by
the Time-Stamp protocol. This crate depends on rust-asn1 and
cryptography to minimize the amount of duplicated code. While it is
usable as a standalone crate, this is not officially supported. Drop
us a message if you are interested in using it.
🦀 rfc3161-client: Another Rust crate that provides Python bindings
to the tsp-asn1 crate using PyO3.
🐍 rfc3161-client A Python library using the crate above to provide a
usable API to create Timestamp Request and read Timestamp Response.
Are there similar projects that are packaged in Debian that I look at
for inspiration?
Any thoughts on if this be split up into two separate Debian source
packages, one maintained by the rust team following their policies and
ship the crates - and one source package maintained by the python team
following their policies that ship the library and depend on the rust
packages -- or just one source package with a more complicated
maintainership and build process?
https://salsa.debian.org/python-team/packages/python-rfc3161-client/
However it lacks the Rust part. Would someone who knows Rust want to
join me working on this package? I'm still learning Python packaging so
I hope to help on that, but I haven't done any Rust packaging at all...
forks, merge requests, commits etc appreciated.

I've packaged a few Python packages that are fully or partially built in rust. The simplest examples are probably:

* dulwich
* python-upstream-ontologist

More advanced are e.g.:

* ruff

If you have any questions, feel free to reach out.

Cheers,

Jelmer