[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



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.

However, looking at
https://udd.debian.org/cgi-bin/autoremovals.cgi
it looks as though literally every package is up for autoremoval:

Santiago Vila <sanvila@debian.org>
   base-files: buggy deps nvidia-graphics-drivers-tesla-470, flagged for removal in 36.8 days

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.

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;
2. then, do the same for the union of main, contrib and non-free, but
   ignore attempts to autoremove additional packages from main during this
   phase

That would mean that a RC-buggy main package could trigger autoremovals
from main, contrib and/or non-free, but RC-buggy contrib/non-free packages
could only trigger autoremovals from contrib/non-free.

    smcv


Reply to: