| 1 |
On Sunday, November 20, 2016 05:07:03 PM Константин wrote: |
| 2 |
> On Sun, Nov 20, 2016 at 01:35:46PM +0000, Peter Humphrey wrote: |
| 3 |
> > On Sunday 20 Nov 2016 16:05:29 Константин wrote: |
| 4 |
> > > On Sun, Nov 20, 2016 at 09:42:40AM -0300, Zhu Sha Zang wrote: |
| 5 |
> > > > Maybe you need to use 'eclean-dist -d'. But, for your safe, use |
| 6 |
> > > > 'eclean-dist -dp' first. |
| 7 |
> > > |
| 8 |
> > > BTW what troubles can I get from 'eclean-dist -d' ? As far as I |
| 9 |
> > > understand it, re-download needed tar.gz will be the worst isn't it? |
| 10 |
> > |
| 11 |
> > You'd think so, wouldn't you? But recently something has been going wrong |
| 12 |
> > here such that 'eclean-pkg -d' removed every single package, leaving just |
| 13 |
> > the directory structure. That was just after I'd spent six hours building |
| 14 |
> > them |
| 15 |
> Don't take me wrong it was not an objection but just a question. There |
| 16 |
> are a lot of warnigns, but no explanations except 'users will not be |
| 17 |
> protected in case they need to downgrade a package or re-install a |
| 18 |
> previously removed package.' or similar. |
| 19 |
> |
| 20 |
> And thanks for example. |
| 21 |
|
| 22 |
One example where this can be annoying is with packages that have fetch- |
| 23 |
restriction enabled. Or, even worse, where certain versions are no longer |
| 24 |
available for download. |
| 25 |
|
| 26 |
-- |
| 27 |
Joost |
Archives