>>> Emerging : portage://dev-libs/liborcus-0.20.0:run?{[]}

These are the packages that would be merged, in order:

Calculating dependencies... done!

 └─step  1─┤ unmask  portage://dev-libs/libixion-0.20.0
             │ unmask  portage://dev-libs/liborcus-0.20.0

 └─step  2─┤ download  portage://dev-build/b2-5.5.3
             │           └─ file ─┤ 1.17 Mb  	 b2-5.5.3.tar.gz
             │ download  portage://dev-libs/boost-1.91.0-r2
             │           └─ file ─┤ 195.10 Mb  	 boost_1_91_0.tar.bz2
             │ download  portage://dev-libs/libixion-0.20.0
             │           └─ file ─┤ 532.01 Kb  	 libixion-0.20.0.tar.xz
             │ download  portage://dev-libs/liborcus-0.20.0
             │           └─ file ─┤ 3.07 Mb  	 liborcus-0.20.0.tar.gz
             │ download  portage://dev-util/mdds-2.1.1-r1
             │           └─ file ─┤ 528.06 Kb  	 mdds-2.1.1.tar.xz

Total: 7 actions (2 unmasks, 5 downloads), grouped into 2 steps.
       200.38 Mb to be downloaded.



>>> Assumptions taken during proving & planning:

  Keyword acceptance (1 package):
  Add to /etc/portage/package.accept_keywords:
    dev-util/mdds **

  Package unmask (2 packages):
  Add to /etc/portage/package.unmask:
    =dev-libs/libixion-0.20.0
    =dev-libs/liborcus-0.20.0


Error The proof for your build plan contains domain assumptions. Please verify:


>>> Domain assumptions

- Keyword filtered (assumed accepted) install dependency: 
  dev-util/mdds:1/3.0

  required by: portage://dev-libs/liborcus-0.20.0


>>> Bug report drafts (Gentoo Bugzilla)

---
Summary: portage://dev-libs/liborcus-0.20.0: keyword-filtered dependency on dev-util/mdds

Affected package: portage://dev-libs/liborcus-0.20.0
Dependency: dev-util/mdds
Phases: [install]

Unsatisfiable constraint(s):
  dev-util/mdds-:1/3.0

Observed:
  portage-ng reports no available candidate satisfies the above constraint(s).
  Available versions in repo set (sample, first 3 of 3): [2.1.1-r1,3.0.0,9999]

Potential fix (suggestion):
  Candidates exist but none match ACCEPT_KEYWORDS. Consider keywording or adjusting KEYWORDS/ACCEPT_KEYWORDS as appropriate.