Corrupt Package Data when downloading about phosphor-elm

[jaredramirez]

I think the best thing is what @lue-bird suggested.

1. In the current (now with the reverted name) package, update the readme saying this package is deprecated
2. Rename the repo & package name
3. Republish a "new" elm package under the new name as v1.0.0 (elm packages auto-namespace based on the github org/owner's name)

Then I, or anyone else, can update our apps to use the newly named version and the repo's naming scheme is consistent with all y'alls other packages/planned changes.

[jaredramirez]

Ah, yes that's probably it! Thanks for the prompt reply!

[jaredramirez]

Or republish under a slightly different name?

[rektdeckard]

Temporarily reverted the rename, your projects should be building now (just tested on a bare app).

[rektdeckard]

Hi @jaredramirez, sorry to hear about that! I recently renamed this repo, it is possible that has something to do with it, now that the name field in elm.json is no longer correct. I guess I made the assumption that Github redirects would hold here too.

Thanks for the issue. Will try to push out a patch today.

[lue-bird]

And I don't think package owners can do anything about it except renaming back maybe (?).
Something something github hash is different after renaming

[lue-bird]

Yeah publishing a new package with the current repo name phosphor-icons/elm has to be done anyway.
Best to then also publish another version under the phosphor-icons/elm-phosphor name leaving a note redirecting to the new package with the name phosphor-icons/elm

[rektdeckard]

Or maybe just rename the repo back? I'm not super knowledgeable about the Elm ecosystem, best-practices, etc. Will defer to you all on best approach.

[rektdeckard]

Ideally this would be published at @phosphor-icons/elm to match the org namespacing on NPM and planned relocations we have for our other JS packages. Not sure if that's a thing on package.elm-lang.org though.