Re: Bug#1115714: impossible to install crate zerovec: depends on missing librust-twox-hash-2+xxhash64-dev
- To: Jonas Smedegaard <dr@jones.dk>
- Cc: Alexander Kjäll <alexander.kjall@gmail.com>, NoisyCoil <noisycoil@debian.org>, Sylvestre Ledru <sylvestre@debian.org>, debian-devel@lists.debian.org, Debian-Rust Mailing List <debian-rust@lists.debian.org>
- Subject: Re: Bug#1115714: impossible to install crate zerovec: depends on missing librust-twox-hash-2+xxhash64-dev
- From: Andreas Metzler <ametzler@bebt.de>
- Date: Sun, 21 Sep 2025 07:03:12 +0200
- Message-id: <[🔎] aM-HEBv9QrF0Tlwc@argenau.bebt.de>
- Mail-followup-to: Jonas Smedegaard <dr@jones.dk>, Alexander Kjäll <alexander.kjall@gmail.com>, NoisyCoil <noisycoil@debian.org>, Sylvestre Ledru <sylvestre@debian.org>, debian-devel@lists.debian.org, Debian-Rust Mailing List <debian-rust@lists.debian.org>
- In-reply-to: <[🔎] 175839485817.2287723.11660409360425660696@cairon.jones.dk>
- References: <[🔎] 175831898478.2287723.9054554471115825057@cairon.jones.dk> <[🔎] 285ba877-eaed-4722-9161-1dbc1dea4b0b@debian.org> <[🔎] 175835707434.2287723.6359106239947211774@cairon.jones.dk> <[🔎] 66f1221e-676f-41b2-ac34-06be1cfcb911@debian.org> <[🔎] CAOuTi9WZrOEFHMixtCZZFJBLVKDfBQN3w9fBjQu_HLyvf_X6hw@mail.gmail.com> <[🔎] 175837935280.2287723.18066496430931631498@cairon.jones.dk> <[🔎] CAOuTi9UZHjwWE7vvZ97sRoiZrVeA1xrWGv=nLt3g-6br-BegwQ@mail.gmail.com> <[🔎] 175838210881.2287723.14368404506094251792@cairon.jones.dk> <[🔎] CAOuTi9WfPm=SOE8GJ72Gb=d1C9Yxi4qkL5z_jrWaS2pvv7My_Q@mail.gmail.com> <[🔎] 175839485817.2287723.11660409360425660696@cairon.jones.dk>
On 2025-09-20 Jonas Smedegaard <dr@jones.dk> wrote:
> Quoting Alexander Kjäll (2025-09-20 19:45:07)
>>> It helps me (and Debian generally, I assume) that packages do not have
>>> missing dependencies or build-dependencies when introduced to unstable,
>>> and it is my understanding that when NEW queue is involved there is no
>>> way to know if they are missing or not because that would requre a
>>> crystal ball. Or am I missing something?
>> Could you explain how this helps? I don't really see it.
> It is helpful to me that I can generally expect Debian unstable to
> contain installable packages.
> It slows me down that for librust-*-dev packages I cannot simply check
> that some packages I need are listed in aptitude, but I need to check
> for each of them that their dependencies are ok.
> Does that make sense? I am having trouble understanding what it is that
> you cannot see, and wonder if we are talking past each other here.
And to spell it out explicitly we would prefer if you changed from
A)
Upload $package + its missing dependencies to unstable
(Causing unstable containing broken packages for $random, posibly very
very long time))
to
B)
* Upload $package + its missing dependencies to experimental
* Wait for all parts to pass through NEW
* Re-upload everything to unstable
cu Andreas
--
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
Reply to: