app-office/libreoffice fails on pretend phase with postgres USE flag enabled. Manually emerging postgresql-base allows libreoffice to emerge. Reproducible: Always Steps to Reproduce: 1. echo "app-office/libreoffice postgres" >> /etc/portage/package.use 2. let emerge run with emerge libreoffice 3. notice pretend failure because of no postgres slot set. 4. emerge potsgresql-base 5. emerge libreoffice, it goes fine. Actual Results: >>> Verifying ebuild manifests >>> Running pre-merge checks for app-office/libreoffice-3.6.6.2 * Checking for at least 512 mebibytes RAM ... [ ok ] * Checking for at least 6 gibibytes disk space at "/var/tmp/portage/app-office/libreoffice-3.6.6.2/temp" ... [ ok ] /var/src/portage/app-office/libreoffice/libreoffice-3.6.6.2.ebuild: line 252: postgresql-config: command not found * PostgreSQL slot must be set to 9.0 or higher. * postgresql-config set 9.0 * ERROR: app-office/libreoffice-3.6.6.2 failed (pretend phase): * PostgreSQL slot is not set to 9.0 or higher. * * Call stack: * ebuild.sh, line 93: Called pkg_pretend * libreoffice-3.6.6.2.ebuild, line 256: Called die * The specific snippet of code: * die "PostgreSQL slot is not set to 9.0 or higher
Created attachment 351404 [details] build.log
It's telling you what to do about it. The ebuild properly DEPENDs on =dev-db/postgresql-base-9.0[kerberos] but cannot help you run `eselect postgresql' more than it already does by telling you how to set it as default.
i strongly disagree with closing it as invalid, because libreoffice shouldn't die if no postgresql slot set automatically. It simply dies even not letting postgresql-base emerged before. If you run emerge postgresql-base merge manually, it sets slot automatically, hence the runtime dep in libreoffice make no sense. how to emerge libreoffice with postgres USE flag enabled if it's not letting you do so in normal way? According to comment here is the way 1 emerge postgresql-base 2 set postgres flag to libreoffice 3 emerge libbreoffice i.e runtime dep doesn't work as it should.
Fixed in cvs by checking if the package is installed before running the slot check. This effectively disables it on first-install pretend phase, but fail during pkg_setup if wrong one is installed.
3.6.6.2 stable version still affected.
See the whiteboard, when 4.0.4 goes stable, it gets propagated.
i'd expect such quirks on ~arch, but not on stable, sorry, there is no way to emerge libreoffice-3.6.6.2. Is it hard to backport 4.0.4.2 ebuild pkg_pretend to 3.6.6.2?
(In reply to Oleg from comment #7) > i'd expect such quirks on ~arch, but not on stable, sorry, there is no way > to emerge libreoffice-3.6.6.2. Is it hard to backport 4.0.4.2 ebuild > pkg_pretend to 3.6.6.2? As you are first reporting it now. I would say it is not so critical it can't wait few weeks for the 4.0.4 stablerequest.
