-
Notifications
You must be signed in to change notification settings - Fork 17.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cmd/go: conversion from legacy dependency managers puts replacement module path in require section #33406
Labels
help wanted
modules
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone
Comments
bcmills
changed the title
cmd/go: go mod init command puts replace's new module path in require section
cmd/go: conversion from Dep puts replacement module path in require section
Aug 2, 2019
bcmills
added
modules
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
labels
Aug 2, 2019
@liuchang0812, is this still an issue? |
bcmills
added
WaitingForInfo
Issue is not actionable because of missing required information, which needs to be provided.
and removed
WaitingForInfo
Issue is not actionable because of missing required information, which needs to be provided.
labels
Sep 16, 2019
Never mind, spotted an issue in |
CC @jayconrod @oiooj |
bcmills
changed the title
cmd/go: conversion from Dep puts replacement module path in require section
cmd/go: conversion from legacy dependency managers puts replacement module path in require section
Sep 26, 2019
@liuchang0812, I don't think we even need a new test case. We need to fix the existing |
This is no longer needed due to #53327. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
help wanted
modules
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
run
go mod init
with a dep project that contains source config.What did you expect to see?
go.mod should put module's old path in require section.
What did you see instead?
go.mod put module's new path in require section.
The text was updated successfully, but these errors were encountered: