>>> Emerging : portage://net-dns/bind-tools-9.18.0-r1:run?{[]}

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

Calculating dependencies... done!

 └─step  1─┤ unmask  portage://net-dns/bind-tools-9.18.0-r1

 └─step  2─┤ verify  net-dns/bind (version unavailable, assumed running)
             │ download  portage://net-dns/bind-tools-9.18.0-r1

 └─step  3─┤ install   portage://net-dns/bind-tools-9.18.0-r1 (unmasked)
             │           └─ conf ─┤ USE = "readline caps -doc -gssapi -idn -libedit -xml"

 └─step  4─┤ run     portage://net-dns/bind-tools-9.18.0-r1

Total: 4 actions (1 unmask, 1 download, 1 install, 1 run), grouped into 4 steps.
       0.00 Kb to be downloaded.



>>> Assumptions taken during proving & planning:

  Package unmask (1 package):
  Add to /etc/portage/package.unmask:
    =net-dns/bind-tools-9.18.0-r1


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


>>> Domain assumptions

- Unsatisfied version constraint for run dependency: 
  wildcardnet-dns/bind-9.18* [ caps? doc? gssapi? idn? xml? ]

  required by: portage://net-dns/bind-tools-9.18.0-r1


>>> Bug report drafts (Gentoo Bugzilla)

---
Summary: portage://net-dns/bind-tools-9.18.0-r1: unsatisfiable version constraint dependency on net-dns/bind

Affected package: portage://net-dns/bind-tools-9.18.0-r1
Dependency: net-dns/bind
Phases: [run]

Unsatisfiable constraint(s):
  wildcardnet-dns/bind-9.18*

Observed:
  portage-ng reports no available candidate satisfies the above constraint(s).
  Available versions in repo set (sample, first 2 of 2): [9.20.27,9.20.29]

Potential fix (suggestion):
  One constraint has zero matches: wildcard9.18*. Consider relaxing/removing that bound after verifying compatibility.
  Available versions for net-dns/bind: 9.20.27 .. 9.20.29 (2 total).