Skip to content
This repository has been archived by the owner on Dec 15, 2022. It is now read-only.

Creating new version failed: Git tag not found #873

Open
pelevesque opened this issue Nov 4, 2019 · 10 comments
Open

Creating new version failed: Git tag not found #873

pelevesque opened this issue Nov 4, 2019 · 10 comments

Comments

@pelevesque
Copy link

Prerequisites

Description

I had problems publishing my syntax highlighter package language-orfeo and did the unfortunate mistake of deleting my git repo and republishing it a few times trying to solve the problem. This created the same issue as #670, #770, and #870

When I try to publish - I get the git tag not found error.
When I try to unpublish - I get the unauthorized error.

I think I need a moderator or an admin to fix the atm database for me so that I can publish my package.

For now, I'm asking my users to install it manually which is less than ideal. I'm hoping this can be resolved sooner than later.

This is my git repo: https://github.com/orfeo-lang/atom-language-orfeo

@pelevesque
Copy link
Author

I removed the git repo - I will add it again once this is resolved. Please let me know as I would love to have my package obtainable from the Atom's Package Manager.

@UziTech
Copy link
Contributor

UziTech commented Feb 26, 2020

Same issue with x-terminal after transferring the repo.

@UziTech
Copy link
Contributor

UziTech commented Feb 26, 2020

I think we got it figured out. Thankfully I didn't delete the original repo, just renamed it.

@pelevesque
Copy link
Author

@lkashef or someone else.

This issue persists for me. I did the mistake of creating a git repo, then deleting it.

I would love to be able to resolve it.

My repo: https://github.com/orfeo-lang/atom-language-orfeo

I want to run: apm publish minor to publish v0.1.0 of this package.

It still creates the problem - Creating new version failed: Git tag not found

In #870, madiedgar had the same issue and it was fixed by @lkashef. I'm hoping the same could happen here.

@lkashef
Copy link

lkashef commented Jul 2, 2020

Hey @pelevesque, thanks for the report!

I will work on pulling some records on our end and update you here as soon as I have a fix

@pelevesque
Copy link
Author

@lkashef

Thanks, that would be awesome. I think you were able to fix it for madiedgar in #870

I'm creating a new programming language for music and planning a release soon, so I would love this to be fixed for that.

@lkashef
Copy link

lkashef commented Jul 2, 2020

@pelevesque sounds cool, I am currently working on other stuff but will try to jump on this as soon as I can

@pelevesque
Copy link
Author

@lkashef - Just wondering if you'll have a bit of time to look at this soon? I'm planning a release of my language near the end of August. I'm hoping to stay with Atom's convention of using 'language-x' for syntax highlighters. I guess I can go with 'x-lang' or 'x-language' if this isn't resolved, but it seems better to stick to conventions.

@pelevesque
Copy link
Author

@lkashef - I gave up waiting and published to a new name which actually is better since my language also has a file format, giving me two syntax highlighters. Published to language-orfeo-timeline

My old repo remains dangling and is useless: https://atom.io/packages/language-orfeo

I cannot unpublish due to the git not found bug.

So, it possible, I would like language-orfeo erased from the database while I keep my new working repo.

This issue should be closed after.

@pelevesque
Copy link
Author

Actually, if language-orfeo could be save somehow I would still like to use it. Let me know if anything can be done.

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

No branches or pull requests

3 participants