How to remove packages from Atmosphere?

[zhouzhuojie]

After releasing a package on atmosphere, I realized that there is already a similar one there (though the old one is not compatible with Meteor 0.6.5+). How could I remove the package from Atmosphere?

I should have searched ahead, and issued a pull request to the author.

Thanks

The package name is: state-machine

[tmeasday]

Hey,

If you're confident no-one else is using your package, you can delete it with:

1. Log in at atmosphere.meteor.com
2. [In the browser console] Meteor.call('removePackage', 'name')

Cheers,
Tom

On Wednesday, 4 September 2013 at 6:36 AM, Zhuojie Zhou wrote:

After releasing a package on atmosphere, I realized that there is already a similar one there (though the old one is not compatible with Meteor 0.6.5+). How could I remove the package from Atmosphere?
I should have searched ahead, and issued a pull request to the author.
Thanks

—
Reply to this email directly or view it on GitHub (#53).

[Lepozepo]

Hi, I tried removing Amazon S3 File Uploader but I couldn't with this command. It's duplicated, I messed up when I pushed the first package I made.

[paralin]

@Lepozepo we see the duplicated package and have added enforcement of "no spaces" in names. I'm not sure if @tmeasday can manually delete it from the mongo db?

[tmeasday]

@Lepozepo you can delete it yourself if you head to atmosphere, and run the following the browser console:

Meteor.call('removePackage', 'name of package', function() { console.log(arguments); });

[Lepozepo]

@tmeasday I tried that and got a 404 on the console.

[tmeasday]

apologies! It's deletePackage

[Lepozepo]

Sweet! That worked, thanks!

[paralin]

To summarize:

Meteor.call('deletePackage', 'mypackage', function() { console.log(arguments); });

This is temporary until we find a better solution for fixing release errors and duplicates.

[michaelbishop]

I want to delete font-awesome-4 since there is a long standing version that is updated. It worked the first time and confirmed it was deleted. I just went back to check and it's back! Says it was updated 2 hours ago?! I tried to delete it again, but I get denied:

Meteor.call('deletePackage', 'font-awesome-4', function() { console.log(arguments); })
undefined
[undefined, "You're not authorized to delete this package"] 

I am logged in:

Meteor.user()
Object {_id: "yC7W9JnEzJGiqK5AP", username: "michaelbishop"}

What did I break? :-( Suggestions?

[Tarang]

The package font-awesome-4 belongs to @stephentcannon (as can be seen to the git repo its linked to). It looks like he forked it from you and republished it with his credentials.

This is why your name appears as an author and you can't remove it. He must have done this after you deleted it.

I'm thinking its not a good idea to actually moderate the packages because of reasons like this, if there are multiple packages its better to know which one people are using more.

Atmosphere v2 will use the rainbow graph to try and give an indication of what package a user should use. @zol & percolate made a really good decision here to do it this way instead.

[papayaah]

is there a way now to remove a package from atmosphere? i just published a package but unfortunately its not working and i'm not planning to continue it anymore.

[tmeasday]

Hi @mickeyren - there's a method in a similar vein to the addPackageMaintainer (https://atmosphere.meteor.com/wtf/maintain) called deletePackage. We don't advertise it as it's rare that it's a good idea, but it might be in your case.

[hugesuccess]

Hey guys. I created a new package on Atmosphere, but wanted the name lowercase instead of uppercase. When I updated the smart.json, it created a completely new package. Can you delete it? Thanks!!!!
delete me - https://atmospherejs.com/package/Famous

[tmeasday]

Hey. You can head to http://atmopshere.meteor.com/accounts and call Meteor.call('deletePackage', 'name'); on the browser console.

[hugesuccess]

Getting "There is no site deployed at this address." from that link :(

[zhouzhuojie]

You may want to try this one:

https://atmosphere.meteor.com/accounts

[hugesuccess]

Got to the page. Called the method from firebug. Got this result:

[undefined, "Package removed"]

But still two packages :(

https://atmospherejs.com/?q=Famous

[tsega]

I just update one of my packages to meteor's new packaging system. I accidentally renamed a package and published to atmosphere. I want to remove the newly created package since I've updated my main package already. How do I do it?

@tmeasday Tried your suggestion but I can't even login to my account. What to do?

[tmeasday]

Hi @tsega - there's not currently a way to "remove" packages in the new system.

We will see what comes from core on this one, we may add a way to hide them in the atmopsherejs.com UI.

[yogiben]

+1

[grigio]

+1

[yogiben]

meteor admin set-unmigrated yogiben:collection-modals is a workaround

[digilord]

I have done that with a package that I maintained for the 0.9.x-1.0 transition. It seems silly that you can't remove your own packages.

Can the admins remove packages?

[paralin]

@digilord It sounds like they would need to just edit them out of the database.

[matteodem]

I guess their motivation is that existing apps won't break if packages are not removed. Also when you're setting your package to unmigrated it won't be searchable and will only be directly useable with the meteor add command.

[albinekb]

+1

[Rathius]

+1

[dandv]

👍 CC @ekatek

[funkyeah]

+1 for being able to at least mark packages as "private" or "non-maintained".

There does not seem to be an officially supported way of forking and using someone else's package without suggesting you are the new maintainer on atmosphere. I suppose you can do a git clone into your packages directory and that whole dance but point me to the core approved way of doing that?!

[digilord]

@funkyeah I have forked and taken over a few packages since I started working with Meteor. There isn't a guideline to follow.

I usually contact the maintainer. If I don't get a response in a week I fork the package, make the fix, use it locally while I wait another week. If still no response I will publish the package under my credentials updating the version number.

[funkyeah]

@digilord so do you ever fork packages and use them by directly cloning into the packages directory or always publish back to atmosphere to use them

I still do think there should be an officially recommended way of forking and using packages without polluting atmosphere with packages from people that aren't willing to commit to being a maintainer

[digilord]

@funkyeah I have worked with people that want a specific change to a package that the maintainer is unwilling to make. Those end up as one off clones into a project.

[funkyeah]

cool and thanks!

[mstn]

I accidentally published a package I was working on. I flagged it using set-unmigrated, but it would be nice to delete it or mark it as private. Is there any news about this functionality?

[zol]

Can't be done due to MDG's packaging implementation.

[paralin]

Seems rather rediculous. Can't someone just write a little script to spam thousands of fake annoying packages on Atmosphere?

[zol]

@paralin sure :) You could take it up with MDG as they're responsible for this sort of backend functionality now.

[bobiblazeski]

+1

[day]

I too would love to "unpublish" a cloned package I published. I've done the set-unmigrated...but really it should just be removed.

[dandv]

Let's continue the discussion in the new Atmosphere repo?