stdout '^example.net/b v0.1.0 '
stdout '^example.net/c '  # BUG, but a minor and rare one


-- go.mod --
module example

go 1.15

replace (
	example.net/a v0.1.0 => ./a1
	example.net/b v0.1.0 => ./b1
	example.net/b v0.2.0 => ./b2
	example.net/c v0.1.0 => ./c1
	example.net/c v0.2.0 => ./c1
)

-- a1/go.mod --
module example.net/a

go 1.15

	example.com/d v0.1.0 => ./d
	example.com/d v0.2.0 => ./d
)
-- go.mod.down1 --
module example.com/a

go 1.15

require (
	example.com/b v0.1.0
	example.com/c v0.2.0
	example.com/d v0.1.0 // indirect
)

replace (
	example.com/b v0.1.0 => ./b1
	example.com/b v0.2.0 => ./b2
	example.com/c v0.1.0 => ./c1
	example.com/c v0.2.0 => ./c2
	example.com/d v0.1.0 => ./d
	example.com/d v0.2.0 => ./d
)

go get example.net/split/nested@v0.0.0

go get example.net/...@v0.1.0
go list -m all
stdout '^example.net/split v0.1.0 '
stdout '^example.net/split/nested v0.1.0 '

go get example.net/...
go list -m all
stdout '^example.net/split v0.3.0 '
stdout '^example.net/split/nested v0.2.0 '


# @none applies to all matching module paths,
# regardless of whether they contain any packages.

go get example.net/...@none

go list -m all
stdout '^example.net/m v0.1.0 '
! stdout '^example.net/m/p '
cp go.mod go.mod.orig

# Upgrading example.net/m/p without also upgrading example.net/m
# causes the import of package example.net/m/p to be ambiguous.
#
# TODO(#27899): Should we automatically upgrade example.net/m to v0.2.0
# to resolve the conflict?
! go get example.net/m/p@v1.0.0

go get example.net/pkgremoved@patch
! go list example.net/pkgremoved

# ... and module to package.

go get example.net/pkgremoved@v0.4.0
! go list example.net/pkgremoved

go get example.net/pkgremoved@patch
go list example.net/pkgremoved
stdout 'example.net/pkgremoved'


-- go.mod --
module example

go 1.16

replace (
	example.net/other v0.1.0 => ./other

	example.net/b v0.2.1 => ./b
	example.net/b v0.3.0 => ./b
	example.net/b v0.3.1 => ./b
)
-- example.go --
package example

import _ "example.net/a"

-- a10/go.mod --
module example.net/a

go 1.16

require example.net/b v0.1.0
-- a10/a.go --
package a

import _ "example.net/b"

-- a11/go.mod --
module example.net/a

go 1.16

require example.net/b v0.2.0  // upgraded

    <file url="file://$PROJECT_DIR$/libraries/examples/browser-example/src/main/resources" charset="UTF-8" />
    <file url="file://$PROJECT_DIR$/libraries/examples/js-example" charset="UTF-8" />
    <file url="file://$PROJECT_DIR$/libraries/examples/js-example/src/main/kotlin" charset="UTF-8" />

  hostnames:
    - "bar.com" # doesn't match abc-foo-example-com listener
    - "*.example.com" # becomes abc.foo.example.com as it cannot be less specific than abc.foo.example.com of the listener
    - "*.foo.example.com" # becomes abc.foo.example.com as it cannot be less specific than abc.foo.example.com of the listener
    - "abc.foo.example.com"
  rules:
    - matches:
        - path:
            type: PathPrefix

stderr '^go: example\.net/m imports\n\texample\.net/w: package example\.net/w provided by example\.net/w at latest version v0\.1\.0 but not at required version v0\.2\.0-pre$'
stderr '^go: example\.net/m imports\n\texample\.net/y: package example\.net/y provided by example\.net/y at latest version v0\.1\.0 but not at required version v0\.2\.0-pre$'

	example.net/b v0.3.0 => ./b3
	example.net/c v0.1.0 => ./c1
	example.net/c v0.2.0 => ./c2
	example.net/d v0.1.0 => ./d
	example.net/d v0.2.0 => ./d
	example.net/e v0.1.0 => ./e
)
-- a.go --
package a

import (
	_ "example.net/b"
	_ "example.net/c"
)

-- b1/go.mod --
module example.net/b

go 1.16

require example.net/e v0.1.0
-- b1/b.go --
package b

import _ "example.net/e"