[gentoo-user] Difference between --update and --emptytree?

[gentoo-user] Difference between --update and --emptytree?

[Walter Dnes]

  Did an update today.  After the update, I checked again...

[d531][waltdnes][~] emerge -pv --update --changed-use world

These are the packages that would be merged, in order:

Calculating dependencies... done!

Total: 0 packages, Size of downloads: 0 kB

  Good... nothing to add... I think.  But replace "--update" with
"--emptytree", and a whole bunch of new and updated stuff shows up.  Is
there a logical explanation?  Should I emerge world?  Or just the new
and updated stuff (with the -1 flag)?  Here are listings of the new and
updated stuff...

[d531][waltdnes][~] emerge -pv --changed-use --emptytree world | grep ' N '
[ebuild  N     ] virtual/perl-Locale-Maketext-Simple-0.210.0-r2  0 kB
[ebuild  N     ] virtual/perl-Package-Constants-0.20.0-r2  0 kB
[ebuild  N     ] virtual/perl-IO-Zlib-1.100.0-r2  0 kB
[ebuild  N     ] perl-core/Compress-Raw-Bzip2-2.60.0  133 kB
[ebuild  N     ] perl-core/Compress-Raw-Zlib-2.60.0  231 kB
[ebuild  N     ] perl-core/Params-Check-0.360.0  12 kB
[ebuild  N     ] perl-core/Module-CoreList-2.800.0  57 kB
[ebuild  N     ] perl-core/Module-Load-0.240.0  6 kB
[ebuild  N     ] virtual/perl-Params-Check-0.360.0  0 kB
[ebuild  N     ] virtual/perl-Compress-Raw-Bzip2-2.60.0  0 kB
[ebuild  N     ] virtual/perl-Compress-Raw-Zlib-2.60.0  0 kB
[ebuild  N     ] virtual/perl-Module-CoreList-2.800.0  0 kB
[ebuild  N     ] virtual/perl-Module-Load-0.240.0  0 kB
[ebuild  N     ] perl-core/IO-Compress-2.60.0  238 kB
[ebuild  N     ] virtual/perl-IO-Compress-2.60.0  0 kB
[ebuild  N     ] perl-core/Archive-Tar-1.900.0  57 kB
[ebuild  N     ] perl-core/Module-Load-Conditional-0.540.0  13 kB
[ebuild  N     ] virtual/perl-Module-Load-Conditional-0.540.0  0 kB
[ebuild  N     ] perl-core/IPC-Cmd-0.780.0  27 kB
[ebuild  N     ] virtual/perl-IPC-Cmd-0.780.0  0 kB
[ebuild  N     ] perl-core/CPAN-Meta-Requirements-2.122.0  21 kB
[ebuild  N     ] virtual/perl-CPAN-Meta-Requirements-2.122.0  0 kB
[ebuild  N     ] dev-lang/vala-0.18.1:0.18  USE="{-test} -vapigen" 0 kB

[d531][waltdnes][~] emerge -pv --changed-use --emptytree world | grep ' U '
[ebuild     U  ] app-arch/rpm2targz-9.0.0.5g [9.0.0.4g] 6 kB
[ebuild     U  ] gnome-base/gnome-common-3.6.0:3 [3.1.0:3] 141 kB
[ebuild     U  ] dev-lang/nasm-2.10.07 [2.10.05] USE="-doc" 665 kB
[ebuild     U  ] perl-core/version-0.990.100 [0.940.0] 105 kB
[ebuild     U  ] perl-core/Test-Harness-3.260.0 [3.230.0] 288 kB
[ebuild     U  ] perl-core/Scalar-List-Utils-1.270.0 [1.230.0] 68 kB
[ebuild     U  ] perl-core/CPAN-Meta-YAML-0.8.0 [0.4.0] 31 kB
[ebuild     U  ] perl-core/ExtUtils-Manifest-1.610.0 [1.580.0] 29 kB
[ebuild     U  ] perl-core/ExtUtils-Install-1.540.0 [1.54] 0 kB
[ebuild     U  ] virtual/perl-version-0.990.100 [0.940.0] 0 kB
[ebuild     U  ] virtual/perl-Scalar-List-Utils-1.270.0 [1.230.0-r2] 0 kB
[ebuild     U  ] virtual/perl-CPAN-Meta-YAML-0.8.0 [0.4.0] 0 kB
[ebuild     U  ] virtual/perl-Test-Harness-3.260.0 [3.230.0-r3] 0 kB
[ebuild     U  ] virtual/perl-ExtUtils-Manifest-1.610.0 [1.580.0-r1] 0 kB
[ebuild     U  ] virtual/perl-ExtUtils-Install-1.540.0 [1.54] 0 kB
[ebuild     U  ] perl-core/Module-Metadata-1.0.11 [1.0.6] 27 kB
[ebuild     U  ] perl-core/Parse-CPAN-Meta-1.440.400 [1.440.100] 8 kB
[ebuild     U  ] virtual/perl-Parse-CPAN-Meta-1.440.400 [1.440.100-r2] 0 kB
[ebuild     U  ] virtual/perl-Module-Metadata-1.0.11 [1.0.6] 0 kB
[ebuild     U  ] virtual/perl-Archive-Tar-1.900.0 [1.54] 0 kB
[ebuild     U  ] perl-core/ExtUtils-CBuilder-0.280.205 [0.27.03] 34 kB
[ebuild     U  ] virtual/perl-ExtUtils-CBuilder-0.280.205 [0.27.03] 0 kB
[ebuild     U  ] perl-core/ExtUtils-MakeMaker-6.640.0 [6.620.0] 412 kB
[ebuild     U  ] virtual/perl-ExtUtils-MakeMaker-6.640.0 [6.620.0] 0 kB
[ebuild     U  ] perl-core/CPAN-Meta-2.120.921 [2.112.621] 75 kB
[ebuild     U  ] virtual/perl-CPAN-Meta-2.120.921 [2.112.621] 0 kB
[ebuild     U  ] perl-core/Module-Build-0.400.300 [0.380.0] USE="{-test%}" 301 kB
[ebuild     U  ] virtual/perl-Module-Build-0.400.300 [0.380.0-r2] 0 kB
[ebuild     U  ] app-arch/libarchive-3.0.4-r1 [3.0.3] USE="bzip2 zlib -acl -e2fsprogs -expat -iconv -lzma -nettle -static-libs -xattr" 3,548 kB


-- 
Walter Dnes <waltdnes@waltdnes.org>
I don't run "desktop environments"; I run useful applications

Re: [gentoo-user] Difference between --update and --emptytree?

[Mike Gilbert]

On Sat, Mar 30, 2013 at 9:49 PM, Walter Dnes <waltdnes@waltdnes.org> wrote:
>   Did an update today.  After the update, I checked again...
>
> [d531][waltdnes][~] emerge -pv --update --changed-use world
>
> These are the packages that would be merged, in order:
>
> Calculating dependencies... done!
>
> Total: 0 packages, Size of downloads: 0 kB
>
>   Good... nothing to add... I think.  But replace "--update" with
> "--emptytree", and a whole bunch of new and updated stuff shows up.  Is
> there a logical explanation?  Should I emerge world?  Or just the new
> and updated stuff (with the -1 flag)?  Here are listings of the new and
> updated stuff...

The extra stuff is probably build-time deps, which do not get updated
by default. Try this:

emerge -pv --update --changed-use --with-bdeps=y world

Re: [gentoo-user] Difference between --update and --emptytree?

[Walter Dnes]

On Sat, Mar 30, 2013 at 10:04:24PM -0400, Mike Gilbert wrote
> On Sat, Mar 30, 2013 at 9:49 PM, Walter Dnes <waltdnes@waltdnes.org> wrote:
> >   Did an update today.  After the update, I checked again...
> >
> > [d531][waltdnes][~] emerge -pv --update --changed-use world
> >
> > These are the packages that would be merged, in order:
> >
> > Calculating dependencies... done!
> >
> > Total: 0 packages, Size of downloads: 0 kB
> >
> >   Good... nothing to add... I think.  But replace "--update" with
> > "--emptytree", and a whole bunch of new and updated stuff shows up.  Is
> > there a logical explanation?  Should I emerge world?  Or just the new
> > and updated stuff (with the -1 flag)?  Here are listings of the new and
> > updated stuff...
> 
> The extra stuff is probably build-time deps, which do not get updated
> by default. Try this:
> 
> emerge -pv --update --changed-use --with-bdeps=y world

  I see nothing at all to be emerged...

====================================================================
[d531][waltdnes][~] emerge -pv --update --changed-use --with-bdeps=y world

These are the packages that would be merged, in order:

Calculating dependencies... done!

Total: 0 packages, Size of downloads: 0 kB
====================================================================

  I've written an "autodepclean" script that I run to guide me through
cleaning up orphaned dependancies.  Think of it as a "sane depclean".
After each use, I run revdep-rebuild to ensure that nothing is broken.
Could this be at the root of my situation?

-- 
Walter Dnes <waltdnes@waltdnes.org>
I don't run "desktop environments"; I run useful applications

Re: [gentoo-user] Difference between --update and --emptytree?

[Michael Hampicke]

Am 31.03.2013 05:12, schrieb Walter Dnes:
> On Sat, Mar 30, 2013 at 10:04:24PM -0400, Mike Gilbert wrote
>> On Sat, Mar 30, 2013 at 9:49 PM, Walter Dnes <waltdnes@waltdnes.org> wrote:
>>>   Did an update today.  After the update, I checked again...
>>>
>>> [d531][waltdnes][~] emerge -pv --update --changed-use world
>>>
>>> These are the packages that would be merged, in order:
>>>
>>> Calculating dependencies... done!
>>>
>>> Total: 0 packages, Size of downloads: 0 kB
>>>
>>>   Good... nothing to add... I think.  But replace "--update" with
>>> "--emptytree", and a whole bunch of new and updated stuff shows up.  Is
>>> there a logical explanation?  Should I emerge world?  Or just the new
>>> and updated stuff (with the -1 flag)?  Here are listings of the new and
>>> updated stuff...
>>
>> The extra stuff is probably build-time deps, which do not get updated
>> by default. Try this:
>>
>> emerge -pv --update --changed-use --with-bdeps=y world
> 
>   I see nothing at all to be emerged...
> 
> ====================================================================
> [d531][waltdnes][~] emerge -pv --update --changed-use --with-bdeps=y world
> 
> These are the packages that would be merged, in order:
> 
> Calculating dependencies... done!
> 
> Total: 0 packages, Size of downloads: 0 kB
> ====================================================================

You can also try adding --deep to your emerge options.

Or double check with eix -u -c

> 
>   I've written an "autodepclean" script that I run to guide me through
> cleaning up orphaned dependancies.  Think of it as a "sane depclean".
> After each use, I run revdep-rebuild to ensure that nothing is broken.
> Could this be at the root of my situation?
> 

What do you mean by sane depclean? Are there any problems with
--depclean that I am not aware of?

Re: [gentoo-user] Difference between --update and --emptytree?

[Walter Dnes]

On Sun, Mar 31, 2013 at 01:56:25PM +0200, Michael Hampicke wrote

> You can also try adding --deep to your emerge options.

  That seems to be it...

emerge -pv --update --changed-use --deep --with-bdeps=y world

produces a list of packages.  The list ends with...

> Total: 52 packages (29 upgrades, 23 new), Size of downloads: 6,521 kB
> Conflict: 1 block

  The 29 upgrades and 23 new seem to exactly match what I had from the
new and upgrade portions of emerge world.  Thanks for your help.

> What do you mean by sane depclean? Are there any problems with
> --depclean that I am not aware of?

  emerge -p --depclean

generates dire warnings.  I keep a previous version of the kernel
(gentoo-sources) as a fallback, and --depclean wants to remove that,
which I want to keep.

-- 
Walter Dnes <waltdnes@waltdnes.org>
I don't run "desktop environments"; I run useful applications

Re: [gentoo-user] Difference between --update and --emptytree?

[Peter Humphrey]

[-- Attachment #1: Type: text/plain, Size: 393 bytes --]

On Sunday 31 March 2013 14:09:56 Walter Dnes wrote:

> I keep a previous version of the kernel (gentoo-sources) as a fallback,
> and --depclean wants to remove that, which I want to keep.

if you let it unmerge the old kernel it will only remove the sources. 
Everything that's generated by building the kernel will be left alone. Would 
that suit you? It's what I do here, anyway:

-- 
Peter

[-- Attachment #2: Type: text/html, Size: 2187 bytes --]

Re: [gentoo-user] Difference between --update and --emptytree?

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 832 bytes --]

On Sun, 31 Mar 2013 09:09:56 -0400, Walter Dnes wrote:

>   emerge -p --depclean
> 
> generates dire warnings.

I wouldn't call this dire

 * Always study the list of packages to be cleaned for any obvious
 * mistakes. Packages that are part of the world set will always
 * be kept.  They can be manually added to this set with
 * `emerge --noreplace <atom>`.  Packages that are listed in
 * package.provided (see portage(5)) will be removed by
 * depclean, even if they are part of the world set.

There used to be big scary warnings in the past, but that was years ago
and depclean seems very reliable now. I'd certainly trust a feature
maintained by the portage devs more than a home-brewed script


-- 
Neil Bothwick

There's a fine line between fishing and standing on the shore looking
like an idiot.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Difference between --update and --emptytree?

[Paul Hartman]

On Sun, Mar 31, 2013 at 8:09 AM, Walter Dnes <waltdnes@waltdnes.org> wrote:
>> What do you mean by sane depclean? Are there any problems with
>> --depclean that I am not aware of?
>
>   emerge -p --depclean
>
> generates dire warnings.  I keep a previous version of the kernel
> (gentoo-sources) as a fallback, and --depclean wants to remove that,
> which I want to keep.

Quoted below is a solution that was posted to this list a few years
ago, I use it for exactly that situation: to prevent kernels from ever
getting depcleaned.

On Thu, Jun 11, 2009 at 11:45 AM, Mike Kazantsev <mk.fraggod@gmail.com> wrote:
>> So, my question: Is there a way to tell depclean to never remove *any*
>> version of gentoo-sources?
>
> That's where portage-2.2 sets find another use.
> Just add following set to /usr/share/portage/config/sets.conf:
>
>   [kernels]
>   class = portage.sets.dbapi.OwnerSet
>   world-candidate = False
>   files = /usr/src
>
> And append "@kernels" line to /var/lib/portage/world_sets
> Now any installed (even with -1) kernel should be safe from ravenous
> depclean.

Hope that helps!