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. You can also run the emerge with -at to get some insight into the package dependencies. What is the reason you run with backtrack=100 ? > !!! All ebuilds that could satisfy "app-arch/bzip2" have been masked. > !!! One of the following masked packages is required to complete your > request: > - app-arch/bzip2-1.0.6-r3::gentoo (masked by: backtracking: slot > conflict) > > Bzip2 installs happily if specified by itself. Portage is at version > 2.2.7, and I did remember to set the active python version to 2.7 > before starting all this. > > Now that I think of it, this slot conflict over bzip2 was among the > reasons I decided to zap the server and start anew. The cure hasn't > fixed the ailment. > > Has anyone any ideas? > --- 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
