Rename packages

[Vrtak-CZ]

Hi i need rename this packages:

From	To
http://packagist.org/packages/nella/nette-addon-diagnostics	nella/diagnostics
http://packagist.org/packages/nella/nette-addon-forms	nella/forms
http://packagist.org/packages/nella/nette-addon-media	nella/media
http://packagist.org/packages/nella/nette-addon-diagnostics	nella/diagnostics

[Seldaek]

You can delete them yourself (make sure you're logged in to see the delete button) and resubmit them with the new names.

[Vrtak-CZ]

This package http://packagist.org/packages/nella/nette-addon-doctrine does not have delete button.

[Seldaek]

Nope, it has too many downloads so it falls out of the user-deletable
category. I deleted it though, please resubmit.

[Vrtak-CZ]

Thx done

[dereuromark]

I have the same issue with 3 repos of mine (CakePHP plugins)

OLD:

https://packagist.org/packages/dereuromark/upgrade-cakephp
https://packagist.org/packages/dereuromark/setup-cakephp
https://packagist.org/packages/dereuromark/tools-cakephp

All 3 cannot be renamed or deleted

NEW:

https://packagist.org/packages/dereuromark/cakephp-upgrade
https://packagist.org/packages/dereuromark/cakephp-setup
https://packagist.org/packages/dereuromark/cakephp-tools

[dereuromark]

It would also be nice if the stats Overall: 1 419 installs etc would be kept - which a delete + new usually will not cover; I guess.
But more importantly, this needs to be working again.

@naderman @Seldaek Is one of you able to help me out here? Thanks.

[Seldaek]

@dereuromark you can now thanks to #421 mark packages deprecated. So you can let people know they should use the new ones. When everyone migrated and there are no more downloads in 30days I guess it's safe enough to delete the old ones (I can do that).

[dereuromark]

Wait.. it is still the same repo. Everything is the same - expect for the package name changed. And do the still open issue #47 I cannot rename it. Nor can I delete the wrong ones and add the right ones.
Is there no way to simple update the package name?

[Seldaek]

If you just update the package name, then anyone using the package is screwed, whenever they do an update they'll get a solver error. Right now two packages exist with the same repo, so that's cool anyone using either name will get the right code. If they see the deprecation note, they'll switch to the new name and then once everyone got that done we can safely delete the old name to clean things up.

[dereuromark]

It does not work properly, though

a) the github service hook for the new one does not get received when there is still an old one and both have the same github repo linked (probably the abondaned one still receives it)

b) The newly created ones cannot be downloaded with composer: "The requested package cakephp-opensearch could not be found in any version"

c) The old one also then stops working leaving it all in a huge mess where nothing works anymore: " The requested package upgrade-cakephp could not be found in any version"

[dereuromark]

How long does it need until the new package name is picked up?
Can this be sped up somehow?

The old package names not working anymore is a huge issue - and contradicts your "then anyone using the package is screwed". Seems like they already are screwed now.
Better to maybe remove all those right away or hard-correct the package name pretty quick.

I agree that this is quite an edge case - but I feel like this should be handled more gracefully.

[Seldaek]

Hm ok, a) is a known issue and I have to look into fixing it, b/c I'm not sure what's up, sounds wrong but could be something I haven't seen yet. Can you post exact repro steps in a new issue?

[Seldaek]

@dereuromark the problem in a) should now be fixed. b/c I can not reproduce. I can require dereuromark/cakephp-upgrade or dereuromark/upgrade-cakephp just fine here, and then switch, run a composer update and get the other one installed instead. Maybe it fails because you have some other libs installed that require dereuromark/upgrade-cakephp or something? Anyway if you can give me clear reproduce steps maybe I can look into it further.

[dereuromark]

Well, that was indeed partly the problem. If there is a dependency requiring the old one, they overwrite each other. But the main problem was the composer update issue (~ 5-10 min). During that time the packages are not (yet) available. So waiting for a while then resolved that "not found" issue.
Thanks for taking care of the other thing.

[TomasVotruba]

I didn't find any clear solution, just replacement workaround.
So, how to approach renaming nowadays?