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

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

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

> 
> If you are on IRC, feel free to join #debian-rust on IRC, we're happy
> to help :)

IRC is no yet my thing.

> 
> Fabian
> 

Best wishes,
Jerome


[1] https://github.com/theleagueof/fontship