Cocoapods 0.0.1 is broken.

[angelolloqui]

Cocoapod spec for 0.0.1 is pointing to a specific commit instead of a tag. For some reason (I guess a rebase and push forced) the commit has disappeared from the tree, and now any other podspec relying on this tool can not be installed. Please, update cocoapods to fix the 0.0.1.

[JoeKun]

Honestly, I don't even know how to use cocoapods. And I'm sorry but I don't have any time to figure it out. Whatever 0.0.1 was, it was probably awful anyway.

I strongly encourage you to upgrade to version 2.0.0 of FileMD5Hash, which is better in many ways, including ARC support.

If you know how to fix cocoapods to the tag I created for version 2.0.0, I would be grateful if you could do it on my behalf. I believe the FileMD5Hash.podspec file I left in the repository, present in the 2.0.0 tag, should do the trick. I just don't know how to "update cocoapods" as you said.

[angelolloqui]

I know how to fix it but I do not have permissions in CocoaPods so I have to "claim ownership" of your pod (I did already, lets see).
Anyway, the problem is not with 2.0.0 (which works ok) but with the 0.0.1, that is pointing to an inexistent commit. Besides, in 2.0.0 the API has changed, so existing code using the old API will not run. Any Pod that uses the old API is right now unusable :(

I propose to ditch the 0.0.1 (or fix it by creating a tag 0.0.1 that is stable enough), and add a 1.0.0 that preserves same API for existing pods.

[icodor]

how fix it?

[michaelgobbers]

I was able to fix this by changing the commit to 5e83f17 in the FileMD5Hash.podspec.json file.
angelolloqui as you have claimed ownership of the pod could you please include this fix? I understand that a webservice has to be used with new versions of the POD when you want to include it in the Specs repo? I suppose that a pull request with a fix would not be accepted when I read the Cocoa Trunk blog post.

[kyledecot]

I'm currently running into this as well. Any update?

[ryanmaxwell]

easiest fix like @michaelgobbers said is to change the commit if you still require (or are in my case using an older library which requires) v 0.0.1.

My process was to create a FileMD5Hash.podspec.json locally next to my Podfile, with contents

{
  "name": "FileMD5Hash",
  "version": "0.0.1",
  "license": "Apache",
  "summary": "Library for computing MD5 hashes of files with small memory usage.",
  "homepage": "http://www.joel.lopes-da-silva.com/2010/09/07/compute-md5-or-sha-hash-of-large-file-efficiently-on-ios-and-mac-os-x/",
  "authors": {
    "Joel Lopes Da Silva": "joel@lopes-da-silva.com"
  },
  "source": {
    "git": "https://github.com/JoeKun/FileMD5Hash.git",
    "commit": "6864c180c010ab4b0514ba5c025091e12ab01199"
  },
  "prefix_header_file": "Common/FileMD5Hash_Prefix.pch",
  "source_files": "Common/*.{h,c}",
  "requires_arc": false
}

then at the top of your podfile before the other dependencies

pod 'FileMD5Hash', :podspec => 'FileMD5Hash.podspec.json'

[mzgaljic]

@ryanmaxwell Thank you for this!! Really nice trick.