search

alohaas / language-nunjucks

Syntax highlighting for nunjucks templates in atom.
MIT License
42 stars 13 forks source link

Installing from within atom.io(0.147.0) error #2

Closed toddbluhm closed 9 years ago

toddbluhm commented 9 years ago

When I try to install this package from within atom.io I receive the following error:

Installing “language-nunjucks@1.1.0” failed. Hide output…
Unable to download https://www.atom.io/api/packages/language-nunjucks/versions/1.1.0/tarball: 400 Bad Request Repository inaccessible

Is the lastest version just not published to apm yet?

alohaas commented 9 years ago

Hey @toddbluhm, This issue came up because I changed my github username recently...maybe not the best decision in retrospect. All of my repos were fine, but I recently encountered the same error when I reinstalled atom on a new computer and tried to download my own package XD

The issue is I do not have publication access to the package via apm so the install script is looking for the repo at /livhaas/language-nunjucks not /alohaas/language-nunjucks. I have reached out to atom.io to see if they can address this issue, but if not, I see two options. Maybe you can help me make a decision:

  1. Republish the package under a new name with my new account.
  2. Switch my github username back to 'livhaas'

any ideas? I'm inclined to go with #1

toddbluhm commented 9 years ago

How does atom.io establish publication rights? Maybe this is way off, but what if you created a new user on github with your old username, could you reestablish apm publication rights with that? All you need to do is be able to unpublish the old version and then you can republish under your new name.

Otherwise I am inclined to say that #1 is the best bet, unless you don't mind switching back to your old username just to unpublish the package...but that could create a lot of other issues for you. This is one discussion I ran into while researching a bit, its a similar issue: https://discuss.atom.io/t/could-not-unpublish-my-package/3041/5. Maybe that will help. No matter what, we atleast know #1 will work!

alohaas commented 9 years ago

@toddbluhm great news! Github staff identified the bug and fixed the error for my package. They are working on fixing the issue for future username switches as well.

Cheers!

toddbluhm commented 9 years ago

Yay! Thanks!