Ticket #578 (closed defect: fixed)

Opened 5 years ago

Last modified 5 years ago

use flag recursion detection is h0nked

Reported by: Berniyh Owned by: ciaranm
Priority: Sometime Milestone:
Component: clients/paludis Version: 0.26.1
Keywords: Cc:
Blocked By: Blocking:
Distribution:

Description

Only happens if metadata is generated:

paludis@1211068254: [WARNING paludis_environment.query_use.recursive] In program paludis (--log-level warning --show-reasons summary --dl-new-slots as-needed --resume-command-template /root/.paludis-resume) -i1 world -p:
  ... When performing install action from command line:
  ... When executing install task:
  ... When building dependency list:
  ... When adding PackageDepSpec 'app-cdr/k3b:kde-svn':
  ... When adding installed package 'app-cdr/k3b-scm:kde-svn::installed':
  ... When adding run dependencies as post dependencies:
  ... When adding PackageDepSpec 'kde-base/libkcddb:kde-svn':
  ... When adding installed package 'kde-base/libkcddb-scm:kde-svn::installed':
  ... When adding run dependencies as post dependencies:
  ... When adding PackageDepSpec 'kde-base/kdelibs:kde-svn':
  ... When adding installed package 'kde-base/kdelibs-scm:kde-svn::installed':
  ... When adding run dependencies as post dependencies:
  ... When adding PackageDepSpec '>=dev-libs/soprano-2.0.98[clucene]':
  ... When querying use flag 'clucene' for 'dev-libs/soprano-scm::kde4-experimental' in Paludis environment:
  ... When generating metadata for ID 'dev-libs/soprano-scm::kde4-experimental':
  ... When saving version metadata to '/var/cache/paludis/metadata/kde4-experimental/dev-libs/soprano-scm':
  ... When querying use flag 'clucene' for 'dev-libs/soprano-scm:0::kde4-experimental' in Paludis environment:
  ... use flag state is defined recursively, forcing it to disabled instead
paludis@1211068254: [WARNING paludis_environment.query_use.recursive] (same context) use flag state is defined recursively, forcing it to disabled instead
paludis@1211068254: [WARNING paludis_environment.query_use.recursive] In program paludis (--log-level warning --show-reasons summary --dl-new-slots as-needed --resume-command-template /root/.paludis-resume) -i1 world -p:
  ... When performing install action from command line:
  ... When executing install task:
  ... When building dependency list:
  ... When adding PackageDepSpec 'app-cdr/k3b:kde-svn':
  ... When adding installed package 'app-cdr/k3b-scm:kde-svn::installed':
  ... When adding run dependencies as post dependencies:
  ... When adding PackageDepSpec 'kde-base/libkcddb:kde-svn':
  ... When adding installed package 'kde-base/libkcddb-scm:kde-svn::installed':
  ... When adding run dependencies as post dependencies:
  ... When adding PackageDepSpec 'kde-base/kdelibs:kde-svn':
  ... When adding installed package 'kde-base/kdelibs-scm:kde-svn::installed':
  ... When adding run dependencies as post dependencies:
  ... When adding PackageDepSpec '>=dev-libs/soprano-2.0.98[clucene]':
  ... When querying use flag 'clucene' for 'dev-libs/soprano-scm::kde4-experimental' in Paludis environment:
  ... When generating metadata for ID 'dev-libs/soprano-scm::kde4-experimental':
  ... When saving version metadata to '/var/cache/paludis/metadata/kde4-experimental/dev-libs/soprano-scm':
  ... When querying use flag 'doc' for 'dev-libs/soprano-scm:0::kde4-experimental' in Paludis environment:
  ... use flag state is defined recursively, forcing it to disabled instead

soprano-scm has:

IUSE="+clucene debug doc elibc_FreeBSD"

nepomuk-scm has:

DEPEND=">=app-misc/strigi-0.5.7[dbus][qt4]
    dev-cpp/clucene
    >=dev-libs/soprano-2.0.98[clucene]"

IIRC, adding this use dep triggered the above.

Change History

comment:1 Changed 5 years ago by ciaranm

  • Status changed from new to closed
  • Resolution set to fixed

r4667

Note: See TracTickets for help on using tickets.