public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
* [gentoo-amd64] revdep-rebuild vs depclean today...
@ 2009-09-10 22:40 Mark Knecht
  2009-09-11  1:35 ` Paul Hartman
  0 siblings, 1 reply; 3+ messages in thread
From: Mark Knecht @ 2009-09-10 22:40 UTC (permalink / raw
  To: gentoo-amd64

Hi,
   I what way can I improve my use of the tools? I don't remember
seeing a case before where revdep-rebuild -ip was clean but emerge
--depclean didn't want to remove files. I.e. - the
sys-libs/db-4.5.20_p2-r1 message.

Thanks,
Mark

lightning ~ # revdep-rebuild -ip
 * Configuring search environment for revdep-rebuild

 * Checking reverse dependencies
 * Packages containing binaries and libraries broken by a package update
 * will be emerged.

 * Collecting system binaries and libraries
 * Generated new 1_files.rr
 * Collecting complete LD_LIBRARY_PATH
 * Generated new 2_ldpath.rr
 * Checking dynamic linking consistency
[ 100% ]

 * Dynamic linking on your system is consistent... All done.
lightning ~ # emerge -p --depclean

 * 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.
 *
 * As a safety measure, depclean will not remove any packages
 * unless *all* required dependencies have been resolved.  As a
 * consequence, it is often necessary to run `emerge --update
 * --newuse --deep @system @world` prior to depclean.

Calculating dependencies... done!
>>> Checking for lib consumers...
>>> Assigning files to packages...
 * In order to avoid breakage of link level dependencies, one or more
 * packages will not be removed. This can be solved by rebuilding the
 * packages that pulled them in.
 *
 *   sys-libs/db-4.5.20_p2-r1 pulled in by:
 *     dev-lang/perl-5.8.8-r5
 *     perl-core/DB_File-1.815
 *
>>> Adding lib providers to graph...
 \
Calculating dependencies... done!
>>> No packages selected for removal by depclean
>>> To see reverse dependencies, use --verbose
Packages installed:   801
Packages in world:    95
Packages in system:   51
Required packages:    801
Number to remove:     0
lightning ~ # emerge -pvDuN @world

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

Calculating dependencies... done!

Total: 0 packages, Size of downloads: 0 kB
lightning ~ #



^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [gentoo-amd64] revdep-rebuild vs depclean today...
  2009-09-10 22:40 [gentoo-amd64] revdep-rebuild vs depclean today Mark Knecht
@ 2009-09-11  1:35 ` Paul Hartman
  0 siblings, 0 replies; 3+ messages in thread
From: Paul Hartman @ 2009-09-11  1:35 UTC (permalink / raw
  To: gentoo-amd64

On Thu, Sep 10, 2009 at 5:40 PM, Mark Knecht <markknecht@gmail.com> wrote:
> Hi,
>   I what way can I improve my use of the tools? I don't remember
> seeing a case before where revdep-rebuild -ip was clean but emerge
> --depclean didn't want to remove files. I.e. - the
> sys-libs/db-4.5.20_p2-r1 message.

I think revdep-rebuild is mostly unneeded these days with recent
portage versions thanks to the @preserved-rebuild system, at least in
my case it does the trick. Based on the above, I bet if you unmerge
the version of db that you don't want, emerge would then put the
appropriate packages in your @preserved-rebuild set and they'd be
rebuilt against the other version of db left over. Kind of like
revdep-rebuild but more intelligent, and no need to scan a million
files on your system every time. :)

I think you should run your commands in this order (slightly modified
from your above examples to ask instead of preview, so you don't need
to run them each twice):

#eix-sync (or emerge --sync/layman -S or however you sync your portage
& overlays)
#emerge -avDuN @world (and @system if it's not in your @world set)
#emerge -avDuN @preserved-build (if necessary)
#emerge --depclean -a
#revdep-rebuild -i -- -a (should only be run when the above commands
have nothing left to do)

That's all just my opinion of course :)

in my case I also use --keep-going so emerge/revdep-rebuild will build
as many things as possible even if one package fails.



^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [gentoo-amd64] revdep-rebuild vs depclean today...
@ 2009-09-11  2:57 Dmitri Pogosyan
  0 siblings, 0 replies; 3+ messages in thread
From: Dmitri Pogosyan @ 2009-09-11  2:57 UTC (permalink / raw
  To: gentoo-amd64

What's wrong with that ? You have two (or even more) db packages installed in
different slots, and due to historical reasons some packages were built agains
one version and some - against another. Remove the old version manually and
run revdep-rebuild


> Hi,
>    I what way can I improve my use of the tools? I don't remember
> seeing a case before where revdep-rebuild -ip was clean but emerge
> --depclean didn't want to remove files. I.e. - the
> sys-libs/db-4.5.20_p2-r1 message.
> 
> Thanks,
> Mark
> 
> lightning ~ # revdep-rebuild -ip
>  * Configuring search environment for revdep-rebuild
> 
>  * Checking reverse dependencies
>  * Packages containing binaries and libraries broken by a package update
>  * will be emerged.
> 
>  * Collecting system binaries and libraries
>  * Generated new 1_files.rr
>  * Collecting complete LD_LIBRARY_PATH
>  * Generated new 2_ldpath.rr
>  * Checking dynamic linking consistency
> [ 100% ]
> 
>  * Dynamic linking on your system is consistent... All done.
> lightning ~ # emerge -p --depclean
> 
>  * 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.
>  *
>  * As a safety measure, depclean will not remove any packages
>  * unless *all* required dependencies have been resolved.  As a
>  * consequence, it is often necessary to run `emerge --update
>  * --newuse --deep @system @world` prior to depclean.
> 
> Calculating dependencies... done!
> >>> Checking for lib consumers...
> >>> Assigning files to packages...
>  * In order to avoid breakage of link level dependencies, one or more
>  * packages will not be removed. This can be solved by rebuilding the
>  * packages that pulled them in.
>  *
>  *   sys-libs/db-4.5.20_p2-r1 pulled in by:
>  *     dev-lang/perl-5.8.8-r5
>  *     perl-core/DB_File-1.815
>  *
> >>> Adding lib providers to graph...
>  \
> Calculating dependencies... done!
> >>> No packages selected for removal by depclean
> >>> To see reverse dependencies, use --verbose
> Packages installed:   801
> Packages in world:    95
> Packages in system:   51
> Required packages:    801
> Number to remove:     0
> lightning ~ # emerge -pvDuN @world
> 
> These are the packages that would be merged, in order:
> 
> Calculating dependencies... done!
> 
> Total: 0 packages, Size of downloads: 0 kB
> lightning ~ #



--
Dmitri Pogosyan            Department of Physics
Professor                  University of Alberta
tel 1-780-492-2150         11322 - 89 Avenue
fax 1-780-492-0714         Edmonton, AB, T6G 2G7, CANADA





^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2009-09-11  2:57 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-09-10 22:40 [gentoo-amd64] revdep-rebuild vs depclean today Mark Knecht
2009-09-11  1:35 ` Paul Hartman
  -- strict thread matches above, loose matches on Subject: below --
2009-09-11  2:57 Dmitri Pogosyan

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox