Skip to content
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

[New Check]: Detect pre-pkgmove (inherited from masters) name being used in repository #650

Closed
1 task done
thesamesam opened this issue Jan 14, 2024 · 1 comment · Fixed by #653
Closed
1 task done
Assignees
Labels

Comments

@thesamesam
Copy link
Member

Is there an existing such new check request for this?

  • I have searched the existing issues

Explain

We should warn on cases where a master repository A has a pkgmove, but a repository B with A as its master still has the pre-pkgmove name (forked version o the package).

Suppose repository A has a pkgmove dev-util/meson -> dev-build/meson. If a repository B with master A still has dev-util/meson/meson-1.2.3.ebuild, we should error out.

Examples

N/A

Output message

OldPackageName

Documentation

Package is using ${CATEGORY}/${PN} which is the source of a pkgmove. It should be updated to the destination (new name) from one of its master repositories.

Result level

error

@thesamesam
Copy link
Member Author

See also #566.

@arthurzam arthurzam self-assigned this Jan 16, 2024
arthurzam added a commit to arthurzam/pkgcheck that referenced this issue Jan 16, 2024
Resolves: pkgcore#650
Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants