On Tue, Jan 13, 2009 at 10:20 AM, Paul Hartman <paul.hartman+gen...@gmail.com> wrote: > On Tue, Jan 13, 2009 at 9:52 AM, Alan McKinnon <alan.mckin...@gmail.com> > wrote: >> On Tuesday 13 January 2009 17:44:37 Paul Hartman wrote: >>> Hi, >>> >>> I normally do "emerge -uDvN @world" (or in other words "emerge >>> --update --deep --verbose --newuse @world"). Right now, it tells me >>> this: >>> >>> Total: 0 packages, Size of downloads: 0 kB >>> >>> I also --depclean on a regular basis to remove any unneeded packages. >>> Right now, it tells me this: >>> >>> No packages selected for removal by depclean >>> >>> Based on those two commands, I'm led to believe I have a fully updated >>> system. So, then, I am curious why when I do "emerge -e @world" it >>> tells me this: >>> >>> Total: 1432 packages (9 upgrades, 2 downgrades, 14 new, 1407 >>> reinstalls, 1 interactive), Size of downloads: 76,235 kB >>> >>> How is that possible? Where do those upgrades, downgrades and new >>> packages come from? What is missing from my traditional "-uDvN" >>> command that is causing me to miss some of those updates? >> >> read the man page. >> >> Especially the bit about bdeps - these are usually not included >> in 'emerge -uND world' but will be included when you use -e > > Well, I've read about that before and am using the default bdep > behavior but I guess I don't understand it entirely. > > I've isolated basically all of the new/changed packages down to > openoffice-3.0.0 -- if I do "emerge -vtp openoffice" it shows me this: > > [ebuild R ] app-office/openoffice-3.0.0 USE="binfilter cups dbus > gtk java kde ldap mono nsplugin opengl pam -debug -eds -gnome > -gstreamer -odk -templates" LINGUAS="en en_US -af -ar -as_IN -be_BY > -bg -bn -br -bs -ca -cs -cy -da -de -dz -el -en_GB -en_ZA -eo -es -et > -fa -fi -fr -ga -gl -gu_IN -he -hi_IN -hr -hu -it -ja -km -ko -ku -lt > -lv -mk -ml_IN -mr_IN -nb -ne -nl -nn -nr -ns -or_IN -pa_IN -pl -pt > -pt_BR -ru -rw -sh -sk -sl -sr -ss -st -sv -sw_TZ -ta_IN -te_IN -tg > -th -ti_ER -tn -tr -ts -uk -ur_IN -ve -vi -xh -zh_CN -zh_TW -zu" > 10,552 kB > > So, apparently openoffice has ~10 megabytes of unfetched files even > though I have not deleted any openoffice distfiles since I emerged it > in November. That would make me think maybe the ebuild has changed > without a version number change. Checking the date on the ebuild it is > January 11 2009. However, the date on > /var/db/pkg/app-office/openoffice-3.0.0/openoffice-3.0.0.ebuild is > November 3 2008. A diff of the files shows some material changes > (downloading newer builds from go-oo.org etc). So in this particular > case I think my suspicion about the ebuild changing without a version > number revision might be right. > > When I do "emerge -Dtp openoffice" it shows this: > > Calculating dependencies ... done! > [ebuild R ] app-office/openoffice-3.0.0 > [nomerge ] dev-perl/Archive-Zip-1.26 > [ebuild UD] virtual/perl-File-Spec-3.29 [3.2701] > [ebuild UD] perl-core/File-Spec-3.29 [3.2701] > [nomerge ] dev-perl/Archive-Zip-1.26 > [nomerge ] perl-core/File-Spec-3.29 [3.2701] > [nomerge ] perl-core/Module-Build-0.31 > [ebuild N ] virtual/perl-ExtUtils-ParseXS-2.19 > [ebuild N ] perl-core/ExtUtils-ParseXS-2.19 > [ebuild N ] virtual/perl-Module-Build-0.31 > [ebuild N ] perl-core/Module-Build-0.31 > [ebuild N ] virtual/perl-Archive-Tar-1.42 > [ebuild N ] perl-core/Archive-Tar-1.42 USE="bzip2" > [ebuild N ] dev-perl/IO-Compress-Bzip2-2.015 > [ebuild N ] dev-perl/Compress-Raw-Bzip2-2.015 USE="-test" > [ebuild N ] perl-core/Package-Constants-0.02 > [ebuild N ] dev-perl/IO-String-1.08 > [ebuild N ] virtual/perl-IO-Zlib-1.09 > [ebuild N ] dev-perl/yaml-0.68 > [nomerge ] virtual/perl-IO-Zlib-1.09 > [ebuild N ] perl-core/IO-Zlib-1.09 > [nomerge ] perl-core/File-Spec-3.29 [3.2701] > [ebuild N ] virtual/perl-ExtUtils-CBuilder-0.24 > > I'm still not entirely clear on why those appear with --deep > openoffice but not --deep world. If they are build-time deps, wouldn't > they be included when I emerge openofifce without --deep? If they are > related to dev-perl/Archive-Zip-1.26 (as it appears), which is > installed, why don't they get touched by @world? Maybe I just can't > wrap my brain around how it works, please have patience with me. > thanks :) > > Paul >
I've found that emerge -vtp @downgrade presents me with almost the same list (sans openoffice): [ebuild UD] virtual/perl-File-Spec-3.29 [3.2701] 0 kB [ebuild UD] perl-core/File-Spec-3.29 [3.2701] 128 kB [nomerge ] perl-core/File-Spec-3.29 [3.2701] [nomerge ] perl-core/Module-Build-0.31 [ebuild N ] virtual/perl-ExtUtils-ParseXS-2.19 0 kB [ebuild N ] perl-core/ExtUtils-ParseXS-2.19 0 kB [ebuild N ] virtual/perl-Module-Build-0.31 0 kB [ebuild N ] perl-core/Module-Build-0.31 204 kB [ebuild N ] virtual/perl-Archive-Tar-1.42 0 kB [ebuild N ] perl-core/Archive-Tar-1.42 USE="bzip2" 48 kB [ebuild N ] dev-perl/IO-Compress-Bzip2-2.015 74 kB [ebuild N ] dev-perl/Compress-Raw-Bzip2-2.015 USE="-test" 138 kB [ebuild N ] perl-core/Package-Constants-0.02 3 kB [ebuild N ] dev-perl/IO-String-1.08 0 kB [ebuild N ] virtual/perl-IO-Zlib-1.09 0 kB [ebuild N ] dev-perl/yaml-0.68 91 kB [nomerge ] virtual/perl-IO-Zlib-1.09 [ebuild N ] perl-core/IO-Zlib-1.09 0 kB [nomerge ] perl-core/File-Spec-3.29 [3.2701] [ebuild N ] virtual/perl-ExtUtils-CBuilder-0.24 0 kB I think File-Spec-3.29 is really an upgrade from 3.2701 (which is really 3.27.01) but portage sees 29 < 2701 so that's why it never got included in my updates. Things are becoming clearer :) Thanks, Paul
