-
Notifications
You must be signed in to change notification settings - Fork 30
Description
Is there an existing issue for this?
- I have searched the existing issues
Current Behavior
Similar to #724.
$ git checkout 80aab9610438516303e213a5dc5692b88836d93c~1
$ cd dev-lang/rust && pkgcheck scan -k NonexistentDeps
dev-lang/rust
NonexistentDeps: version 1.84.1-r1: BDEPEND: nonexistent packages: dev-lang/rust-bin:1.84.0, dev-lang/rust:1.84.0
NonexistentDeps: version 1.85.0: BDEPEND: nonexistent packages: dev-lang/rust-bin:1.84.0, dev-lang/rust:1.84.0
NonexistentDeps: version 1.86.0_beta20250218: BDEPEND: nonexistent packages: dev-lang/rust-bin:1.84.0, dev-lang/rust:1.84.0
More generally: I think the issue here is that we don't consider time it has been missing for. It seems to me that we should treat this the same as OutdatedBlocker and only warn if it's been gone from git for $PERIOD.
(In this situation: The eclass has a large || ( ... ) reflecting that Rust versions need a specific earlier version to build Rust. The NonexistentDeps warning here encourages that || ( ... ) block to be cleaned up as soon as 1.84.0 is removed from tree, even though it's perfectly valid to use for building 1.84.1 if already installed.
i.e. The warning here doesn't account for the fact that removing 1.84.0 as a dep is harmful.)
Expected Behavior
Make NonexistentDeps similar to OutdatedBlocker in that it'll check git to see how long something has been unsolvable for.
pkgcheck version
0.10.33
pkgcore version
0.12.29