Proposal for Package naming : updating existing non-conform packages

Hi folks, Having read the proposal for Package naming and file naming (http://pear.php.net/pepr/pepr-proposal-show.php?id=55), I would like to know the procedure for updating an existing non-conform package, according to the defined rules, to get conformity. In fact, I would like to upload a new release for the Var_Dump class (PHP category), following the above rules : the package was previously released under the (non-conform) name "Var_Dump", but to match the defined rules in this RFC, the package should be named "PHP_Var_Dump". I tried to upload this new release using the web form, but this is not possible because I don't have permission to upload the release under the new name, so I would like to know how I can manage this : - use "New proposal" to propose the conform package, but in that case I'll be loosing the history for the Var_Dump package (releases, changelog...) - someone with karma rename the old package with the new name so I have the permissions to upload a new release conforming with the rules - ? Regards --------------------- Frederic Poeydomenge