Need help republishing package after repo delete/recreation

[coryforsythe]

Description

The repository backing atom-cfn was deleted and then re-created. Unfortunately this means it cannot be updated. Can you kindly unpublish atom-cfn so that I can re-publish it?

[rsese]

Sounds like the situation in #757 and #707? Did you already try unpublishing on your end?

[coryforsythe]

Correct. Please note the output of unpublish below:

`
$ apm unpublish
Are you sure you want to unpublish ALL VERSIONS of 'atom-cfn'? This will remove it from the apm registry, including download counts and stars, and this action is irreversible. (no)yes

Unpublishing atom-cfn ✗

Unpublishing failed: GitHub API returned error: NotFound
`

[rsese]

Thanks @coryforsythe 👍

@jasonrudolph, I think this is similar to what you described in #707 (comment) yes? But it looks like option 2 isn't working in this case - when you have a moment would you be able to confirm if option 1 is what's necessary here and if it is, update the package registry details (I asked Lee if he could take a look but it looks like he no longer has the admin powers to try and fix thing up anymore)?

[jasonrudolph]

@rsese: I looked into this issue, and here's what I'm seeing:

In atom.io, the atom-cfn package is associated with GitHub repository ID 81249477. That repository was owned by GitHub user ID 11410115 (with username coryforsythe). That user account (and all its repositories) was deleted by the user at 2017-12-02 13:17:24 -0500.

A new user account (GitHub user ID 34719930) with username coryforsythe was created at 2017-12-20 12:53:13 -0500. The user created a new repository (GitHub repository ID 145001053) named atom-cfn at 2018-08-16 10:41:56 -0400.

At this point, when someone attempts to perform any action on the atom-cfn package via apm, atom.io checks to see if the actor has permissions on repository 81249477 on github.com, but no such repository exists. This is why unpublishing doesn't work.

@rsese: I can think of two possible remedies in situations like this:

1. We can update the package registry so that the atom-cfn package points at the new github.com repository ID (145001053). If you want to go this route, let's pair on it so that we can raise our bus number. 😇

2. We can recommend that the user publish the package with a new package name.

As a longer-term solution, we could also consider teaching apm unpublish to unpublish the given package if the repository no longer exists on github.com.

[rsese]

If you want to go this route, let's pair on it so that we can raise our bus number. 😇

I'd loooove to do this 🚌 I'll reach out to you in chat to set something up and I'll followup here when this is resolved @coryforsythe (I'm also assuming that keeping the same package name is important for you).

[coryforsythe]

@rsese , Yes keeping the same name would be preferable if at all possible. I appreciate everyones' time looking into this. Looks like it sourced from my own actions with the add/drop of my GitHub account. Glad to have your help resolving it.

[rsese]

Hey @coryforsythe - just wanted to let you know that the team performed step 1 Jason described above. Can you go ahead and try publishing again and let us know if you have any trouble?

[coryforsythe]

@rsese - I'm getting a bit further but seeing an issue in tagging:

$ apm publish minor
  Preparing and tagging a new version ✓
  Pushing v1.1.0 tag ✓
  Publishing atom-cfn@v1.1.0 ✗
  Creating new version failed: Git tag not found

Could Creating new version failed: Git tag not found be indicative of something like issue #218?

[rsese]

Hmm, did you unpublish first? If not, can you try unpublishing and then publish again?

[coryforsythe]

@rsese I attempted to unpublish but am also encountering a (different) error:

$ apm unpublish
Are you sure you want to unpublish ALL VERSIONS of 'atom-cfn'? This will remove it from the apm registry, including download counts and stars, and this action is irreversible. (no)yes
Unpublishing atom-cfn ✗
Unpublishing failed: Unauthorized

I executed apm login once again to ensure I had the correct token. That does not appear to have helped.

[jasonrudolph]

@coryforsythe: It looks like the package was still associated with your old GitHub account (GitHub user ID 11410115, deleted at 2017-12-02 13:17:24 -0500). I've updated the package registry to associate the package with your new GitHub account (GitHub user ID 34719930, created at 2017-12-20 12:53:13 -0500). We had previously updated the package to point to the new repository, but given that you deleted your GitHub user account, we needed to update the user account information as well.

Can you try publishing again and let us know if you have any trouble?

[coryforsythe]

@jasonrudolph That did the trick! I was able to publish. Thank you.

[govindsaini616]

@rsese
i have same issue with my package "jspp". i have deleted my github account unfortunately and now i can't unable to unpublished package. i need to publish package with same name "jspp". please help..

[rsese]

Hi @govindsaini616 - can you open a new issue with the issue template filled out so we can track this? With the team's current workload and the holidays coming up, we can't promise a timeframe for when we can get to it, but creating a separate issue will be super helpful.

[rsese]

Oh I see that you emailed us about this issue @govindsaini616 - no need to open an issue now we'll just use that message for tracking.

[calebh]

@jasonrudolph

I need help with this same issue but for https://github.com/calebh/language-juniper
I would prefer not to loose the download count on the Atom plugin.