On Fri, 20 Jun 2014 13:33:26 +0200, Alan McKinnon wrote: > These dependency chains can get long and complex, so best is usually to > look at the whole thing and see exactly what is going on. Most often you > have something in world that is keyworded, or the current version is > still ~arch
Another problem with this method of switching to stable gradually is that it sometimes want to downgrade a package.Say foo-1.0 is stable and foo-1.1 is testing and you have ~foo-1.1 in package.accept_keywords. Then foo-1.1.1 is added to ~arch and the 1.1 ebuild is removed, having never been stabilised. Portage will then try to downgrade to 1.0, possibly messing with your dependencies. The moral is always look for portage trying to downgrade packages and add the appropriate keyword entries when using this approach. -- Neil Bothwick Earlier, I didn't have time to finish anything. This time I w
signature.asc
Description: PGP signature
