pod trunk push fails with "Git sources should specify a tag", even with --allow-warnings

[michaeltyson]

We have a Pod that comes from a dumb HTTP git repository, which does not support --depth.

From August, CocoaPods has added shallow fetching (--depth 1) to its git support, which breaks our Pod. As a workaround, I've replaced the ":tag" parameter with ":commit", to force CocoaPods to avoid the incompatible --depth parameter.

However, trying to push this fixed Pod results in the failure:

    - WARN  | [source] Git sources should specify a tag.
[!] The Pod Specification did not pass validation.

Trying to add the --allow-warnings param to pod trunk push makes no difference, even though the issue is a warning.

[segiddins]

Currently, trunk does not accept specs with warnings. In order to debug the issue with the downloader, we need to be able to play around with such a 'dumb HTTP git repository'.

[michaeltyson]

Certainly - the repository is http://developer.audiob.us/download/SDK.git

You'll need to make a (free) account at http://developer.audiob.us/register to get an email/password for access (this is a measure we take to ensure developers are using our system correctly).

Until then, do you have any thoughts on how I might proceed? Currently, the Pod is unusable.

[segiddins]

This is an issue with the downloader, and thus needs to be rectified over there. Can you provide me with credentials to access the repo? (my email is on my profile)

[michaeltyson]

Okay - I've registered you; you'll need to use the password reset facility to get a password (check your inbox).

Thank you!

[segiddins]

@fabiopelosin I'm going to look into doing something like http://stackoverflow.com/questions/9270488/is-it-possible-to-detect-whether-a-http-git-remote-is-smart-or-dumb in the downloader

[kylef]

We've made a fix for the dumb downloader.

Can you try updating the downloader and confirming the fix:

$ [sudo] gem install cocoapods-downloader

[ninjitaru]

Hi,

Is it possible to have option to manually remove --depth 1 using pod spec.
The repository that I have to work with is even more dumb.
It actually crash itself when --depth is used, which is a disaster
I tried query our repo's git Content-Type, which appear to be smart
Content-Type: application/x-git-upload-pack-advertisement
so there is something more wrong with our repo...

[segiddins]

Jason, please open up a new issue with some more details.

-Samuel E. Giddins

On Dec 19, 2014, at 6:14 AM, Jason Chang notifications@github.com wrote:

Hi,

Is it possible to have option to manually remove --depth 1 using pod spec.
The repository that I have to work with is even more dumb.
It actually crash itself when --depth is used, which is a disaster

—
Reply to this email directly or view it on GitHub.