Re: [gentoo-user] eclean-pkg strips everything out

[Dale]

Peter Humphrey wrote:
> On Wednesday 05 Apr 2017 09:36:57 Dale wrote:
>> Peter Humphrey wrote:
>>> On Tuesday 04 Apr 2017 17:52:30 Dale wrote:
>>>> Peter Humphrey wrote:
>>>>> Has anyone else noticed that running "eclean-pkg -d" removes all
>>>>> packages, or nearly so? I've had it happen recently on a few amd64
>>>>> systems and an x86 system, and it's becoming annoying. Well, no,
>>>>> actually it's long since become annoying.
>>>> If it is removing to much, leave out the -d option.  With -d, it only
>>>> leaves the minimum needed to re-emerge the packages currently
>>>> installed.  It works the same way with -dist as well.  From the man
>>>> page:
>>>>
>>>> -d, --deep                    only keep the minimum for a
>>>> reinstallation
>>>>
>>>> I think if you leave off the -d option it leaves anything that is still
>>>> in the tree, may include overlays as well.
>>> Yes, I've done that of course. The point is that it used to work with
>>> -d,
>>> and now it doesn't. If you ask how I know it used to work, my answer is
>>> that of course I don't, but at least it only removed a sensible-looking
>>> number of packages.
>>>
>>> The other day I was left with just six package files and the directory
>>> structure.
>>>
>>> I haven't noticed a problem with eclean-dist.
>> I just tested it here and it works as expected.  It left about 1500
>> files in my packages directory.  I'm using gentoolkit-0.4.0 here.  If
>> you are using something different, may want to try it.
> gentoolkit-0.3.3 here.
>
>> I use that pretty regular and its always worked as it should for me.  If
>> you are only left with 6 packages, something isn't right somewhere.
>> Have you checked to be sure it is still saving a tarball of each
>> installed package?  Maybe something was changed in make.conf and it
>> isn't building new ones for some reason, a errant edit maybe.  May want
>> to build a new package and check to confirm it saved it or not.
> This is in a 32-bit chroot for a slower machine on the local net:
>
> (webs-chroot) peak / # alias emerj
> alias emerj='emerge --jobs=24 --load-average=60 --keep-going --nospinner'
> (webs-chroot) peak / # emerj -eB world
>
> --->8
>
> (webs-chroot) peak / # find /usr/portage/packages -type f | wc
>     647     647   29800
> (webs-chroot) peak / # eclean-pkg -d
> 	[snipped hundreds of lines]
>  [  774.8 M ] Total space from 646 files were freed in the packages
> directory
> (webs-chroot) peak / # find /usr/portage/packages -type f | wc
>       1       1      31
>
> [Copy backup back in.]
>
> (webs-chroot) peak / # eclean-pkg
>  * Building file list for packages cleaning...
>  * Your packages directory was already clean.
>
>
>> If we compare what I have that works with what you have, maybe we can
>> figure out what is making this not work.  Clearly something isn't working.
> Indeed. And it isn't just on one system, as I said the first time. And it
> started happening several weeks ago.
>


I see you have buildpkg set properly which should tell it to save a
copy.  So, it should be working on that part, might still be worth
testing tho.  The only other difference I see is, we use a different
version of gentoolkit.  I tend to run the latest non-9999 version of
things related to portage and tools.  I've found them to be stable and I
get new nifty features sooner. 

If it were me, I'd try the new version of gentoolkit on one machine that
doesn't currently work.  If it works then, it is a bad version of the
package.  If it doesn't, then it is something else which could lead to a
little head scratching. 

Dale

:-)  :-)