Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tags were moved, but not published #40

Open
BrtnikFM opened this issue Mar 13, 2024 · 18 comments
Open

Tags were moved, but not published #40

BrtnikFM opened this issue Mar 13, 2024 · 18 comments

Comments

@BrtnikFM
Copy link

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

@BrtnikFM BrtnikFM changed the title Tags were moved,. but not published Tags were moved, but not published Mar 13, 2024
@YevgenZi
Copy link

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

@maxhille
Copy link

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

@kokizzu
Copy link

kokizzu commented Mar 13, 2024

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
Copy link

kokizzu commented Mar 13, 2024

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
Copy link

kokizzu commented Mar 13, 2024

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
Copy link

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
Copy link

Any update on resolving this?

@rvantonder
Copy link

+1 for this issue

@p-grummel
Copy link

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

@p-grummel
Copy link

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

mostlyobvious added a commit to RailsEventStore/rails_event_store that referenced this issue Mar 19, 2024
@ryan-haskell
Copy link
Owner

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
Copy link

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
Copy link
Owner

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

@AlexandreHerbreteau
Copy link

Hello Ryan, thanks a lot for your answer, this solved my issue.
Initially, I used elm-json upgrade in order to update Elm Charts(from 3.0.0 to 4.0.0), but no change was detected !
Now that you point me on this new version, I uninstall + install a new time elm charts, and it magically installs in 4.0.0 version, which is the new version. Since then, no more dependency to your old package.

Thanks !

@nevrome
Copy link

nevrome commented Mar 21, 2024

I also ran into this issue, because I'm using elm-charts. I personally struggled a bit to update terezka/elm-charts. When I removed it from the elm.json file and then ran elm install terezka/elm-charts it would always fall back to version 3.0.0, not the new 4.0.0.

I had to remove all of the following packages from the elm.json file to make it detect the latest version correctly:

ryan-haskell/date-format
terezka/elm-charts
terezka/intervals

@Iphi-Jeff
Copy link

Hi @ryan-haskell , just want to let you know that the issue is also on elm-transformer. Thanks

`@parcel/elm-transformer:
-- 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: 86534146f5a550bb8e87b87a7484ea5732090bb5

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.`

@loicknuchel
Copy link

Hi,

I upgraded my elm.json and got "ryannhg/date-format": "2.3.0" replaced by "ryan-haskell/date-format": "1.0.0" so I don't have this error anymore, like @pgit19 I suppose.

But now I get a similar one on: "ryannhg/elm-spa": "6.0.0"

Verifying dependencies (58/58)-- CORRUPT PACKAGE DATA --------------------------------------------------------
[2024-03-27 18:35:49] │ 
[2024-03-27 18:35:49] │ I downloaded the source code for ryannhg/elm-spa 6.0.0 from:
[2024-03-27 18:35:49] │ 
[2024-03-27 18:35:49] │     https://github.com/ryannhg/elm-spa/zipball/6.0.0/
[2024-03-27 18:35:49] │ 
[2024-03-27 18:35:49] │ But it looks like the hash of the archive has changed since publication:
[2024-03-27 18:35:49] │ 
[2024-03-27 18:35:49] │   Expected: ef713492aac6715e88fba5231c42f7d1caec7175
[2024-03-27 18:35:49] │     Actual: b4134ea4f324d0620b1be7048e18fb72624566ce
[2024-03-27 18:35:49] │ 
[2024-03-27 18:35:49] │ This usually means that the package author moved the version tag, so report it
[2024-03-27 18:35:49] │ to them and see if that is the issue. Folks on Elm slack can probably help as well.

When I look at https://github.com/ryan-haskell/elm-spa I see that the last release is 6.0.6.
But looking at https://package.elm-lang.org/packages/ryannhg/elm-spa/latest, the last release is 6.0.0.
And https://package.elm-lang.org/packages/ryan-haskell/elm-spa/latest last release is 1.0.0.

Replacing "ryannhg/elm-spa": "6.0.0" with "ryan-haskell/elm-spa": "1.0.0" fixed the issue.
Posting here to help others and maybe it could help to add a warning message about these changes to ease the transition.
Cheers!

@luispedro
Copy link

luispedro commented Mar 30, 2024

https://github.com/dillonkearns/elm-rss also depends on this package through https://github.com/dmy/elm-imf-date-time

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests