On 05/06/2022 20.25, Paul Gevers wrote:
> However, this looks like the path where the issue lies.
> bin:nvidia-kernel-dkms (non-free, built from src:nvidia-graphics-drivers
> in non-free) Depends (on amd64 only) on nvidia-firmware-470.103.01 which
> is Provided by bin:nvidia-kernel-support (built
Hi,
On 25-05-2022 22:09, Paul Gevers wrote:
While not having figured out where the bug exactly lies (I mean, which
lines of code), I think it's important to note that the
src:nvidia-settings (in main) is building a bin:nvidia-settings in
contrib. This is allowed by policy, but I think this is
On Wed, May 25, 2022 at 10:09:56PM +0200, Paul Gevers wrote:
>...
> Chance has it that some Release
> Team members have been discussing internally about viewing the key package
> set differently already, because there are more potential boundaries to draw
> in the current set. (As an example of
Control: user qa.debian.org
Control: usertag -1 udd.debian.org
Hi Simon,
On 19-05-2022 13:58, Paul Gevers wrote:
dkms and nvidia-graphics-drivers-tesla-470 currently have RC bug #1010884
triggering autoremovals (it was closed today, so maybe it will cease
to be
relevant soon).
Turns out
Control: reassign -1 qa.debian.org
On 19-05-2022 12:37, Simon McVittie wrote:
Package: release.debian.org
dkms and nvidia-graphics-drivers-tesla-470 currently have RC bug #1010884
triggering autoremovals (it was closed today, so maybe it will cease to be
relevant soon).
I would expect the
Package: release.debian.org
dkms and nvidia-graphics-drivers-tesla-470 currently have RC bug #1010884
triggering autoremovals (it was closed today, so maybe it will cease to be
relevant soon).
I would expect the only packages affected by this to be packages that
specifically depend on dkms or on
6 matches
Mail list logo
