paludis is not a replacement. i've never said that is a replacement. i only suggested it for a report of the system. it's safe to have installed 2 package managers and you could also use them both independently. when you use paludis to update the package db of your world, the first time you'll use portage it will reread the package db. the same goes for paludis: when installing something with portage you'll have to regenerate the installed cache. trying it out for the report only with --report option (it doesn't modify effectively your world packages) is safe. it only sows out incoherences in world db, and then you can use portage to remove/modify the packages that paludis signals as not ok. anyway, i thought you could give a try to its report, or to the other package manager, which i don't remember how it is called, to see if there are some broken things that portage doesn't signal. this problem comes out mainly with packages installed with old portage versions. and that is the only thing that i can say it may give you the difference. i don't really know portage very well, but a lot of breaks and broken builds have made me change package manager about one year ago. i've learned that portage has really grown up this last year and that had some changes, but i will never go back to that old fat and slow thing. only the unstable parallel compilation could at some time change my mind if it would became stable. and for the setarch package, on my amd64 system is not a system part. paludis has given me as a dependency for * net-www/nspluginwrapper-0.9.91.4::installed * app-office/openoffice-bin-2.2.1::installed * media-libs/win32codecs-20061022-r1::installed * media-video/realplayer-10.0.8::installed * net-www/netscape-flash-9.0.48.0-r1::installed * x11-themes/redhat-artwork-0.243-r1::installed * x11-themes/ximian-artwork-0.2.32.1::installed * app-arch/rpm2targz-9.0-r5::installed * app-cdr/k3b-1.0.3::installed * app-emulation/wine-0.9.43::installed * app-misc/hal-info-20070425::installed * kde-base/kdebase-meta-3.5.7::installed * kde-base/kdebase-startkde-3.5.7::installed * kde-base/kdm-3.5.7::installed * kde-base/kdesktop-3.5.7::installed * kde-base/konq-plugins-3.5.7::installed * media-sound/amarok-1.4.6-r1::installed * x11-themes/baghira-0.7::installed * kde-base/konqueror-3.5.7-r2::installed * kde-base/konsole-3.5.7::installed * kde-base/kcontrol-3.5.7-r90::installed * kde-base/khelpcenter-3.5.7::installed * kde-misc/krusader-1.70.1::installed * kde-base/kdebase-kioslaves-3.5.7-r1::installed * media-gfx/sane-backends-1.0.18-r2::installed * media-gfx/gwenview-1.4.1::installed * media-plugins/kipi-plugins-0.1.0_rc1::installed * media-libs/libgphoto2-2.2.1-r1::installed * media-video/kaffeine-0.8.3::installed * media-libs/xine-lib-1.1.4-r2::installed * media-sound/pulseaudio-0.9.5-r6::installed * net-misc/knetworkmanager-0.2_pre20070702-r1::installed * net-misc/networkmanager-0.6.5::installed * sys-apps/hal-0.5.9-r1::installed * sys-apps/util-linux-2.12r-r7::installed maybe some time ago it was included in the system db because of the dependency of util-linux. that's the only thing that makes me think that setarch was included in system. try setting removing it from system and see if the two emerge will look the same.
2007/8/13, Joshua Hoblitt <[EMAIL PROTECTED]>: > > The profiles are identical (as shown by the unified diff of `emerge > --info`). Paludis is not really a solution for me as these are > production machines. I'm really trying to understand Portage's behavior > in the scenario I outlined. > > -J > > -- > On Sun, Aug 12, 2007 at 12:30:44PM +0200, Beso wrote: > > do you have the same profile on both the systems? if one was installed > in > > 2003 and hadn't the profile updated you may have troubles getting the > same > > installeddb. > > another way of seeing the db is paludis --report. > > emerge paludis and do a paludis --report and see if that package manager > can > > see all your packages. i'm currently using that for the increased speed > in > > resolving the deps tree, for the repositories cache and for the better > use > > of overlays, or at least, the more intuitive one. of course before > working > > on the system you have to install also the paludis hooks with all the > hooks > > installed so that paludis doesn't do something weird (it never happened > to > > my system, but you can never say), and convert the system config with > the > > portage2paludis script and then you're ok. > > if you want to give a try the gentoo wiki link for making paludis work > is > > here: http://gentoo-wiki.com/Paludis > > > > 2007/8/11, Joshua Hoblitt <[EMAIL PROTECTED]>: > > > > > > The scenario: I have two amd64 systems one newish machine and one > that > > > was installed in late 2003. I really want to sink these systems to > have > > > the exact same package set. All packages are installed from bin pkgs > > > built on another system. They have identical: > > > > > > /etc/make.profile (same symlink) > > > /etc/make.conf > > > /etc/portage > > > /var/lib/portage/world > > > > > > The portage tree and overlay are both mounted from NFS as is the > package > > > dir. > > > > > > The only different in `emerge --info` is: > > > > > > -- > > > Portage 2.1.2.9 (!../usr/portage/profiles/default-linux/amd64/2007.0, > > > gcc-4.1.2, glibc-2.5-r3, 2.6.22-gentoo x86_64) > > > ================================================================= > > > -System uname: 2.6.22-gentoo x86_64 Dual Core AMD Opteron(tm) > Processor > > > 285 > > > +System uname: 2.6.22-gentoo x86_64 AMD Opteron(tm) Processor 248 > > > Gentoo Base System release 1.12.9 > > > Timestamp of tree: Mon, 09 Jul 2007 18:00:01 +0000 > > > distcc 2.18.3 x86_64-pc-linux-gnu (protocols 1 and 2) (default port > 3632) > > > [disabled] > > > -- > > > > > > These systems have both had these commands run on them: > > > > > > # dump portage cache > > > rm -rf /var/cache/edb/ > > > # prune duplicate packages, dangerous but if we really need it the > world > > > # emerge should pick it up > > > emerge -P > > > # check/fix packages deps > > > emerge -KnuD world > > > # remove packages still orphaned at this point > > > emerge --depclean > > > # look for blockers > > > emerge -KDep world > > > # fix any blockers... > > > emerge -KDe world > > > > > > Yet they both emerge a different number of packages (671 vs 668) and > > > report a > > > different number of installed packages they -e emerges! > > > > > > Calculating dependencies... done! > > > > > > Packages installed: 701 > > > Packages in world: 2 > > > Packages in system: 55 > > > Unique package names: 701 > > > Required packages: 701 > > > Number to remove: 0 > > > > > > > > > Calculating dependencies... done! > > > > > > Packages installed: 676 > > > Packages in world: 2 > > > Packages in system: 56 > > > Unique package names: 676 > > > Required packages: 676 > > > Number to remove: 0 > > > > > > > > > So clearly there are install packages that aren't part of "world" and > > > aren't found by depclean. How do I get rid of them other than by > > > comparing `equery list` with `emerge -e world` and manually removing > > > the difference? And for some reason one system does include setarch > as > > > part of "system". Seeessh. > > > > > > -J > > > > > > -- > > > > > > > > > > > > -- > > dott. ing. beso > > -- dott. ing. beso
