Can't publish package "origin" not git repo?


#1

I am getting this error, no idea why:

charizard:oceanic-next-syntax stevel$ apm publish minor
Preparing and tagging a new version ✓
Pushing v0.4.0 tag ✗
fatal: 'origin' does not appear to be a git repository
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

My repo is at https://github.com/smlombardi/oceanic-next-syntax

apm 0.137.0
npm 2.3.0
node 0.10.35
python 2.7.6
git 1.9.3
os 10.10.2


Can't publish package. Application error
#2

origin is the default name for the Git “remote” where you push your repository to. You can have any number of remotes, they just have to be uniquely named. You can get the list of remotes and to where they refer with the command: git remote -v. For example, with my tabs-to-spaces package:

$ g remote -v
origin	git@github.com:lee-dohm/tabs-to-spaces.git (fetch)
origin	git@github.com:lee-dohm/tabs-to-spaces.git (push)

apm assumes that your GitHub repository is at your origin remote.


#3

fixed that. thanks

but now I get

charizard:oceanic-next-syntax stevel$ apm publish minor
Preparing and tagging a new version ✓
Pushing v0.1.0 tag ✓
Publishing oceanic-next-syntax@v0.1.0 ✗
Creating new version failed: Application error

#4

I searched the forum , tried this to no avail:


#5

Why was it pushing v0.4.0 in the first output but now only v0.1.0 in the latest one? Looks like your tags are all messed up :frowning:


#6

OK. I deleted the repo on github.

I cleared out my git folder. To start over.

Created new local, new remote. Pushed to remote.

Set package.json to 0.0.0

Apm publish minor

charizard:oceanic-next-syntax stevel$ apm publish minor
Preparing and tagging a new version ✓
Pushing v0.8.0 tag ✓
Publishing oceanic-next-syntax@v0.8.0 ✗
Creating new version failed: Application error

I’m at a loss.


#7

You’re probably going to need @thedaniel to clean it up. Or you can start over completely with a new repo and new package name. There are tokens and things that have to stay in sync between the Atom Package API and the GitHub repo … which probably got messed up when you renamed or removed the GitHub repo. Since you removed the repo, I doubt there is anything you can do to fix this yourself now.


#8

I renamed my package, and it published successfully. Thanks @leedohm