The transferrer right now reuses the legacy importer logic that verifies a package address as listed in the legacy registry files is the same as the location of its latest tag. On failure, the transferrer is skipping that package. Of course, this is exactly the circumstance in which we should transfer the package!
Due to this issue, 20 packages have not been transferred and have not been receiving updates since the legacy importer considers this a package failure. 18 of them should be transferred (the location they redirect to is valid / not in use). These 18 packages are not being updated by the legacy importer because a redirecting URL is considered a PackageURLRedirect error to prevent us from publishing packages that have moved and been re-registered.
Here are the packages that moved locations but were re-registered and won't be transferred:
Package purescript-heterogeneous-extrablatt has moved to https://github.com/rowtype-yoga/purescript-record-studio.git
New location https://github.com/rowtype-yoga/purescript-record-studio.git is not unique; package will not be transferred.
Package purescript-web-intl has moved to https://github.com/pete-murphy/purescript-js-intl.git
New location https://github.com/pete-murphy/purescript-js-intl.git is not unique; package will not be transferred.
Here's the full list of packages that ought to be transferred (and will be automatically with this PR):
The transferrer right now reuses the legacy importer logic that verifies a package address as listed in the legacy registry files is the same as the location of its latest tag. On failure, the transferrer is skipping that package. Of course, this is exactly the circumstance in which we should transfer the package!
Due to this issue, 20 packages have not been transferred and have not been receiving updates since the legacy importer considers this a package failure. 18 of them should be transferred (the location they redirect to is valid / not in use). These 18 packages are not being updated by the legacy importer because a redirecting URL is considered a
PackageURLRedirect
error to prevent us from publishing packages that have moved and been re-registered.Here are the packages that moved locations but were re-registered and won't be transferred:
Here's the full list of packages that ought to be transferred (and will be automatically with this PR):