-> Ying-Chun Liu (PaulLiu) <[email protected]>, 2026-08-15T08:55:00Z -> > > On 8/15/26 3:24 PM, Blair Noctis wrote: >> -> PaulLiu <[email protected]>, 2026-06-24T01:13:54+0100 -> >>> Hi Jonas, >>> >>> Can you explain this a bit? I'm still new to Rust. >>> >>> From crates.io, tonic and tonic-prost are different crates. >>> And tonic 0.12.* depends on prost. >>> But on tonic 0.14.6, it didn't depend on prost. >>> >>> Does that mean if we update tonic to 0.14, then we need to package this >>> anyway? >>> >>> Yours, >>> Paul >> It's not about Rust, it's about how Debian's Rust packaging works, and the >> current, somewhat less optimal scene. >> >> There are two ways to package Rust things in Debian; the Debian Rust team >> uses >> an "unconventional" workflow, while some others, along with some in the Rust >> team who are not satisfied with that, use a more "conventional" workflow. >> >> Jonas goes conventional. He packages the entire tonic workspace, including >> but >> not limited to tonic, tonic-build, and, among others, tonic-prost. >> >> Your words indicate that you only ever got to know about the Rust team's >> workflow. It's not your problem per se, there is a lack of communication >> between those two crowds, and there's no indication that a Rust team member, >> or, someone going the team's unconventional flow, should avoid packaging >> tonic >> crates. >> >> I do, however, question why you uploaded it while not even familiar with the >> Rust team's workflow, as evidenced by [MR#1205]. > > > I've written that in the merge request already. The release.sh said that > I can upload. And > > it even gives me the dput command for me to run. So I run that command > and then it get uploaded. > > And it is the conventional way to me, just I used some extra tools from > the Rust team. > > I mean, the source package generated by those tools just looks good to > me. And upload it to salsa is just some extra good steps for me to do. > But without uploading to salsa is also ok for me personally. As not all > the packages I maintain is in salsa. I'll consider if the package is > really used by a lot of people or need to be maintained by group. And if > someone asks me to upload it to salsa because he wants to help, I'm > happy to do it too. But if it is just a dependencies of something I > maintain for myself, I usually don't upload it to salsa as there will be > only me anyway.
My apologies for the accusing tone earlier. It's not really helpful for solving
the problem at hand.
I can see how the output from release.sh led you to believe that it's ready to
upload. It should distinguish between mechanical readiness (whether it builds)
and coordination (whether the upload conflicts with existing work). I should
not have framed this simply as being unfamiliar with a specific workflow.
There is nothing wrong with using the tooling; my main concern is about the
resulting maintenance designation. The tooling marks Maintainer as Debian Rust
Maintainers, and Vcs-Git as debcargo-conf's repo on salsa. These designate it
as team maintained, where coordination with the team is not merely optional
"extra steps".
Nothing wrong with solo maintenance. If that was your intention, however, the
package should have named you as the Maintainer instead, with appropriate Vcs-*
fields pointing to a repo of yours, or, if you prefer, without them.
A separate issue is that tonic-prost is part of the upstream tonic workspace.
As the Rust team workflow packages crates.io releases as separate source
packages in Debian, it's reasonable on a technical ground to follow it when
using the team's tooling; nevertheless, it is the maintainer's responsibility
to identify and examine the upstream source for possible problems. Such
procedure should have surfaced src:rust-tonic here, prompting coordination that
would have prevented this conflict.
Thank you for helping resolve the conflict.
--
,Sdrager
Blair Noctis
🇵🇸
signature.asc
Description: PGP signature
