xmpp4r gem not building
Reported by Glenn Rempe | June 8th, 2008 @ 01:20 PM
The xmpp4r gem hosted in these two repo's does not seem to be building on GitHub. There is unfortunately still no way to debug the reason for failing builds on GitHub.
http://github.com/ln/xmpp4r/tree...
http://github.com/grempe/xmpp4r/...
It builds fine locally with:
gem build xmpp4r.gemspec
As this script runs without any exceptions (provided on gems.github.com):
http://github.com/grempe/xmpp4r/...
It has been in GitHub for several days and still no gem.
Can you help?
Thanks.
Comments and changes to this ticket
-
Glenn Rempe June 8th, 2008 @ 02:13 PM
FYI. The script I linked to above for testing my gemspec is actually now at:
-
Glenn Rempe June 9th, 2008 @ 12:28 PM
Just saw the blog post about 'Gem Builder Feedback'. Thats great. However, I still don't have a gem build for my project, nor do I have any feedback messages. In fact I got some additional errors today trying to install:
--
~/src/git/xmpp4r-grempe (master)\ > sudo gem install grempe-xmpp4r
Password:
Bulk updating Gem source index for: http://gems.rubyforge.org/
Updating metadata for 193 gems from http://gems.github.com/
.............................................................................................................................................................................Failed to download spec dyoder-autocode-0.9.8 from http://gems.github.com/:
Gem::RemoteFetcher::FetchError: bad response Not Found 404 reading http://gems.github.com/quick/dyo...
....Failed to download spec pluskid-rmmseg-cpp-0.2.1 from http://gems.github.com/:
Gem::RemoteFetcher::FetchError: bad response Not Found 404 reading http://gems.github.com/quick/plu...
.Failed to download spec carlosbrando-autotest-notification-0.0.5 from http://gems.github.com/:
Gem::RemoteFetcher::FetchError: bad response Not Found 404 reading http://gems.github.com/quick/car...
....Failed to download spec defunkt-ambition-0.5.3 from http://gems.github.com/:
Gem::RemoteFetcher::FetchError: bad response Not Found 404 reading http://gems.github.com/quick/def...
..Failed to download spec jbarnette-pastejour-1.0.3 from http://gems.github.com/:
Gem::RemoteFetcher::FetchError: bad response Not Found 404 reading http://gems.github.com/quick/jba...
Failed to download spec front-end-blender-0.8 from http://gems.github.com/:
Gem::RemoteFetcher::FetchError: bad response Not Found 404 reading http://gems.github.com/quick/fro...
...
complete
ERROR: could not find grempe-xmpp4r locally or in a repository
--
Do I need to push something to the repo to force a build with associated error report?
-
Glenn Rempe June 9th, 2008 @ 01:00 PM
FYI. I pushed a change to the README.rdoc file to try to trigger a gem build (or fail message). That was 25 minutes ago. Still no gem available. Still no message in my GitHub inbox. :-(
-
Glenn Rempe June 10th, 2008 @ 02:34 PM
24+ hours and still no gem built, and no error message in my github inbox. :-(
-
Glenn Rempe June 11th, 2008 @ 02:45 PM
OK. I just received my first error message from GitHub. Which is great. But its actually not so great since its not very helpful in resolving the issue.
--
github sent you a message 1 minute ago
[xmpp4r] Gem Build Failure
The gem build failed with the following error: Illegal operation
--
So as I stated above I have followed the directions found on gems.github.com and my build works locally with gem build and it seems to be fine when I run the testing script your provided.
Can you tell me what the 'illegal operation' is??
-
PJ Hyett June 12th, 2008 @ 05:52 PM
- → State changed from “new” to “invalid”
It means you're trying to execute external code, using code such as ``
-
Glenn Rempe June 12th, 2008 @ 05:55 PM
- → Assigned user changed from “” to “PJ Hyett”
No I am not 'trying to execute external code, using code such as ``'
http://github.com/grempe/xmpp4r/...
The closest thing I have to that is adding two strings together with a '+'
-
PJ Hyett June 13th, 2008 @ 05:33 PM
- → State changed from “invalid” to “hold”
I found a bug in our code, your gem should build correctly now. Let me know if it does not.
I apologize for the inconvenience.
-
Glenn Rempe June 21st, 2008 @ 03:26 PM
PJ.
It's working now. I appreciate your continuing the followup and the bugfix on your end. So what was the problem?
You can close this bug now as resolved.
-
PJ Hyett June 22nd, 2008 @ 10:15 AM
- → State changed from “hold” to “resolved”
There was a regular expression to disallow some of the most egregious code, but it was too strict and marked your code as a false positive.
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
