On Sun, 02 Mar 2014 14:59:49 +0000 Peter Humphrey <pe...@prh.myzen.co.uk> wrote:
> On Sunday 02 Mar 2014 12:21:24 yac wrote: > > On Sat, 01 Mar 2014 22:34:45 +0000 > > > > Peter Humphrey <pe...@prh.myzen.co.uk> wrote: > > > Hello list, > > > > > > While wrestling with my owncloud problem I decided to re-install > > > the server box from scratch. It's a little Atom box so I keep a > > > 32-bit chroot on this machine (the one I'm writing this on), > > > nfs-mount the server's packages directory in the chroot and do > > > all the heavy emerge work on the i5 here. The contents > > > of /etc/portage/* are identical in both systems, with minor > > > exceptions detailing --jobs= and the proxies (the server serves > > > the portage tree and is the rsync host, and it can't do that for > > > itself until http- replicator etc. are in place). > > > > > > I got as far as installing a recent stage 3 and adding nfs-utils > > > so that I could export the package directory. Then I ran emerge > > > -eavK world (I'd already rebuilt all the packages in the chroot > > > before zapping the server). You'll never guess what happened. > > > Well, actually, I hope someone can because I'm stumped again. > > > > > > $ OPTIONS="backtrack=100" emerge -pvKe world > > > ... > > > > Please provide the whole output. There should be an explanation why > > there is the conflict. > > OK. I've been over all my groundwork again, making sure of my facts > and running revdep-rebuild, python-updater and perl-cleaner. > > I ran three commands: > 1. emerge -epvK world > emerge.with-K > 2. emerge -epvk world > emerge.with-k > 3. emerge -epv world > emerge.no-Kk > Those three files are attached. (I pasted the STDERR text into the > first one because I couldn't remember the bashism for redirecting > both output streams to a single file.) > The slot conflict occurred in case 1. It did not occur in cases 2 and > 3, but the package list was ordered differently. -K makes portage to use *only* pre-compiled binary packages, so I guess there's the problem. As you say you are not getting conflicting on later commands, the issue is fixed for you, right? > > You can also run the emerge with -at to get some insight into the > > package dependencies. > > Hmm. A bit of a tall order with 330 packages. > > > What is the reason you run with backtrack=100 ? Actually it seems you are not setting anything as portage doesn't read the OPTIONS variable [1]_. .. [1] http://git.overlays.gentoo.org/gitweb/?p=proj%2Fportage.git&a=search&h=HEAD&st=grep&s=OPTIONS > I don't usually set it at all; I only tried it this time to confirm > my expectation that no amount of back-tracking would make any > difference. > --- Jan Matějka | Gentoo Developer https://gentoo.org | Gentoo Linux GPG: A33E F5BC A9F6 DAFD 2021 6FB6 3EBF D45B EEB6 CA8B
signature.asc
Description: PGP signature
