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

Old zipballs no longer available #8

Closed
alienscience opened this issue Aug 31, 2018 · 5 comments
Closed

Old zipballs no longer available #8

alienscience opened this issue Aug 31, 2018 · 5 comments

Comments

@alienscience
Copy link

alienscience commented Aug 31, 2018

Hello,
We have an Elm project whose Jenkins builds failed with the following error this morning:

    07:17:43 Error: The following HTTP request failed.
    07:17:43 <https://github.com/avh4/elm-transducers/zipball/3.0.1/>
    07:17:43 
    07:17:43 404: Not Found

It appears that the project has been reset to version 1:0:
https://github.com/avh4-experimental/elm-transducers/blob/master/elm.json#L6

Is this something we need to workaround on our side or is there something you can do to restore the URL?

Many thanks for your help.

@avh4
Copy link
Collaborator

avh4 commented Aug 31, 2018

Hmm, Elm doesn't seem to support renaming packages at all, so I'm trying to find some hack that will work... I tried re-adding the 3.0.1 tag. Let me know if that works.

@alienscience
Copy link
Author

Many thanks for the quick reply. I tried again and we no longer get a 404. However, there is still an error with elm-package:

Error: Problem when downloading the avh4/elm-transducers 3.0.1 code.

I tried renaming the dependency to avh4-experimental/elm-transducers and that also fails:

Error: Could not find any packages named avh4-experimental/elm-transducers.

Here are some packages that have similar names:

    avh4-experimental/elm-layout
    avh4/elm-transducers
    avh4-experimental/elm-compose-programs
    sawaken-experiment/elm-lisp-parser

If we find a workaround I will add it to this bug report.

@avh4
Copy link
Collaborator

avh4 commented Aug 31, 2018

Hrm, that sucks :(

Maybe Elm 0.18 depends on the filename of the resulting file and the redirect is confusing it? That seems unlikely, but in any case I just tried forking avh4-experimental/elm-transducers back to avh4/elm-transducers. @alienscience Let me know if that fixes things.

@avh4
Copy link
Collaborator

avh4 commented Aug 31, 2018

I just tried making an empty folder, and then with Elm 0.18:

console output
$ elm-package install avh4/elm-transducers
To install avh4/elm-transducers I would like to add the following
dependency to elm-package.json:

    "avh4/elm-transducers": "3.0.1 <= v < 4.0.0"

May I add that to elm-package.json for you? [Y/n] y

Some new packages are needed. Here is the upgrade plan.

  Install:
    avh4/elm-transducers 3.0.1
    elm-lang/core 5.1.1
    elm-lang/html 2.0.0
    elm-lang/virtual-dom 2.0.4

Do you approve of this plan? [Y/n] y
Starting downloads...

  ● elm-lang/virtual-dom 2.0.4
  ● avh4/elm-transducers 3.0.1
  ● elm-lang/core 5.1.1
  ● elm-lang/html 2.0.0

Packages configured successfully!

and it worked for me. So hopefully it is fixed (at least until the new package name gets up to a 3.0.1 version, in which case I guess the Elm 0.18 version will break again, but I don't expect to be doing new major versions any time soon).

@alienscience But let me know if it works for you now.

@alienscience
Copy link
Author

I am sorry for the slow reply. This worked..

Many thanks for the help.

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

2 participants