# This test checks that when there are two major versions of a module
# with no default, we don't try to resolve to one of them, but instead
# report an error about the ambiguity.

# TODO the error currently does not mention the actual ambiguity that caused
# the issue - that should be fixed.
-- want --
error: failed to resolve "example.com/foo": cannot find module providing package example.com/foo
-- tidy-check-error --
module is not tidy: cannot find module providing package example.com/bar@v1
-- cue.mod/module.cue --
module: "main.org@v0"
language: version: "v0.99.99"
-- main.cue --
package main

import (
	"example.com/foo@v0"
	"example.com/bar@v1"
)
-- other.cue --
package main
import "example.com/foo"

-- _registry/example.com_v0.0.1/cue.mod/module.cue --
module: "example.com@v0"

-- _registry/example.com_v0.0.1/foo/foo.cue --
package foo

-- _registry/example.com_v1.0.0/cue.mod/module.cue --
module: "example.com@v1"

-- _registry/example.com_v1.0.0/bar/bar.cue --
package bar