[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1011268: release.debian.org: proposes autoremoving every package(?) when nvidia-graphics-drivers-tesla-470 is RC-buggy



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 only packages affected by this to be packages that
specifically depend on dkms or on the NVIDIA proprietary driver.

It's a great surprise to me that this happened. I *suspect* it's due to that the fact that the bug you mentioned is assigned to both a key package and a non-key package. As one can imagine, autoremovals are based on bugs in testing. The bug in testing affects a non-key package, but I wouldn't be surprised if that once it takes the bug number in (for a non-key package) it isn't aware of the bts feature that a bug can be assigned to more packages and doesn't handle this case.

This seems very wrong. I'm fairly sure base-files doesn't depend on
graphics drivers, and in any case the NVIDIA proprietary driver is in
non-free, so by policy no package in main can possibly depend on it.

With the understanding above, I suspect it's just because of the removal of dkms, which is part of the key package set for $(reasons).

It might be better if autoremovals were evaluated something like this:

1. work out what autoremovals would take place if main was the only
    archive area that existed;

Autoremoval is supposed to only remove non-key packages and completely ignore key packages. That's obviously not what happened, so a clear bug.

Technically the autoremoval is calculated by udd, hence reassigning there.

Paul

Attachment: OpenPGP_signature
Description: OpenPGP digital signature


Reply to: