1 |
On 04/27/2018 08:43 AM, Pacho Ramos wrote: |
2 |
> El vie, 27-04-2018 a las 00:48 -0700, Zac Medico escribió: |
3 |
>> On 04/26/2018 11:34 PM, Kent Fredric wrote: |
4 |
>>> On Thu, 26 Apr 2018 13:35:15 -0700 |
5 |
>>> Zac Medico <zmedico@g.o> wrote: |
6 |
>>> |
7 |
>>>> emerge --depclean, resulting in an unbootable system. Just say-in. |
8 |
>>> |
9 |
>>> And depclean being very verbose doesn't do many favours here either. |
10 |
>>> |
11 |
>>> ( I regularly do >500 package depcleans and spotting things that aren't |
12 |
>>> meant to be |
13 |
>>> culled amongst that list is a bit of a challenge )> |
14 |
>> |
15 |
>> At least for system packages, it will show a warning like the one shown |
16 |
>> here: |
17 |
>> |
18 |
>> https://bugs.gentoo.org/642484#c0 |
19 |
>> |
20 |
>> Hopefully that message helps those that are paying enough attention. |
21 |
>> What can we do for those that overlook the warning message, other than |
22 |
>> give them some rescue instructions for making their system boot again? |
23 |
> |
24 |
> Have you think in changing a bit the behavior of depclean to *not* depclean |
25 |
> system packages and ask administrator to do something like "emerge -a --depclean |
26 |
> --force" to force the depclean of that packages? |
27 |
> |
28 |
> That could help to prevent that mistakes I think |
29 |
|
30 |
I don't want this system packages warning to do anything other that |
31 |
change the display, since it's really based on heuristics. The sysvinit |
32 |
package wouldn't be removed if it was the only provider of virtual/init, |
33 |
and it only triggers the warning because it's the preferred provider. |
34 |
-- |
35 |
Thanks, |
36 |
Zac |