Migrate packages dependent on vbom.ml/util vanity path to the new paths. #7
Comments
This was referenced Sep 13, 2020
prymitive
pushed a commit
to prymitive/karma
that referenced
this issue
Sep 13, 2020
This was referenced Sep 13, 2020
agnivade
pushed a commit
to agnivade/funnel
that referenced
this issue
Sep 14, 2020
thediveo
pushed a commit
to thediveo/klo
that referenced
this issue
Sep 15, 2020
* Run 'go mod tidy' * Replace sortorder package with new version. Refs fvbommel/util#7
|
With all of the pull requests merged except for the two that got no response at all (both in repositories that haven't had any commits in almost 6 months), I'm declaring this effort a success. |
stgraber
pushed a commit
to canonical/lxd
that referenced
this issue
Sep 24, 2020
This was bundled in PR #7786 due to #7784. The package has since moved to a more stable import path (github.com/fvbommel/sortorder). See fvbommel/util#7 Signed-off-by: Frits van Bommel <fvbommel@gmail.com>
placintaalexandru
pushed a commit
to placintaalexandru/k9s
that referenced
this issue
Apr 3, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Due to some issues with the server handling the vanity imports (see #5 and #6), I unfortunately had to move this package to
github.com/fvbommel/util. Since I was breaking import paths anyway, I decided to also move the much more popularsortordersub-package togithub.com/fvbommel/sortorderinstead.However, a large number of external packages are still dependent on the old import path for the
sortorderpackage. While most of those seem to be forks, I'd like to help migrate at least the original repositories to the new import path (assuming that any actively-used forks will then automatically migrate when they sync changes from their origin).This is a tracking issue for that effort.
The text was updated successfully, but these errors were encountered: