Tags were moved, but not published

[BrtnikFM]

I started to get complilation error: Same for 2.2.0 and 2.3.0

I downloaded the source code for ryannhg/date-format 2.3.0 from:

https://github.com/ryannhg/date-format/zipball/2.3.0/

But it looks like the hash of the archive has changed since publication:

Expected: 70c67866fed499bec685f43f23fea279556757f2
Actual: 86534146f5a550bb8e87b87a7484ea5732090bb5

[YevgenZi]

@ryan-haskell pls republish package as 2.3.1. Your readme update changed hash

[maxhille]

If possible, moving the tag back to "repair" 2.3.0 would be even better I'd say.

[kokizzu]

find replace ryannhg to ryan-haskell also didn't work:

-- INCOMPATIBLE DEPENDENCIES ------------------------------------------ elm.json
The dependencies in your elm.json are not compatible.
Did you change them by hand? Try to change it back! It is much more reliable to
add dependencies with elm install or the dependency management tool in
elm reactor.
Please ask for help on the community forums if you try those paths and are still

[kokizzu]

elm install ryan-haskell/date-format
Here is my plan:
  
  Add:
    ryan-haskell/date-format    1.0.0
    ryannhg/date-format         2.3.0

also still breaks because it imported ryannhg/date-format@2.3.0 as indirect

[kokizzu]

apparently in my case (after checking with proper tool: elm-json caused by elm-visualization that still depend on old ryannhg/date-format, so i forked both to kokizzu/elm-visualization and kokizzu/elm-date-format and it works now.

at least this is temporary solution until all dependencies updated

[lxadtz33]

We also are seeing the issue:

Verifying dependencies (27/27)-- CORRUPT PACKAGE DATA --------------------------------------------------------
I downloaded the source code for ryannhg/date-format 2.3.0 from:
    https://github.com/ryannhg/date-format/zipball/2.3.0/
But it looks like the hash of the archive has changed since publication:
  Expected: 70c67866fed499bec685f43f23fea279556757f2
    Actual: 8[65](https://gitlab.com/leadid-dev/jornaya-ui/webapp-admin/-/jobs/6384159223#L65)34146f5a550bb8e87b87a7484ea5732090bb5
This usually means that the package author moved the version tag, so report it
to them and see if that is the issue. Folks on Elm slack can probably help as
well.
Dependency problem!

[lxadtz33]

Any update on resolving this?

[rvantonder]

+1 for this issue

[p-grummel]

I used
elm-json upgrade
to resolve the problem in my project

[p-grummel]

The line in my elm.json now looks like this:
"ryan-haskell/date-format": "1.0.0"

[ryan-haskell]

Hi all, happy to help with this issue- but I'm not sure exactly how to implement the suggestions here.

This is the first time I've messed with my username and tags for an Elm package, so your guidance would be appreciated!

For solutions involving tagging, could you walk me through the git commands and elm publish commands you are hoping I can run?

---

For folks that are blocked on this, my package consists of three Elm files, and I think the easiest solution is to move them into your codebase.

I'm sure many of you have done this, but for anyone who are feeling stuck in the interim- this code is open source and free to steal! It only depends on elm/core and elm/time.

---

Sorry for the inconvenience, I expected republishing my package would "just work" for folks- I didn't anticipate people to have issues with the old tags (or it somehow depending on an old version of itself!)

Any help would be appreciated, thank you all!

[AlexandreHerbreteau]

Hi. Please let me share my concern:
For me, using elm-json upgrade does not work because date-format is still linked in the old version of the lib (2.3.0) as indirect library, linked to this library: "terezka/elm-charts": "3.0.0" (https://www.elm-charts.org/)
So, simply copying the 3 sources files won't work for me.
The only way could be to publish a new tag. But technically I'm not used with elm publishing, sorry I can't help.

[ryan-haskell]

Hi. Please let me share my concern: For me, using elm-json upgrade does not work because date-format is still linked in the old version of the lib (2.3.0) as indirect library, linked to this library: "terezka/elm-charts": "3.0.0" (https://www.elm-charts.org/) So, simply copying the 3 sources files won't work for me. The only way could be to publish a new tag. But technically I'm not used with elm publishing, sorry I can't help.

Ahh, I see! This is from another Elm package that depends on mine.

Tereza was able to release a new version of Elm Charts with the updated dependency last week:
https://github.com/terezka/elm-charts/blob/master/elm.json
As a bonus, they were even kind enough to update the older line charts, for those who haven’t made the switch yet.

—-

Still open to concrete steps I can take on my end, in case folks are able to provide specific git / elm publish commands