Cannot publish: Creating new version failed: Git tag not found

[yongkangchen]

apm publish patch
Preparing and tagging a new version ✓
Pushing v2.1.6 tag ✓
Publishing remote-sync@v2.1.6 ✗
Creating new version failed: Git tag not found

The repo: https://github.com/vslinko/remote-sync is transferred to me yesterday, I think it may cause this issue. The new url is: https://github.com/yongkangchen/remote-sync

BTW, https://atom.io/packages/remote-sync didn't update the username and url to the latest? Did it will auto update after I publish new version?

[kevinsawicki]

@thedaniel can you take a look at this?

[thedaniel]

I'll take a look - I might have to do some manual updating in the DB. There's a little bit of missing functionality still related to username changes that this is probably related to.

[yongkangchen]

Thanks very much.

[yongkangchen]

Any news?

[yongkangchen]

@thedaniel
My users submit a issue, maybe have something todo with this issue yongkangchen/remote-sync#64.

"Package installation fails":

Unable to download https://www.atom.io/api/packages/remote-sync/versions/2.1.4/tarball: 400 Bad Request Repository inaccessible

[yongkangchen]

still cannot publish, 😢

[joefitzgerald]

+1 - https://github.com/saschagehlich/autocomplete-plus has been transferred to https://github.com/atom-community/autocomplete-plus. I would like to update the registration for this package to match this new ownership and location.

[joefitzgerald]

This is now preventing anyone from installing autocomplete-plus: https://github.com/atom-community/autocomplete-plus/issues/147 - can we get some help on this @thedaniel?

[thedaniel]

@yongkangchen Sorry about that, updated the info in the DB. @joefitzgerald I did the same for autocomplete-plus, and sent you an email as well.

[yongkangchen]

@thedaniel publish now works.
But there still a problem: user cannot update the remote-sync package in setting-view.

I cannot see the latest version of the remote-sync package in setting-view, so I cannot update the package in setting-view.

I guess same problem may exist in autocomplete-plus package.

[yongkangchen]

[yongkangchen]

Uninstall and install will be ok. But the name did not change in atom-setting view:

[joefitzgerald]

@thedaniel @kevinsawicki we have migrated two more packages (related to autocomplete-plus) to the atom-community Github organization:

• https://github.com/atom-community/autocomplete-paths
• https://github.com/atom-community/autocomplete-snippets

Could you please work the same database magic you did for autocomplete-plus?

[joefitzgerald]

@nathansobo @benogle can you help with #218 (comment)?

[thedaniel]

@joefitzgerald done

[joefitzgerald]

Thanks!

[carlosbaraza]

Hi @thedaniel and @kevinsawicki,

I am experiencing the same issue with a recently created package. I changed my username from xel51 to carlosbaraza and now I am not able to publish anymore. If I run apm publish --tag v0.3.1, I get:

Publishing yard@v0.3.1 ✗
Creating new version failed: Git tag not found

The repository causing issues is: https://github.com/carlosbaraza/yard

Thank you very much for the DB magic!

However, it could be nice to handle this kind of cases in an automated way. A possibility could be that every time a package is published, the repository checked for the tags is the last one set up in the package.json. The issue #188 might be related.

[thedaniel]

It could be nice to handle this kind of cases in an automated way.

Agreed, this is definitely on the list of things to do, it just hasn't been done yet. In the meantime I'll fix you up by hand.

[carlosbaraza]

Thank you very much @thedaniel !

[carlosbaraza]

Hi @thedaniel, the issue with the publication is not still fixed. Thank you very much.

[jordiorlando]

Hi guys, I just tried publishing my first package and because of some confusion on my part it got published as v0.2.0. That said, the publish was successful. So to 'fix' the versioning I unpublished the package and then completely deleted the repository, then recreated it with the same name as earlier. Now whenever I try to publish the package apm throws the following error:

➜  language-lc-3 git:(master) apm publish minor
Preparing and tagging a new version ✓
Pushing v0.1.0 tag ✓
Publishing language-lc-3@v0.1.0 ✗
Creating new version failed: Application error

Is there any way someone could fix this for me, perhaps @thedaniel? Thank you in advance.

[necocen]

Hi @thedaniel , I am facing the same problem.
I have destroyed the github repository which is related to the package('kill-ring') for certain reasons, and re-create repository with the same name( https://github.com/necocen/kill-ring ). After that, I have tried to update the package, and received Creating new version failed: Application error message.
Could you please apply the DB magic for me?

[james2doyle]

I would add more detail, but this is all I get

[awatson1978]

Hello. I'm getting these problems with the meteor-api and starrynight-helper packages. Any chance they can be put into the queue to be fixed? Thanks in advance!

[thevuong]

Vuong@DESKTOP-1O626O2 MINGW64 /d/Vuong/GitHub/v-code (master)
$ apm publish minor
Preparing and tagging a new version done
Pushing v0.1.0 tag done
Publishing v-code@v0.1.0 failed
Creating new version failed: Git tag not found

Help me!!!

[thedaniel]

@thevuong Can you link me to the repository for your package?

[thevuong]

@thedaniel my repository: https://github.com/thevuong/v-code
my package: https://atom.io/packages/v-code

[thedaniel]

@thevuong I see you published v0.2.0 since then, but I don't see a tag for it in your git repo. Are you doing anything unusual with your repo, like force pushing, etc?

[thevuong]

ubuntu@ubuntu:/github/v-code$ git ls-remote --tags
From https://github.com/thevuong/v-code.git
7ffd71d2aa347dbe79add9b43aa5781ac9b94e26 refs/tags/v0.1.0
572fe3c89c256d0bad4094fd264e02632fbddada refs/tags/v0.1.0^{}
dd78ce29eac22775ca614c0d1951ceb7d1e4c8e3 refs/tags/v0.1.1
80d993549dad91a83a8858db815000e84efac2d6 refs/tags/v0.1.1^{}
f2097c0a37e2ab19ae9825d2a52df74faf8036d0 refs/tags/v0.1.2
e5ffb79ff5bcb9300fe1152272c057138d8b0e88 refs/tags/v0.1.2^{}
5003961f9292dc0e9f6648f8e6a3e7b6a65126ac refs/tags/v0.1.3
2d35c360cdcd82c92e34754faff299b543142e32 refs/tags/v0.1.3^{}
6c4fc70f1285740402c4b34d617e021a58d077b6 refs/tags/v0.1.4
7b3b30ac735d0f55d24f23d1a7d8911ba5d73e8f refs/tags/v0.1.4^{}
37cbc3bd750bb71238d237753104a3d51e8965d0 refs/tags/v0.1.5
0e3a191e77995e528530c646998300b8e1d34e4a refs/tags/v0.1.5^{}
89c6a5886c8ea94bff2c4f51ef65c4b5841c401c refs/tags/v0.1.6
a5f3a3b20039ef12ffc5cb359745f1ada57cfcf8 refs/tags/v0.1.6^{}
6e082341888534df16f96d93b0364c88cf228a86 refs/tags/v0.1.8
7d07823c8edc11a517df9bbf02b1aeb21fbb7abb refs/tags/v0.1.8^{}
4d290458f2daee9339a7d13f4d27298b6943928b refs/tags/v0.1.9
28618ae6c313a0f87b875d26f570d1831cba2a01 refs/tags/v0.1.9^{}
335a4f87fffe87d9d38ee86096f48e3bfad70bd9 refs/tags/v0.2.0
185d1b5a8d4d7bd292d5fd5a608cef26a9e60d74 refs/tags/v0.2.0^{}
ubuntu@ubuntu:/github/v-code$ apm publish -t "v0.2.0"
Publishing v-code@v0.2.0 ✗
Creating new version failed: Git tag not found

@thedaniel Why "git tag not found"??

[dkatzdev]

I am having the same issue with my language-avr-assembly package. please do your magic for me https://github.com/dkatzdev/language-avr-assembly

[dkatzdev]

it should be v0.3.1 but all the tags and releases got messed up with my attempts to fix it

[nathansobo]

Try deleting the tag, force push away the release commit, and try again. The GitHub issues yesterday caused similar problems for me.

[dkatzdev]

i tried that but it isnt working. I dont know how to force push away a release commit, since i already deleted and reuploaded the entire repo.

[dkatzdev]

I have reuploaded in a new repository PLEASE REMOVE https://github.com/dkatzdev/language-avr-assembly AND https://github.com/dkatzdev/language-assembly-avr from the package database as I am unable to unpublish it @thedaniel