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

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

packaging rfc3161-client

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

Contents

  packaging rfc3161-client Simon Josefsson <simon@josefsson.org> - 2024-12-26 16:00 +0100
    Re: packaging rfc3161-client weepingclown <weepingclown@disroot.org> - 2024-12-26 16:20 +0100
    Re: packaging rfc3161-client Alexander Kjäll <alexander.kjall@gmail.com> - 2024-12-26 16:40 +0100
    Re: packaging rfc3161-client Simon Josefsson <simon@josefsson.org> - 2024-12-26 16:40 +0100
      Re: packaging rfc3161-client Simon Josefsson <simon@josefsson.org> - 2025-08-26 15:00 +0200
        Re: packaging rfc3161-client Alexander Kjäll <alexander.kjall@gmail.com> - 2025-08-26 15:40 +0200
        Re: packaging rfc3161-client Louis-Philippe Véronneau <pollo@debian.org> - 2025-08-26 17:20 +0200
    Re: packaging rfc3161-client Jelmer Vernooij <jelmer@jelmer.uk> - 2024-12-26 16:40 +0100
    Bug#1120560: ITP: python-rfc3161-client -- Opinionated Python RFC3161 Client Simon Josefsson <simon@josefsson.org> - 2025-11-12 10:30 +0100

#16636 — packaging rfc3161-client

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

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

[toc] | [next] | [standalone]

#16637

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

On 26 December 2024 2:55:07 pm UTC, Simon Josefsson <simon@josefsson.org> wrote:
>Are there similar projects that are packaged in Debian that I look at
>for inspiration?

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

#16638

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

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 :)

On Thu, Dec 26, 2024, 15:55 Simon Josefsson <simon@josefsson.org> wrote:

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

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

#16640

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

Jelmer Vernooij <jelmer@jelmer.uk> writes:

> 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

Thanks!

Alexander Kjäll <alexander.kjall@gmail.com> writes:

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

weepingclown <weepingclown@disroot.org> writes:

> 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

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

#17032

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

Folks,

Is there someone who like to help on the rfc3161-client package, which
involves both Rust and Python?  Starting point is here:

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

Build failure here:
https://salsa.debian.org/python-team/packages/python-rfc3161-client/-/jobs/8106868

I haven't had time to look into the pointers given earlier, I am hoping
this is easy to solve for anyone familiar with Rust & Python packaging.

There is good interaction with upstream going on about dependencies for
the entire Sigstore stack --
https://github.com/sigstore/sigstore-python/issues/1524 -- and I think
we can influence things a little (like temporarily avoiding use of the
UV build system for some Python code) if we put some cycles into
preparing packages that are needed for Sigstore into Debian.

/Simon

Simon Josefsson <simon@josefsson.org> writes:

> Jelmer Vernooij <jelmer@jelmer.uk> writes:
>
>> 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
>
> Thanks!
>
> Alexander Kjäll <alexander.kjall@gmail.com> writes:
>
>> 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.
>
> weepingclown <weepingclown@disroot.org> writes:
>
>> 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
>

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

#17033

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

Looks like the build system isn't configured to use local packages and
instead tries to download them?

On Tue, Aug 26, 2025, 14:55 Simon Josefsson <simon@josefsson.org> wrote:

> Folks,
>
> Is there someone who like to help on the rfc3161-client package, which
> involves both Rust and Python?  Starting point is here:
>
> https://salsa.debian.org/python-team/packages/python-rfc3161-client
>
> Build failure here:
>
> https://salsa.debian.org/python-team/packages/python-rfc3161-client/-/jobs/8106868
>
> I haven't had time to look into the pointers given earlier, I am hoping
> this is easy to solve for anyone familiar with Rust & Python packaging.
>
> There is good interaction with upstream going on about dependencies for
> the entire Sigstore stack --
> https://github.com/sigstore/sigstore-python/issues/1524 -- and I think
> we can influence things a little (like temporarily avoiding use of the
> UV build system for some Python code) if we put some cycles into
> preparing packages that are needed for Sigstore into Debian.
>
> /Simon
>
> Simon Josefsson <simon@josefsson.org> writes:
>
> > Jelmer Vernooij <jelmer@jelmer.uk> writes:
> >
> >> 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
> >
> > Thanks!
> >
> > Alexander Kjäll <alexander.kjall@gmail.com> writes:
> >
> >> 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.
> >
> > weepingclown <weepingclown@disroot.org> writes:
> >
> >> 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
> >
>

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

#17034

On 2025-08-26 8 h 50 a.m., Simon Josefsson wrote:
> Folks,
> 
> Is there someone who like to help on the rfc3161-client package, which
> involves both Rust and Python?  Starting point is here:
> 
> https://salsa.debian.org/python-team/packages/python-rfc3161-client
> 
> Build failure here:
> https://salsa.debian.org/python-team/packages/python-rfc3161-client/-/jobs/8106868
> 
> I haven't had time to look into the pointers given earlier, I am hoping
> this is easy to solve for anyone familiar with Rust & Python packaging.
> 
> There is good interaction with upstream going on about dependencies for
> the entire Sigstore stack --
> https://github.com/sigstore/sigstore-python/issues/1524 -- and I think
> we can influence things a little (like temporarily avoiding use of the
> UV build system for some Python code) if we put some cycles into
> preparing packages that are needed for Sigstore into Debian.
> 
> /Simon
> 
> Simon Josefsson <simon@josefsson.org> writes:
> 
>> Jelmer Vernooij <jelmer@jelmer.uk> writes:
>>
>>> 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
>>
>> Thanks!
>>
>> Alexander Kjäll <alexander.kjall@gmail.com> writes:
>>
>>> 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.
>>
>> weepingclown <weepingclown@disroot.org> writes:
>>
>>> 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
>>

Here's an example of a Python project I worked on that uses maturin:

https://salsa.debian.org/python-team/packages/python-watchfiles

You'll need to patch the cargo file manually to use the right versions 
of the Rust packages in the Debian archive...

-- 
   ⢀⣴⠾⠻⢶⣦⠀
   ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
   ⢿⡄⠘⠷⠚⠋   pollo@debian.org / veronneau.org
   ⠈⠳⣄

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

#16641

On Thu, Dec 26, 2024 at 03:55:07PM +0100, Simon Josefsson wrote:
> 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.

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

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

#17140 — Bug#1120560: ITP: python-rfc3161-client -- Opinionated Python RFC3161 Client

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

Package: wnpp
Severity: wishlist
Owner: Simon Josefsson <simon@josefsson.org>

* Package name    : python-rfc3161-client
  Version         : 1.0.5
  Upstream Author : Trail of Bits
* URL             : https://github.com/trailofbits/rfc3161-client
* License         : Apache-2.0
  Programming Lang: Rust/Python
  Description     : Opinionated Python RFC3161 Client

rfc3161-client is a Python library implementing the Time-Stamp Protocol
(TSP) described in RFC 3161.

This package was discussed on the rust/python list earlier, but I didn't
file an ITP.  I'm resuming work and hope to make the NEW upload.

Packaging lives here:

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

/Simon

[toc] | [prev] | [standalone]

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

csiph-web