On Sun, 21 Sep 2025 10:41, Jonas Smedegaard <d...@jones.dk> wrote:
Package: librust-tower-lsp-dev Version: 0.20.0-1 Severity: grave X-Debbugs-Cc: debian-devel@lists.debian.org, debian-r...@lists.debian.org-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Package librust-tower-lsp-dev is impossible to install: depends on missing package librust-async-codec-lite-0.0+default-dev. The cause seems to be the common situation in the Rust team of initially uploading to NEW, despite knowledge that some declared dependencies are not yet available in that Debian suite. Please do not knowingly destabilize Debian unstable, but release known broken packages to experimental, re-releasing to unstable only when dependencies are all there.
Hi,in my packaging work, I rarely, if all upload packages to NEW that have unsatisfied dependencies or are not installable. Otherwise I upload to experimental. Likewise, no one on the Debian rust is *deliberately* destabilizing Debian unstable. If packages become uninstallable this is because of human error. We are all volunteers here (at least I am). Single team members might have involuntarily b0rked packages before (I certainly have at one point), but this has been usually remedied quick.
If we want to have it enshrined in policy that we should *only* upload NEW packages to experimental, I suggest moving this to -project.
This is not fair, and you know it. Many teams use an alioth mail as Maintainer: and their -lists mail for discussions. It's not uncommon that contributors in teams are not subscribed to the former.debian-devel@l.d.o is Cc'ed, and debian-rust@l.d.o as well since apparently the Rust team treats their Maintainer field email address as something else than for human conversations.
best, werdahias PS: not subscribed to -devel, please CC for relevant replies
signature.asc
Description: Digital signature
