On Thursday, 09. Feb 2017, 08:41:00 -0500, Michael Orlitzky wrote: > On 02/09/2017 08:27 AM, Bertram Scharpf wrote: > > > > The use flag "postgresql" is _not_ set. Deinstalling pgadmin3 > > did not help. > > > > Besides that, masking 9.5 helps. Yet, it doesn't tell > > _where_ the dependency arises from. > > > > A wild guess: you keyworded a specific version of postgresql:9.6 in > package.accept_keywords. When you installed that version, portage was > happy. Later, there was a version bump of the 9.6 series in the tree. > Afterwards, your keyword no longer matches any 9.6 version in the tree, > so portage falls back to the newest stable postgres (9.5.x). > > Fix: update the entry in package.accept_keywords to match the latest 9.6 > series ebuild.
Indeed, there was a line in /ec/portage/package.keywords/custom, written on 2016-10-04 (git blame): =dev-db/postgresql-9.6.0 ~amd64 The installed version was still 9.6.0. In the meantime the ebuild belonging to 9.6.0 disappeared. I changed the = into a >=, then the "emerge -avuDNT @world" updated to 9.6.1 and forgot about 9.5.5. Thank you all! Bertram -- Bertram Scharpf Stuttgart, Deutschland/Germany http://www.bertram-scharpf.de
