0

I'm having an issue with a repository of mine where the list of dependents includes a reference to the original repository.

enter image description here

The dependency list in the Cargo.toml file does not include a reference to itself, however I discovered that the generated Cargo.lock file does:

[[package]]
name = "polykill"
version = "0.2.0"
dependencies = [
 "bytesize",
 "clap",
 "console",
]

(line 219-226 of Cargo.lock)

Is this normal behaviour? I haven't noticed any other problems caused by this recursive dependency but I was very confused when I saw this.

Here is the repository.

Bdeering
  • 338
  • 3
  • 14
  • 1
    Please post code, errors, sample data or textual output here as plain-text, not as images that can be hard to read, can’t be copy-pasted to help test code or use in answers, and are barrier to those who depend on screen readers or translation tools. You can edit your question to add the code in the body of your question. For easy formatting use the `{}` button to mark blocks of code, or indent with four spaces for the same effect. The contents of a **screenshot can’t be searched, run as code, or easily copied and edited to create a solution.** – tadman May 04 '23 at 21:41
  • does cargo.lock really mean it's a dependency? – user253751 May 04 '23 at 21:41
  • 2
    The parent crate being present in the `Cargo.lock` is normal. It's not there as a dependency. This may a bug on Github's part. – PitaJ May 04 '23 at 21:42
  • You can always file a bug report with GitHub. – tadman May 05 '23 at 02:21

0 Answers0