This source package is a duplicate of src:rust-tonic - please do not
soft-hijack an actively maintained package by introducing another
version in another source package.

You are quite welcome to join me in maintaining rust-tonic :-)

Kind regards,

 - Jonas
-----BEGIN PGP SIGNATURE-----

iQJABAEBCgAqFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmo5J+8MHGRyQGpvbmVz
LmRrAAoJECx8MUbBoAEh+csP/iVyysNPHjOcDDvWtudXTf/LokN91fvBgWt2A8RA
1KnqlnqC2kqzXMVDxnFbmm9J86pBdRoauZovJ1g6paCWx0hiEpMi01Whrxncz4Lu
JxPnwRpC4C30OtbBj3IEkeLuVI3veq66+pMQcL6VHxfNzFm9BKFzfyQgS+1GM37+
AcZL3YaZgSA6hgvIqO0B8nYO0dA5zaRiIbhoxID7DODTrPeMkCGZuUTUZ33tdIE9
UIkxaSEcQucNsi8S7VdC95EhjN4ZawTw/QNrglw4Lb4W9MYBIsTP45bb/ZIZWJHQ
Iy7AoJ+p5GoT+jHJoCYCJl906g43xYwr1YaqVzzgNP9Hdy+I6v5iP00w0cml21oL
DMT2VFLan4yQvPT66oxKoTMH6pnzNfOuEY85IRb5puJe7ImI0XhC187pm1/OeZ7+
vhB41AH8PjxkZHTD/PLtExGCMiJXR+dXgKI8LmYDNLch8kVcDTOVEcvutjfb1qlC
go8vKeSC6HJSiV4gzYyNEUEmt1V8c2Kj04fotxYvFwbU53/fkv8dMXLlgifj7N36
65qiUgMEF6tFLdeGaemhmptX/WhgFrCEkIlpoFRL3E202aenm/4cQxnIT2JakJQr
dmIu+Z0bwCnEB6VnAiW4/5P/sEDGL28kyBOGgUriRjYQOu0XXv5gZvssZe9GcUm5
xwFf
=6cj2
-----END PGP SIGNATURE-----

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

-> PaulLiu <pauliu@debian.org>, 2026-06-24T01:13:54+0100 ->

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

Please be respectful to things you aren't familiar with, and ask around to get
an idea of what you are doing before taking any material actions.

[MR#1205]: https://salsa.debian.org/rust-team/debcargo-conf/-/merge_requests/1205

Hi PaulLiu,

PaulLiu <pauliu@debian.org> wrote:

Sorry for my late response (and thanks to Blair for bringing my
attention to it): I had totally missed your email until now.

Yes, they are different crates, but part of same source project.

A crate is a packaging artifact in the crates.io distribution system.
Debian packages upstream preferred form for editing as a source package
and generates one or more binary packages from that source package.
Crates are sometimes similar to Debian source packages but they are not
upstream preferred form for editing, and for some upstream projects the
crate is not even close to being upstream preferred form for editing.

The Rust team tries to simplify maintenance of Rust code by attempting
to correlate crate.io and Debian packaging units. Sometimes it sort of
works, but sometimes it does not fit. Here it does not make sense to
look at crates: The tonic project is a set of multiple crates, and I
have packaged that in Debian as that set. It is wrong of others in
Debian to package the same thing again and calling it something else -
we call such an act "hijacking".

I am sure you did not intent to hijack the package that I maintain. It
seems from your question that you were not even aware that you were
working on the same thing as me. That confusion is a side-effect of the
Rust team simplification of their processes - but the Rust team is a
subset of Debian, and I am not part of the Rust team: They are free to
call a package a crate or call a crate a package, inside their team,
but I outside the team - in Debian - there is no such thing as a crate,
there are source packages corresponding to upstream preferred form for
editing, and there are binary packages. The upstream preferred form for
editing called "tonic" is already packaged, by me, as the source
package "rust-tonic" - please drop the duplicate work called
"rust-tonic-prost" because it really corresponds to the same upstream
preferred form for editing as the one I am maintaining.

Hope that makes sense.

Kind regards,

 - Jonas

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.

Hi Jonas,


Yes, I'll remove this package.


As I told you in the DebConf, I just want to package nostr relay program.

And rust-tonic is just one of the dependencies (3 or 4 layers deep maybe).

So I don't intent to hijack it.


I'll just remove this package anyway. And seek how to use rust-tonic
with prost.


Yours,
Paul

Quoting Ying-Chun Liu (PaulLiu) (2026-08-15 22:58:07)

Thanks.

Again: I am open to collaborate with you, if you are willing to try
that.  I work differently from the Rust team, and my approach might fit
your needs better (or worse - try, and we might learn from it).

 - Jonas

-> Ying-Chun Liu (PaulLiu) <paulliu@debian.org>, 2026-08-15T08:55:00Z ->

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.

Dear submitter,

as the package rust-tonic-prost has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1144488

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)