Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to restore a deleted package? #100

Open
splendido opened this issue Jun 16, 2014 · 6 comments
Open

How to restore a deleted package? #100

splendido opened this issue Jun 16, 2014 · 6 comments

Comments

@splendido
Copy link

Hi all,
I've deleted a package as mentioned inside issue #53 hoping to re-publish it with a better version number (I made a mistake and started from 1.0.0 instead 0.1.0..)

Now I guess its field "deleted" is set to true and mrt release, despite apparently succesfully publishing it, is not enough to recover it.

The package name is accounts-meld
Can anyone help with this?
I'm sorry for the mess :-(

@tmeasday
Copy link
Member

Hmm. This is tricky as that package has a bunch of downloads. The idea is to not mess up people who are already depending on the package. I don't really know what to do here... Is there another name you could call the package?

@splendido
Copy link
Author

I know it was'n a good idea, not at all.
At the moment there were just a few people I know that were waiting for updates, since it was only a tentative 'pre release' (despite the version number).
...from issue #53 it seemed possible to republish a package (see post by michaelbishop), so I went for it :-(

If possible I'd like to keep the name, since I already have another dependent package building on the same prefix, accounts-meld-client-bootstrap, and similar names are already taken (e.g., accounts-merge, accounts-multi, ...).

I know it may a bit out of the rules but, is there any one who could access the mongo shell and 'restore' the package? Or even actually delete it?
I've already brought back to 1.1.0 the version number on the repo, I guess there will be no problems with it.

Many thanks,
Luca

@tmeasday
Copy link
Member

I can "undelete" it if you are happy to continue on from the 1.0 version number..

@splendido
Copy link
Author

At the moment, I'd say yes!
I still have to better understand what is the best versioning strategy (also considered that Meteor is still below 1.0.0), but the package now is in a stable and comes with a bunch of tests... so, in general, I guess that 1.1.0 could be fine.

If you could, that would be lovely!

@tmeasday
Copy link
Member

Done. Should propagate to new atmosphere soon.

I appreciate it's a bit annoying but I hope you can see why we are trying to be cautious here.

@splendido
Copy link
Author

Yes I see, and I think you're doing a great job!
I promise I'll never delete a package from now on, unless strictly necessary!

I guess something was changed since the discussion in the above cited issue, and I think it could be useful if you (ore someone else, but not me, definitely...) could add another post there saying it is no more possible to re-publish a package after it was deleted.
This would prevent people like me trying to hack their package's version number :-(
What do yo think?

Anyway, thanks for all! Sorry again

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

No branches or pull requests

2 participants