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