Re: cargo-debstatus: Connection timed out (os error 110)

On Sun, May 3, 2026, at 2:02 PM, Jerome BENOIT wrote:
> Hello, thanks for the feed back.
>
> On 02/05/2026 21:14, Fabian Grünbichler wrote:
>> On Sat, May 2, 2026, at 9:01 PM, Jerome BENOIT wrote:
>>> Hello,
>>>
>>> I am on my way to package a software partially written in rust and in python.
>>> I may add that rust is new for me.
>>> Whatever, I gave it a try to cargo-debstatus,
>>> but it keeps stalling and terminating with the message
>>>
>>> Error: A worker crashed
>>>   
>>> Caused by:
>>>       0: error connecting to server: Connection timed out (os error 110)
>>>       1: Connection timed out (os error 110)
>>>
>>> Can anyone give a hint to solve this issue ?
>> 
>> Which version of cargo-debstatus are you using? which crate/project are
>> you running it on?
>
> I am working a schroot Sid environment, so I am using cargo-debstatus 
> version 0.6.5-6.
>
> I am working on packaging fontship [1]. It is a mixture a python and 
> rust and autotools.
>> 
>> It sounds to me like it fails/failed to connect to UDD. If you run it
>> with `RUST_LOG=debug cargo debstatus` it will be more verbose (you
>> can also use `info` or `trace` as levels).
>
> Indeed. It was blocked by my firewall. Now I can get the list.
>
> However, for now, I am not sure what to do with the list.
> I was hoping to get a Build-Depends list to insert as-is in `debian/control`.

Yes, cargo-debstatus will only tell you which parts of the dependency
tree are already packaged, and which aren't (or might need patching
or upgrading to match).

If you want to get a starting point for d/control, you can run
`debcargo deb-dependencies` or `debcargo update-dependencies`,
the latter will directly change d/control. I recommend running
it in cycles combined with patching Cargo.toml (and potentially
Rust source code) to match which versions are in the archive.

> Can you point me to Debian packages of software that might look like 
> fontship [1] ?

There's a few packages that use cargo to build Rust code without
being pure Rust:

- papers (and many similar GNOME applications using meson)
- python-cryptography (and similar python/rust projects using pyo3)
- ..

I suggest taking a look at the Debian Rust team documentation as
well:

https://rust-team.pages.debian.net/book/process-workspace.html#manual-wrapper-approach

There's also a specific discussion list: [email protected]

Hope this helps,
Fabian