We are switching to a slotted eselect based postgresql ebuild system. This has ebuilds of the form virtual/postgresql-base dev-db/postgresql-base deb-db/postgresql-server. These ebuild are presently ~ masked. This obsoletes and blocks the libpq and postgresql ebuilds. with portage, the bacula ebuild wants to pull in the old postgresql ebuilds with paludis, the bacula ebuild wants to pull in a slotted postgresql 8.0 ebuild even though postgresql-server 8.3 is available and eselect postgresql 'set-all' and 'update' has been run. Reproducible: Always
21 May 2008; Tiziano Müller <dev-zero@gentoo.org> bacula-2.0.3.ebuild, bacula-2.2.8.ebuild, bacula-2.2.8-r1.ebuild: Changed dependency for postgresql from dev-db/postgresql to virtual/postgresql-server We would appreciate it if you included the output of `emerge --info'.
Thanks for that. emerge --info yes. I'll try and remember that. There must be some way of getting that information out of paludis. Thanks again, this virtual/postgresql is long overdue --john
Yes thats fixed it. Thanks