You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
Is there an existing such new check request for this?
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 hasdev-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
The text was updated successfully, but these errors were encountered: