Re-publish package with capital name doesn't work

[Ethella]

I'm the owner of Magic-sdk package

published Magic-sdk first package https://github.com/CocoaPods/Specs/commit/940b9f21fd8313b274dbce3bb7f8b74588da1e3d Remove Magic-sdk the only package https://github.com/CocoaPods/Specs/commit/dc2e10cee54e4784dcc16884dd1d100d8f7f5eec

Try to publish with the same name with capital letters, and here's what I get:

$ pod trunk push Magic-SDK.podspec 
Updating spec repo `trunk`

CocoaPods 1.9.1 is available.
To update use: `sudo gem install cocoapods`

For more information, see https://blog.cocoapods.org and the CHANGELOG for this version at https://github.com/CocoaPods/CocoaPods/releases/tag/1.9.1

Validating podspec
 -> Magic-SDK (0.1.0)
    - NOTE  | xcodebuild:  note: Using new build system
    - NOTE  | [iOS] xcodebuild:  note: Planning build
    - NOTE  | [iOS] xcodebuild:  note: Constructing build description
    - NOTE  | [iOS] xcodebuild:  note: Execution policy exception registration failed and was skipped: Error Domain=NSPOSIXErrorDomain Code=1 "Operation not permitted" (in target 'Magic-SDK' from project 'Pods')
    - NOTE  | [iOS] xcodebuild:  note: Execution policy exception registration failed and was skipped: Error Domain=NSPOSIXErrorDomain Code=1 "Operation not permitted" (in target 'Pods-App' from project 'Pods')
    - NOTE  | [iOS] xcodebuild:  note: Execution policy exception registration failed and was skipped: Error Domain=NSPOSIXErrorDomain Code=1 "Operation not permitted" (in target 'App' from project 'App')
    - NOTE  | [iOS] xcodebuild:  warning: Skipping code signing because the target does not have an Info.plist file and one is not being generated automatically. (in target 'App' from project 'App')

[!] {"name"=>["is already taken"]}

Could anyone help me to completely remove the name from the registry? Much appreciated

Sorry for pinging unexpectedly @orta @dnkoutso

[orta]

We're open to well tested PRs which allow this to trunk

[Ethella]

@orta @dnkoutso Sorry, I'm not clear about what feature is needed. I would spend my effort on fixing this issue.

But please help me out, which feature shall I propose?

• Allow the owner to change the name of the package.
• Allow the owner to unpublish the package. Deregister the name from the database?
• Could I reset the name in the database?

[orta]

I don't remember the original discussions anymore as it was 5-6 years ago when we made this, but I'd be OK with existing authors publishing new versions of pods with the same case when all packages have been unpublished.

I'm very wary of allowing any case changing in pods because we support the local file systems as a database and that's bound to break something somewhere.