• I am on the latest Poetry version.
• I have searched the issues of this repo and believe that this is not a duplicate.
• If an exception occurs when executing a command, I executed it again in debug mode (-vvv option).

• Centos 7:
• 1.0b4:
• Link of a Gist with the contents of your pyproject.toml file: https://gist.github.com/dimbleby/0721a2b8ce3b138e5d4d1f88092113c5 (shows the general shape, I have redacted details of my actual custom repository)

Issue

If I use a custom repository, as in:

[[tool.poetry.source]]
name = "custom"
url = "https://example.com/api/pypi/pypi-virtual/simple"

then any packages installed from that repository are redundantly re-installed at poetry update.

I believe the reason is that:

• the desired package source type is marked as 'legacy' in poetry.lock:

[package.source]
reference = "custom"
type = "legacy"
url = "https://example.com/api/pypi/pypi-virtual/simple"

• but the found package source type is left empty, here
• so this code decides that an update is needed

cf this comment. On the plus side, I think that bf2d515 has probably fixed #1240; but it has introduced at least this case where we make unnecessary updates (and maybe others too?).