qrush / gemcutter
- Source
- Commits
- Network (85)
- Issues (34)
- Wiki (10)
- Graphs
-
Branch:
master
-
I can't update a gem. This is the first time I have used gemcutter, so I have no idea where to look to find a solution.
$gem push vincenty-1.0.3.gem Enter your Gemcutter credentials. ...
Email: rob@burrowes.org
Password:
Signed in. Your api key has been stored in ~/.gem/credentials
Pushing gem to Gemcutter...
There was a problem saving your gem:The credentials file was created and matches the gemcutter copy.
I am the owner of the gem.$ gem owner vincenty Owners for gem: vincenty
- rob@burrowes.orgI am using gem version 1.3.5.
Comments
-
Hello,
I've added a delete rubygem feature, allowing a gem owner to delete it.
That's two commits :
http://github.com/dmathieu/gemcutter/commit/98332f331b847c03684806921cd22397274f4a05
http://github.com/dmathieu/gemcutter/commit/2b9bc88b8e7550cf41b960f90b650a58307d0411I'm open to any suggestion.
Comments
jtrupiano has been working hard on
gem yank, I would suggest checking that fork out. http://github.com/qrush/gemcutter/issues#issue/55 -
Can be possible edit home page link when we edit our project?
I do that "hacking" params but I think can be a good choice leave the people to do that in a "normal" way.
Super thanks!
Comments
The gemspec is your interface to the site. I'm trying to get all of the other links in the site (wiki, docs, etc) into the gemspec as well...you can push an updated version with your updated home page if need be.
Lipsiasoft
Wed Dec 16 06:19:45 -0800 2009
| link
A sorry, I forget to check my gemspec.
Thanks!
-
0 votes
Recovery of two gems i've created on Rubyforge with migration mistakes
1 comment Created 16 days ago by lecidHi, i want to correct the migration/push already made for my two own gem project on gemcutter
- Ldapmapper => from rubyforge
- cvstools => from rubyforge
please could you remove this two gems on GemCutter to permit me to re-push it myself.
Comments
Please email me directly at nick@gemcutter.org to resolve migration/ownership issues.
-
I've tried doing gem migrate monkeybars to port over Monkeybars. I've done this with and without the API key added. Both result in a 404 (the entire HTML is output to the terminal).
Tried this using Ruby 1.8.7 and jruby 1.5.0.dev.
Comments
LoganBarnett
Wed Dec 09 07:01:41 -0800 2009
| link
Forgot to mention, this is on gemcutter 0.2.0
LoganBarnett
Wed Dec 09 07:18:43 -0800 2009
| link
Thanks! It looks like I'll need that same help with Jemini and Rawr (two other gems I maintain).
-
PostgreSQL has a default log message level of notice which means each test run yields 10 or so lines of notices relating to table creation. I've added a min_messages of warning to cut down on the noise.
http://github.com/jpignata/gemcutter/tree/squelch_postgres_notices
Comments
-
Hey Nick,
As we discussed at RubyConf, we're (Gilt Groupe) are interested in running our own private Gemcutter install for internal packages. You expressed that you've had similar feedback from other people and we're planning on documenting that process.
Just creating this ticket to track that effort... If I end up getting to going through the install process before you get the docs, I'll try to keep notes to turn into a Wiki page.
Cheers,
-Bryan
Comments
I've started the instructions off here:
http://wiki.github.com/qrush/gemcutter/standup-your-own-gemcutter
I've asked the javagems.org guys to take a look at this and edit as they see fit, I'll have Tom Copeland take a look too. As always, if you need help feel free to hop into #gemcutter.
-
I hate having passwords/tokens in my config files.
1) Its in plain text and totally insecure
2) I can't publish my .gemrc file to my public dotfiles because it has sensitive informationI patched the gemcutter gemplugin thing to check the OS X keychain for your token. Its hard to write tests for since it mostly shells out to the security bin. Please test on your own system.
http://github.com/josh/gemcutter/commit/8d0dc28c4e02b02173408d1eb9f2009c35c65074
Comments
This would have to be merged into qrush/rubygems, and in there we're already storing the api key in ~/.gem/credentials. So, no better security wise but at least it's separated from the config file. I think you should lobby for this change with rubygems proper instead of here at gemcutter.
Yeah, i saw it.
I think it maybe better to use a gem wrapper instead. zenspider has a decent one. http://gemcutter.org/gems/osx_keychain
-
0 votes
3 comments Created about 1 month ago by itsnotvalidDashboard's "Latest updates" are not sorted in any meaningful mannerbugxScreenshot: http://flic.kr/p/7iBxmv
Description: As shown in the given screenshot, it is clear that the "newest item" is 19 days ago, while rails 2.3.5 was only released within 24 hours. This is nothing meaningful as it should be sorted by reserve chronological order.
Comments
Addressed this issue in the topic branch order_updates_by_built_at on my fork. Added a quick order on built_at to the named_scope used by the dashboards controller.
http://github.com/jpignata/gemcutter/tree/order_updates_by_built_at
-
I'm migrating all my gems to gemcutter but I found a problem.
I'm trying to migrate all gems(packages) of Brazilian Rails. Please look:
the project: http://rubyforge.org/projects/brazilian-rails/
and
error: http://gist.github.com/242377
Thanks
Comments
-
1 vote
gem migrate fails with differently named homepage
1 comment Created about 1 month ago by bernerdschaeferMy project/gem is called mail_builder, but it's rubyforge homepage is http://mailbuilder.rubyforge.org and I get the following error when running 'gem migrate mail_builder':
Starting migration of mail_builder from RubyForge... A migration token has been created. Uploading the migration token to mail_builder.rubyforge.org. Please enter your RubyForge login: Login: bernerdschaefer Password: There was a problem uploading your token: SCP did not finish successfully (1)
Perhaps "gem migrate" needs to check rubyforge to obtain the domain? For now I've changed the homepage URL and am waiting for it to propagate.
Comments
-
0 votes
Please nuke zentest (all lowercase!) from orbit
1 comment Created about 1 month ago by zenspider -
Where it says "version downloads" I'm confused every time I look at it. I'd prefer it to say simply "latest version" -- the word "download" can easily be inferred by the placement next to "total downloads".
Comments
-
0 votes
Errno::EPIPE: Broken pipe (http://gemcutter.org/gems/devise-0.5.5.gem)
1 comment Created about 1 month ago by billsaysthisGetting this FetchError when trying to install the Devise gem (OS X 10.5, rubygems up to date, ruby 1.8.7)
Comments
gemcutter master % gem fetch devise -Vv 0.5.5 GET 200 OK: http://gemcutter.org/specs.4.8.gz GET 200 OK: http://gemcutter.org/quick/Marshal.4.8/devise-0.5.5.gemspec.rz Downloading gem devise-0.5.5.gem GET 302 Found: http://gemcutter.org/gems/devise-0.5.5.gem GET 200 OK: http://s3.amazonaws.com/gemcutter_production/gems/devise-0.5.5.gem Downloaded devise-0.5.5
That just worked for me on Ubuntu...gonna say this is a non-issue. If it's still not working let me know!
-
Hello,
This gem does not seem to have been imported correctly from rubyforge:
http://gemcutter.org/gems/rumai
It shows an error page saying "Server error. No Stairway, denied!"
All of my other gems were imported from rubyforge successfully.
Thanks.
Comments
Hi Suraj -
Hm, one of that gem's development dependencies got created without a rubygem to point to. It's Dependency id 164305 in our database... rubygem_id is nil, so the view is blowing up when it tries to render that page.
I'm not sure of the best way to clean this up; you might want to hop in #gemcutter on freenode and ask qrush or ddollar.
Yours,
Tom
Hi Suraj -
Nick showed me how to troubleshoot this. You do "gem spec rumai -r", that shows you the dependencies, and I saw this:
dependencies:
- !ruby/object:Gem::Dependency name: :dfect type: :development version_requirement: version_requirements: !ruby/object:Gem::Requirementrequirements: - - ">=" - !ruby/object:Gem::Version version: "0" version:I bet that name of ":dfect" is causing the problem... probably it should just be "dfect"?
Yours,
Tom
It should work now, please use a string instead of a symbol to describe your dependencies in your gemspec. We'll be building in better validation for this, but just for a heads up if we don't fix it before you push a new version.
-
3 votes
3 comments Created about 1 month ago by robgleesonFeedback/comment feature for gemsfeaturexHi,
I am wondering would there be any plans in the future to enable feedback comments on a gem? I know github exists - and most projects link to a github repoistory where you can post issues but that seems to be a "report a problem" feature rather then a "feedback" feature.
I'm thinking for comments that may be like:
"I liked this gem because...."
"I disliked this gem because..."
"Thanks for this gem!"
Personally - I'd like feedback because I see a good few people have downloaded my gem but i don't know what their opinion of the gem actually is. They haven't filed any issues on github, but i've no idea of what they actually think of it.
Thanks,
Rob
Comments
This would be a really nice addition, for both the maintainers of the gem and possible new users to get latest information and help about common problems as well.
Let's just use http://www.ruby-toolbox.com/ instead right now for this kind of thing. I don't want Gemcutter turning into a unsupported forum, and I'm sure gem authors would prefer discussion/problems posted on places they specify instead. Feel free to convince me otherwise.
robgleeson
Mon Nov 23 01:32:37 -0800 2009
| link
qrush,
You're the boss :-) As a gem author, I'd love to get some kind of feedback and that feedback isn't being directed at the github issue tracker - people seem to reserve using that for bugs, but the decision rests with you. I don't have any argument other then the one i put forward in my first post.
-
0 votes
3 comments Created about 1 month ago by scrum8bad response Internal Server Error 500 when fetching gems using bundlerbugxSometimes I get bad response error when fetching gems using bundler from gemcutter:
ERROR: While executing gem ... (Gem::RemoteFetcher::FetchError)
bad response Internal Server Error 500 (http://gemcutter.org/quick/Marshal.4.8/camcapture-0.1.0.gemspec.rz)When I go hit that address from the browser, I also get error 500
Comments
This sounds like a platform issue. Can you try doing @gem install -V@ and paste the output? Also, what is your gem platform? Paste the platform stuff from @gem env@ output too.
This is the output of gem env:
` RubyGems Environment:
- RUBYGEMS VERSION: 1.3.5 - RUBY VERSION: 1.9.2 (2009-11-13 patchlevel -1) [i686-linux] - INSTALLATION DIRECTORY: /usr/local/lib/ruby/gems/1.9.1 - RUBY EXECUTABLE: /usr/local/bin/ruby - EXECUTABLE DIRECTORY: /usr/local/bin - RUBYGEMS PLATFORMS:- ruby - x86-linux- GEM PATHS:
- /usr/local/lib/ruby/gems/1.9.1
- /home/jpartogi/.gem/ruby/1.9.1
- GEM CONFIGURATION:
- :update_sources => true
- :verbose => true
- :benchmark => false
- :backtrace => false
- :bulk_threshold => 1000
- :sources => ["http://gemcutter.org", "http://gems.rubyforge.org/", "http://gems.github.com"]
- REMOTE SOURCES:
Major refactoring of the Hostess (our gem server) has fixed this issue.
$ curl -i http://gemcutter.org/quick/Marshal.4.8/cucumber-screenshot-0.1.0.gemspec.rz HTTP/1.1 403 Forbidden Date: Sun, 06 Dec 2009 06:36:05 GMT Server: Apache/2.2.3 (Red Hat) mod_ssl/2.2.3 OpenSSL/0.9.8e-fips-rhel5 Phusion_Passenger/2.2.5 X-Powered-By: Phusion Passenger (mod_rails/mod_rack) 2.2.5 X-Rack-Cache: miss Content-Length: 32 Status: 403 Content-Type: application/x-deflate This gemspec could not be found.%
- GEM PATHS:
-
I would prefer to keep ~/.gemrc version in my (public) dotfiles repository, but can't do it anymore because gemcutter stores the gemcutter_key there.
What do you think about storing this in ~/.gemcutter instead? Would also pave the way if gemcutter wanted to add more stored config without polluting or conflicting with RubyGems as well.
Thoughts?
Cheers,
-Bryan
Comments
-
I find it useful to make a build available publicly to assist those who are contributing to the project. This simple patch adds the field to the linksets table and exposes it in the UI.
Patch: http://github.com/brynary/gemcutter/commit/046c8f5772c8a68575a4c9128bd17cf99591cb95
Comments
There was some talk about moving this kind of thing into the gemspec. Going to hold off until that's figured out for sure.
-
$ ruby -v Now Running: ruby 1.9.1p243 (2009-07-16 revision 24175) [i386-darwin10] $ gem owner sitemap_generator --add xxx@gmail.com ERROR: While executing gem ... (TypeError) can't dup Symbol $ chruby Now Running: ruby 1.8.7 (2008-08-11 patchlevel 72) [universal-darwin10.0] $ gem owner sitemap_generator --add xxx@gmail.com Added owner: xxx@gmail.com Owners for gem: sitemap_generator - xxx@gmail.com - xxxx@gmail.comThanks,
Comments
Hmm, that's not good. can you run gem owner --debug in 1.9.1 and gist/paste that backtrace?
adamsalter
Sun Nov 08 17:36:04 -0800 2009
| link
gem owner sitemap_generator --add xxx@gmail.com --debug Exception `OptionParser::InvalidOption' at /opt/local/lib/ruby1.9/1.9.1/optparse.rb:1453 - invalid option: no-rdoc Exception `OptionParser::InvalidOption' at /opt/local/lib/ruby1.9/1.9.1/optparse.rb:1267 - invalid option: --no-rdoc Exception `OptionParser::InvalidOption' at /opt/local/lib/ruby1.9/1.9.1/optparse.rb:1453 - invalid option: no-ri Exception `OptionParser::InvalidOption' at /opt/local/lib/ruby1.9/1.9.1/optparse.rb:1267 - invalid option: --no-ri Exception `TypeError' at /opt/local/lib/ruby1.9/1.9.1/net/http.rb:1529 - can't dup Symbol ERROR: While executing gem ... (TypeError) can't dup Symbol /opt/local/lib/ruby1.9/1.9.1/net/http.rb:1529:in `dup' /opt/local/lib/ruby1.9/1.9.1/net/http.rb:1529:in `urlencode' /opt/local/lib/ruby1.9/1.9.1/net/http.rb:1524:in `block in encode_kvpair' /opt/local/lib/ruby1.9/1.9.1/net/http.rb:1524:in `map' /opt/local/lib/ruby1.9/1.9.1/net/http.rb:1524:in `encode_kvpair' /opt/local/lib/ruby1.9/1.9.1/net/http.rb:1517:in `block in set_form_data' /opt/local/lib/ruby1.9/1.9.1/net/http.rb:1517:in `each' /opt/local/lib/ruby1.9/1.9.1/net/http.rb:1517:in `map' /opt/local/lib/ruby1.9/1.9.1/net/http.rb:1517:in `set_form_data' /Users/adam/.gem/ruby/1.9.1/gems/gemcutter-0.1.6/lib/commands/owner.rb:31:in `block (2 levels) in add_owners' /Users/adam/.gem/ruby/1.9.1/gems/gemcutter-0.1.6/lib/commands/abstract_command.rb:70:in `make_request' /Users/adam/.gem/ruby/1.9.1/gems/gemcutter-0.1.6/lib/commands/owner.rb:30:in `block in add_owners' /Users/adam/.gem/ruby/1.9.1/gems/gemcutter-0.1.6/lib/commands/owner.rb:29:in `each' /Users/adam/.gem/ruby/1.9.1/gems/gemcutter-0.1.6/lib/commands/owner.rb:29:in `add_owners' /Users/adam/.gem/ruby/1.9.1/gems/gemcutter-0.1.6/lib/commands/owner.rb:23:in `execute' /opt/local/lib/ruby1.9/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/command.rb:257:in `invoke' /opt/local/lib/ruby1.9/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/command_manager.rb:132:in `process_args' /opt/local/lib/ruby1.9/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/command_manager.rb:102:in `run' /opt/local/lib/ruby1.9/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/gem_runner.rb:58:in `run' /opt/local/bin/gem:21:in `<main>' -
3 votes
4 comments Created about 1 month ago by floriuninitialized constant Gem::AbstractCommand::Netbugx(flori@macro:foo 1)$ gem push --backtrace pkg/foo-6.6.6.gem ERROR: While executing gem ... (NameError)
uninitialized constant Gem::AbstractCommand::Net /usr/lib/ruby/gems/1.8/gems/gemcutter-0.1.6/lib/commands/abstract_command.rb:76:in `use_proxy!' /usr/lib/ruby/gems/1.8/gems/gemcutter-0.1.6/lib/commands/abstract_command.rb:17:in `setup' /usr/lib/ruby/gems/1.8/gems/gemcutter-0.1.6/lib/commands/push.rb:21:in `execute' /usr/lib/ruby/site_ruby/1.8/rubygems/command.rb:257:in `invoke' /usr/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:132:in `process_args' /usr/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:102:in `run' /usr/lib/ruby/site_ruby/1.8/rubygems/gem_runner.rb:58:in `run' /usr/bin/gem:21Comments
Hmm, that's not good...does it work without a proxy configured?
Also, the gemcutter gem is being merged into RubyGems proper, so hopefully this kind of thing will be going away soonly.
I'm seeing the same error on 0.1.7 when using a proxy. It's fine without.
Same error for me.
Quick workaround is to write in your .gemrc:gem: --no-http-proxy
-
1 vote
3 comments Created about 1 month ago by sunaku[PATCH] preserve whitespace in gem descriptiondesignxHello,
Gem descriptions have traditionally been assumed to be plain-text (pre-formatted with linebreaks). However, gemcutter is displaying them as simple HTML paragraphs --- thereby omitting all pre-formatting.
For example, consider Allgems display versus Gemcutter display.
The patch for this problem is simple:
.main .info #markup p { font-size: 1.4em; white-space: pre; /* add this line! */ font-family: monospace; /* add this line! */ }In addition, it would be useful if you can convert bare URLs in the gem description into hyperlinks, just like GitHub does for README files.
Thanks for your consideration.
Comments
We're going to have readmes on the site (soon, i hope) so I don't want to encourage putting any more text/data into the gemspec's description or summary than necessary.
That seems like a reasonable alternative. Let's close this issue once that feature is released.
Nick, you might also want to consider the gemspec example on page 260 of Pickaxe v3:
s.description= File.read(File.join(File.dirname(__FILE__), 'README'))That example encourages the behavior of putting project information / release notes into the gem description. Cheers.
-
Maybe I'm missing something, but I looked hard and multiple times: there seems to be no direct link to download the Gems as a .gem file.
I know more than one person that has to do manual downloading due to company policy and would be real happy about this. (I once was one of them :/)
Comments
This should definitely be added. The crate gem requires you to add the upstream_source and its current example refers to ruby forge.
thewoolleyman
Thu Dec 10 11:26:20 -0800 2009
| link
Anyone working on this yet? If not, I may try to tackle it...
My attempt:
http://github.com/andhapp/gemcutter/tree/feature-116Please comment.
Merged in andhapp's work with some slight modifications. Thanks!
-
The RubyGems.org move means the homepage could use a bit of shuffling around. Here's a small list of what I'd like to see:
- Lessen the install instructions' importance (ready, set, go). They'll now just need to know:
gem update --system,gem push yourgem-0.0.0.gem - Some space to show conferences/events like discussed long ago would be awesome
- We can now track downloads as they come in, so that's another interesting bit of content we could show along with most downloaded, just updated, and new gems.
Comments
Here's a horrible mockup of what I was thinking of:
http://gomockingbird.com/mockingbird/index.html?project=6c7dcf43bdd582706779b2481d52e170618a55bd
- Lessen the install instructions' importance (ready, set, go). They'll now just need to know:
-
We're becoming "RubyGems.org: your community gem host". The logo could use a bit of rework for this.
Comments
-
We're becoming "RubyGems.org: your community gem host". The logo could use a bit of rework for this.
Comments
Done: http://gemcutter.org/images/rubygems.png
Just waiting on the RubyGems team now.
-
0 votes
Can't migrate gems which are just packages of another project
5 comments Created about 1 month ago by wincentExample case:
My Walrus gem has already been successfully migrated with a basic "gem migrate walrus"; note that I have ownership of it:
http://gemcutter.org/gems/walrus
But note that there is another gem (wopen3) which is a package within the Walrus project rather than being a separate project.
http://rubyforge.org/projects/walrus/
"gem migrate wopen3" doesn't work in this case, failing thusly:
There was a problem uploading your token: SCP did not finish successfully (1) Asking Gemcutter to verify the upload... Gemcutter is still looking for your migration token.Any way to finish the migration? At the moment the gem is ownerless on the Gemcutter site, and I evidently can't push new versions:
Comments
Ok, reading here:
http://gemcutter.org/pages/gem_docs
That the migration process "works by looking at the rubyforge_project from your gemspec". The wopen3 gem doesn't have such a setting; perhaps I need to add a:
s.rubyforge_project = 'walrus'to the gem specification...
I just approved your ownership over wopen3, you should be all set.
Perhaps this is a "bug" then in the sense that the error message provided by Gemcutter is a bit misleading.
curl http://gemcutter.org/gems/wopen3.jsonShows that the rubyforge_project setting is nil:
{"downloads":2,"name":"wopen3","authors":"Wincent Colaiuta","version":"0.1","rubyforge_project":null, ...So perhaps instead of "SCP did not finish successfully" a better error message might be "rubyforge_project missing from Gem specification; cannot upload" or similar.
-
The .gemrc might not be the best place for the API key. Some folks (myself included) store this file in public git repos. Even for those that don't, it seems prudent to separate this sensitive bit from the non-sensitive config stuff. Perhaps a .gemcutter file?
Comments
-
Given I am a user
And I search for the paperclip gem
Then I should not see a URL like this - http://gemcutter.org/search?query=paperclip&commit=SearchThe "commit=Search" bit is going to keep me up at night.
Comments
I guess it really never bothered me, but if you can figure out a way for Rails not to dump that into the querystring I'm all for it.
mjankowski
Thu Oct 29 13:35:40 -0700 2009
| link
I think this works...
<%= submit_tag 'Search', :name => nil %>
Just sent a pull request... although a minor thing it does look shabby.
mjankowski
Sun Nov 22 12:04:06 -0800 2009
| link
An incredible weight has been lifted from our collective shoulders.
-
1 vote
This patch fixed the problem for me: flori/gemcutter@9824043
Comments
We can't bring the requires for that out since RubyGems will try to load that for everything.
gem migratewill be going away for the rubygems.org transition so I have to say no to this one, sorry.Well, I have migrated all my gems now, but maybe other people haven't yet.
How about this patch instead? -> flori/gemcutter@872d9b0 -
The generate_api_key method in app/models/user.rb creates a user's API key based only on email address and time of generation. This dramatically reduces the search space necessary for a brute-force search to guess a user's key. A better approach would be to utilize ActiveSupport::SecureRandom or similar to generate the key using entropy gathered from /dev/urandom. The key would then actually have 128 bits of entropy as expected.
Comments
Good deal :) I implemented API key generation using SecureRandom, and a test to go along with it. chriskite/gemcutter/tree/random_api_key
What's the point of the
rescue? I don't really think it's necessary.SecureRandom.hex will raise a NotImplementedError exception if there is an error reading random data from /dev/urandom. Since that should never happen in production, maybe you'd prefer to log the error?
Yeah, just we'll let hoptoad catch it if it happens. that's truly an exceptional case :)
-
0 votes
1 comment Created 2 months ago by djberg96Gemcutter displays wrong version when no "base" gem@ddollarxAs of version 0.9.0, the sys-proctable gem does not have a "base" version. All versions of the gem are platform gems (because every platform does things differently).
However, if you look at http://www.gemcutter.org/gems/sys-proctable, you'll see the base version as 0.7.6. This should be 0.9.0. In other words, if no "base" version is found, it should stub out the latest platform specific version somehow.
Comments
-
Ruby 1.8.7, Snow Leopard, rubygems 1.3.5:
This error crops up from time to time. It seems to be intermittent:
dberger@globe-madison ~>gem migrate win32-nio --debug Exception `LoadError' at /usr/local/lib/ruby/site_ruby/1.8/rubygems/ custom_require.rb:31 - no such file to load -- json/pure Using pure library for JSON. Starting migration of win32-nio from RubyForge... A migration token has been created. Exception `LoadError' at /usr/local/lib/ruby/site_ruby/1.8/rubygems/ custom_require.rb:31 - no such file to load -- Win32API Exception `LoadError' at /usr/local/lib/ruby/site_ruby/1.8/rubygems/ custom_require.rb:38 - no such file to load -- Win32API Exception `LoadError' at /usr/local/lib/ruby/site_ruby/1.8/rubygems/ custom_require.rb:31 - no such file to load -- net/scp Exception `LoadError' at /usr/local/lib/ruby/site_ruby/1.8/rubygems/ custom_require.rb:31 - no such file to load -- highline Exception `LoadError' at /usr/local/lib/ruby/site_ruby/1.8/rubygems/ custom_require.rb:31 - no such file to load -- Win32API Exception `LoadError' at /usr/local/lib/ruby/site_ruby/1.8/rubygems/ custom_require.rb:38 - no such file to load -- Win32API Exception `LoadError' at /usr/local/lib/ruby/site_ruby/1.8/rubygems/ custom_require.rb:31 - no such file to load -- termios Exception `LoadError' at /usr/local/lib/ruby/site_ruby/1.8/rubygems/ custom_require.rb:38 - no such file to load -- termios Uploading the migration token to Win32Utils.rubyforge.org. Please enter your RubyForge login: Login: djberg96 Password: Exception `Net::SSH::Exception' at /usr/local/lib/ruby/gems/1.8/gems/ net-ssh-2.0.15/lib/net/ssh/transport/algorithms.rb:296 - could not settle on language_client algorithm Exception `Net::SSH::Exception' at /usr/local/lib/ruby/gems/1.8/gems/ net-ssh-2.0.15/lib/net/ssh/transport/algorithms.rb:296 - could not settle on language_server algorithm Exception `RuntimeError' at /usr/local/lib/ruby/gems/1.8/gems/net- scp-1.0.2/lib/net/scp.rb:384 - scp: /var/www/gforge-projects/ Win32Utils/migrate-win32-nio.html: No such file or directory Exception `Net::SCP::Error' at /usr/local/lib/ruby/gems/1.8/gems/net- scp-1.0.2/lib/net/scp.rb:351 - SCP did not finish successfully (1) There was a problem uploading your token: SCP did not finish successfully (1) Asking Gemcutter to verify the upload... Gemcutter is still looking for your migration token. removing /var/folders/wF/wFJ3R9sfFgCrHQbWYrM+G++++TM/-Tmp-/ token20091012-33187-hqdcan-0...done
Comments
-
Comments
Addressed this issue in the topic branch show_platform_in_version_title on my fork. Added some the platform to the view if one is specified and a cucumber feature to test this functionality.
http://github.com/jpignata/gemcutter/tree/show_platform_in_version_title
jpignata: this patch isn't passing the tests off the latest master. could you take another look at it? also, please use spaces instead of tabs (git log -p your commit to see it) thanks!
qrush: Ah, okay - I've fixed the tab issue and the intermittent test failures which were due to timing. I've amended my commit and pushed my changes to my remote branch. Let me know if this one fails (but, er, hopefully not.)
-
2 votes
7 comments Created 2 months ago by levinalexsearch should priorize exact match on gem namefeaturexsearching for a gem that has a common name (like ahowards
main) shows many unrelated results and pushes the correct result to the second page. (example)If there is an exact match in the gem name this gem should appear at the very top of the result list
Comments
Agreed. Anything to make the search nicer is fine. I also think it should sort and show the number of downloads for a gem.
What about breaking an exact match out above the rest of the results with possibly a bit more info/prominence?
We gave this a shot. This branch highlights exact search results and orders by downloads (and cleans up the URL to boot).
This is pretty much the same approach I took as well but I added a #search_exact method to the model. Scenarios, tests and code here:
http://github.com/npverni/gemcutter/commit/0fe35fef12ce15c32b04b46877a14066352d5a85
-
0 votes
2 comments Created 2 months ago by djberg96Gem name displayed shows platform specific gembugxIf you take a look at http://gemcutter.org/gems/ptools you'll see that it displays "1.1.8-x86-mswin32-60", because the Windows specific gem happened to be the last one uploaded I guess.
But I just want it to display "1.1.8". Shouldn't it just use Gem::Specification#version ?
Comments
-
I cannot install RedCloth gem. Is it something to do with the capital letters? All other gems are working fine.
gem install RedCloth --source http://gemcutter.org ERROR: could not find gem RedCloth locally or in a repositoryI'm on OS X (Snow Leopard)
Comments
Looks like you found a bug. gem fetch RedCloth works, so you can do that and then install the .gem for now until we figure this out.
-
0 votes
3 comments Created 2 months ago by carljmgem push fails with LoadError on Ubuntu: no net/httpsbugxJust logging this here for reference (maybe it could go in a FAQ or something)? On an Ubuntu system, "gem push" results in a LoadError traceback, unable to find net/https. The solution is to "apt-get install libopenssl-ruby1.8"
Comments
That sucks. I think a new 'troubleshooting' page is necessary.
Yah. Guess I should be clear and say I'm seeing this on Ubuntu 8.04 Hardy, which is fairly old; dunno if it's the same on newer Ubuntus.
Added to the new help page: http://wiki.github.com/qrush/gemcutter/help
-
If for some reason a user doesn't receive an activation email after signing up, they are at a bit of a dead end.
There should be an option somewhere on the log-in form to resend the activation email. If a user tries to log into their unactivated account, they should also see a message saying they aren't activated and should be presented with the resend link - currently it just returns to the login form without any indication of what happened.
Comments
robbyrussell
Fri Oct 09 09:44:52 -0700 2009
| link
This is regarding my attempt to sign-up. After I put in my email/password to create an account, I got a blank page at /users. (not sure what happened here)
No response... and when I tried it again, it said that my email address was already taken. It's been about 20 minutes and I haven't received a confirmation email and when I try to use the, "forgot password" feature, it just reloads the form without giving me any response.
I used the email address: robby@planetargon.com
Thanks in advance!
>> User.find_by_email("robby@planetargon.com") => nilThis sounds like a bug with clearance. Perhaps try it again?
-
0 votes
3 comments Created 2 months ago by jasonmgemcutter_key inserted into .gemrc without proper formatbacklogxAfter gem tumble, I see this:
$ cat ~/.gemrc
:benchmark: false gemcutter_key: OH-NOES-SECRETS
:backtrace: false :update_sources: true :verbose: true :bulk_threshold: 1000 :sources: - http://gemcutter.org - http://gems.rubyforge.org/ - http://gems.github.comShouldn't there be a colon before gemcutter_key?
Comments
lukeredpath
Fri Oct 09 09:20:44 -0700 2009
| link
For consistency, perhaps, but it just means the API key is keyed on a string rather than a symbol so techniaclly speaking I couldn't call this a bug, its not that big a deal.
I originally tried to make this work as a symbol, but it requires some hacking onto Gem::ConfigFile. If you can make it work in the symbol syntax I'd be willing to switch to it.
http://github.com/jbarnette/rubygems/blob/master/lib/rubygems/config_file.rb
-
Have a sensible default for the root gem source too.
Comments
-
A "%" in the search parameter leads to an "Heroku Error" ("Oops, we seem to have a glitch in our system.")
Comments
-
1 vote
5 comments Created 2 months ago by copiousfreetimeReview 'push' rake task contributionbacklogxSorry about the noise, I sent a pull request before reading the contributions section of the readme.
Its commit copiousfreetime/gemcutter@af083d0 and a follow up commit copiousfreetime/gemcutter@f5a02d1 to fix the documentation
Comments
I think I'd rather leave this up to package management solutions like Jeweler. I'd like to hear your argument why gem owners shouldn't use one of the accepted solutions that already exist like that or Hoe.
copiousfreetime
Sun Oct 04 18:28:06 -0700 2009
| link
I'm all for using package management solutions. I was thinking this would be for them to use. I made the task because it appears Jeweler may be the only one that has a gemcutter task right now and I do not use Jeweler.
I think its appropriate to have something that would potentially be used quite a bit via a rake task to provide either a sample, or a common rake task to do the job. rcov, rspec and rubygems all provide rake tasks.
Also, part of it is allowing PushCommand#send_gem to have a parameter. Otherwise, it appears the only way to use the push command is to shell out to execute it.
I'm not set on having this accepted, I just thought it would be appropriate to offer it.
copiousfreetime
Mon Nov 09 12:28:03 -0800 2009
| link
Sounds good. Any thoughts on just the PushCommand#send_gem() bit?, that allows for pushing the gem via ruby API instead of requiring a commandline invocation.
-
0 votes
4 comments Created 2 months ago by koraktorSmall UI change: Gem summaries as link titlesfeaturexComments
Getting a bit of a failure when trying this out, silly me, I didn't run the tests before committing: http://runcoderun.com/qrush/gemcutter/builds/4bd167829aaf5fee9c00ceffc47259cb8b8a9da0/2/ruby_186
Patch this up with some tests and I'll get it merged and deployed.
Uh, I'm sorry for not testing this one. Never thought that
RubyGem#versions.latestcould benil. Still new to your code. ;)I'll fix this once I'm at home.
Didn't miss anything in your code, just didn't take a look at how the tests generate the gems and versions. :)
Amended updated tests at http://github.com/koraktor/gemcutter/commit/d00a5febda95a86dad8c3ff3dc9b2dbf50934d9d
Once again sorry for any inconvenience.
-
Start tracking which versions of what are downloaded. Also, it would be awesome to get real time data for http://gemcutter.org/stats, for example, see the latest gems downloaded. Perhaps we can just dump the latest gems downloaded into memcached? Or even use memcached as the store and have cron back that up to a table.
It would also be sweet to start tracking total downloads over time. Start an hourly cron job to save that and the date and whip up some sweet graph for the stats page.
Comments
-
I added a OpenSearch description file and the fitting
<link>tag in http://github.com/koraktor/gemcutter/commit/402ed1a44fde4fc239317370a61e0f870bf6e9dbComments
-
Comments
-
$ gem tumble
ERROR: While executing gem ... (RuntimeError)
Unknown command tumble
Comments
harukizaemon
Wed Sep 30 03:23:19 -0700 2009
| link
D'oh! Needed to: gem update --system
Yeah, I think the install message could be clearer though about this.
-
0 votes
3 comments Created 3 months ago by koraktorUI inconsistency in RubygemsController#indexbugx/gemsshowsall gems starting with abut
/gems?letter=Ashowsall gems starting with AI added some consistency tweaks, so that
param[:letter]defaults to 'A' and letter is upcased if it's only a single character.http://github.com/koraktor/gemcutter/commit/b6306e1cc73ee9640a1a6579dbb7de69d316b698
Comments
I'm fine with this change, but I definitely want to see some tests for it. Add some into the RubygemsControllerTest and you can consider this merged.
Updated my commit with tests.
http://github.com/koraktor/gemcutter/commit/7bd8c1776018ccd7095cba018f310a8a77c2c5b9
-
Trying to run a clone of gemcutter with
script/serverresulted in the following error:=> Booting Mongrel => Rails 2.3.4 application starting on http://0.0.0.0:3000 no such file to load -- xmlsimpleThe solution was to install the
xml-simplegem - so I think this should be included invendor/gemstoo.Comments
-
Checking out the new gemcutter design I noticed that the gems are not sorted lexicographically once a starting letter is chosen. E.g., I see "strophe_ruby, sys-admin, sqlite-ruby" in that order. It makes it hard to figure out on what page a gem should appear.
Comments
-
The three columns on the main page don't push their container down if they are tall:
http://skitch.com/jasonmorrison/nypiq/gemcutter-awesome-gem-hosting
Comments
-
0 votes
1 comment Created 3 months ago by qrushNew gems shouldn't show up in the updated gems list.bugxAs seen on: http://staging.gemcutter.org
Comments
-
0 votes
1 comment Created 3 months ago by qrush@ddollarxDisplay issue when a gem doesn't have an authordesignxComments
-
0 votes
1 comment Created 3 months ago by epitronChrome has problems selecting the "gem install ..." linebacklogxWhen you're on a gem's homepage, and you try to select the "gem install..." line by hand, selecting the edge of the word "gem" will select all of the rest of the page.
It appears that the " > " element is overlapping the "gem install..." element.
The " > " image definitely has a lot of extra space on the right hand side... perhaps it could be trimmed?
Comments
-
As seen on: http://staging.gemcutter.org/gems/wxruby
Comments
-
0 votes
1 comment Created 3 months ago by qrush@qrushxLong gem names cause the leaderboards to breakdesignxCasrack is causing it: http://staging.gemcutter.org/
Comments
-
On line #17 of app/views/rubygems/show.html.erb 14: 15: 16: 17: <%= simple_markup(@current_version.info) %> 18: 19: 20: app/views/rubygems/show.html.erb:17 haml (2.1.0) [v] lib/haml/helpers/action_view_mods.rb:14:in `render' haml (2.1.0) [v] lib/haml/helpers/action_view_mods.rb:14:in `render' haml (2.1.0) [v] rails/./lib/sass/plugin/rails.rb:19:in `process' /home/heroku_rack/lib/static_assets.rb:9:in `call' /home/heroku_rack/lib/last_access.rb:15:in `call' /home/heroku_rack/lib/date_header.rb:14:in `call' thin (1.0.1) lib/thin/connection.rb:80:in `pre_process' thin (1.0.1) lib/thin/connection.rb:78:in `catch' thin (1.0.1) lib/thin/connection.rb:78:in `pre_process' thin (1.0.1) lib/thin/connection.rb:57:in `process' thin (1.0.1) lib/thin/connection.rb:42:in `receive_data' eventmachine (0.12.6) lib/eventmachine.rb:240:in `run_machine' eventmachine (0.12.6) lib/eventmachine.rb:240:in `run' thin (1.0.1) lib/thin/backends/base.rb:57:in `start' thin (1.0.1) lib/thin/server.rb:150:in `start' thin (1.0.1) lib/thin/controllers/controller.rb:80:in `start' thin (1.0.1) lib/thin/runner.rb:173:in `send' thin (1.0.1) lib/thin/runner.rb:173:in `run_command' thin (1.0.1) lib/thin/runner.rb:139:in `run!' thin (1.0.1) bin/thin:6 /usr/local/bin/thin:20:in `load' /usr/local/bin/thin:20Comments
-
0 votes
Update site header copy to a more consistent Sign Up/In/Out
1 comment Created 3 months ago by bryanwoodsAdded commit for review:
http://github.com/bryanwoods/gemcutter/commit/b8d50aaead89a655f5c31e95fb87b74228588610
Comments
This is fixed in the design branch: http://staging.gemcutter.org/
I'm going to add in a blurb to the readme about not making UI changes on master until the redesign done...sorry about the time wasted here :[
-
Something like: http://contributors.rubyonrails.org/
But nowhere near as complex. It could be as simple as
git shortlog -s -nthat's pushed into a pages view when deployed.Comments
-
gem master % gem push pkg/gemcutter-0.1.3.gem
Pushing gem to Gemcutter...
Successfully registered gem: gemcutter (0.0.3)
Comments
-
0 votes
3 comments Created 3 months ago by raggifeaturexSupport the use of ~/.rubyforge/user-config.yml if presentpatchxPatch replaced now, added tests.
http://github.com/raggi/gemcutter/tree/rubyforge_config
specifically:
http://github.com/raggi/gemcutter/commit/1752a4d832c135f407918ec13999938cd46d4697
Comments
-
0 votes
2 comments Created 3 months ago by jamesarosenSearch page should start with focus on input#queryfeaturex -
ERROR: While executing gem ... (NameError) uninitialized constant Gem::AbstractCommand::NetComments
What version of the gemcutter gem are you using? And Ruby?
Gemcutter: gemcutter (0.1.3)
Ruby: ruby 1.8.7 (2009-06-12 patchlevel 174) [x86_64-linux]I read the source
lib/abstract_command.rb. I solve the problem adding
requires fornet/httpandnet/httpsin source header instead
withinmake_requestmethod.I'll send to you a pull request.
But, I can't push a new gem. The response for post request method is:
... when Net::HTTPUnauthorized say "You do not have permission to manage this gem." ...I will solve this problem.
Puts! I'm sorry! I don't had migrated my gem to Gemcutter.org repository ... was the reason of the second error ... :P
Thanks.
I'm still getting error using http_proxy: uninitialized constant Gem::AbstractCommand::Net
"use_proxy!" is called before "make_request" Please move net/http requires somewhere higher. maybe in #setup ?
My current workaround is:
@@@ def use_proxy! + require 'net/http' + require 'net/https'proxy_uri = http_proxy @proxy_class = Net::HTTP::Proxy(proxy_uri.host, proxy_uri.port, proxy_uri.user, proxy_uri.password)end
-
0 votes
Difficult to use gemcutter gems in gem dependencies
4 comments Created 3 months ago by adamsalterCurrently if you want to use a gem hosted on gemcutter as a dependency of another gem you have to require that the user already have
gem install gemcutter,gem tumbleWould it be possible to have the gemcutter gem add the gemcutter source to the sources list on gem install (at the end of the sources list is fine)?
gem tumblecould move the source to the front of the sources list.That way gems could be used as gem dependencies as long as the gemcutter gem is included as a dependency first.
Comments
Sadly, the post-install hook for Rubygems seems to be broken, or else I would do that instead of using
gem tumble. Basically, it only runs the hook on installs after the gem with the given install. Also, doing that would stomp on every other gem in your system and I'm trying hard not to do that.You don't need the gemcutter gem installed in order to use the site as a gem source. All you have to do is specify
-s http://gemcutter.organd you're good to go.As for going forward, I've proposed some changes to Rubygems/Rubyforge here that you can follow: http://rubyforge.org/pipermail/rubygems-developers/2009-August/004914.html Hopefully if these get implemented, this should disappear :)
adamsalter
Tue Sep 15 18:27:37 -0700 2009
| link
Can you be more specific about the
-s http://gemcutter.org? where do I specify this?
adamsalter
Tue Sep 15 18:29:26 -0700 2009
| link
oh wait i think i get you... you mean when installing the gem on the system? sure.
But I was talking about using gemcutter gems as dependencies to rubyforge gems... can you specify a dependency source in a .gemspec file?
adamsalter
Tue Sep 15 18:48:58 -0700 2009
| link
I've raised a bug on specifying a gem dependencies source:
http://rubyforge.org/tracker/index.php?func=detail&aid=27109&group_id=126&atid=575
If this issue gets fixed my problem will be solved. Thanks for your help. :)
-
I think it would be neat to show the logged in users' gravatar. Perhaps gravatar for gem owners could be shown somewhere on gems/show too.
Comments
aussiegeek
Tue Oct 20 01:25:03 -0700 2009
| link
I'm working on this one
I think we should include a hover on the image like github does. (Hover over your gravatar image in your profile page).
http://github.com/qrush/gemcutter/commit/70372cca3e9deae15e1b1bc8bb2ce147c3c90da0 I tackled current_users' gravatar. qrush -- if this looks good I can do something similar for gem owners.
-
Everyone's going to have it and it's going to be less of a hassle for other Ruby implementations.
Comments
you could also use json_pure, which is a pure ruby implementation and will work with JRUBY!
Great stuff! Can you put up a date where the fixed version will be released?
-
It would be nice to be able to hashtag your projects so you can search against this. Have the hashtags defined in the gemspec maybe?
Considering that Rubyists like to name their projects having nothing to really do with the functionality to be able to search against such tags would be valuable.
Comments
bcardarella
Mon Sep 07 09:05:50 -0700 2009
| link
I'm looking over the RubyGem attributes: http://www.rubygems.org/read/chapter/20
and I don't see any attribute that can logically be used for this. And it appears that the Gem attributes are pretty much hard coded into RubyGems... can't create new ones on the fly. (would be nice if you could)You hit the nail on the head, this would need to be something done at the Rubygems level. You could, however, put whatever hashtags you like in your gem description.
bcardarella
Wed Sep 09 17:52:54 -0700 2009
| link
While that would be a work around I don't think it is a clean solution.
Agreed. Though, ideally, a gem's description would be complete enough to have it be found on a search for something like "json parser" without the need for hashtags.
Why would this need to be done at the RubyGem level? We could have gem authors set it manually on the site. Boom roasted.
bcardarella
Wed Sep 09 18:15:42 -0700 2009
| link
@qrush: I thought the same at first, but wouldn't it be nicer to have that stored in the gemspec? That way as features are added to a library you can just edit that info there, push to Gemcutter and have those hashtags indexed. No messing around with having to log into Gemcutter and edit those settings there.
Further, it seems that Gemcutter can also work as a good internal networked gem hosting service. So if I push something to gemcutter.org and something to a local gemcutter that's two places I have to edit those tags.
bcardarella
Wed Sep 09 18:16:58 -0700 2009
| link
@ddollar: if the gem description that is being pulled from the gemspec is being indexed then that could be a "good enough" solution
@bcardarella Yep. Gemcutter's Search searches both name and description.
bcardarella
Wed Sep 09 18:24:04 -0700 2009
| link
Hmmm... maybe this issue should be closed then. In the case of the description being searchable maybe hashtags would be redundant.
-
Ran into another issues with migrating gem from Rubyforge.
$ gem migrate pom Starting migration of pom from RubyForge... A migration token has been created. Uploading the migration token to pom.rubyforge.org. Please enter your RubyForge login: Login: transami Password: There was a problem uploading your token: SCP did not finish successfully (1) Asking Gemcutter to verify the upload... Gemcutter is still looking for your migration token.
The problem is that the pom gem is not in the pom project. It is in the proutils project.
I really wish you'd just dump this migration crap, and let us push our gems without worry about legacy releases on Rubyforge.
Comments
I just updated the rubyforge_project of that gem to proutils, so you should be able to migrate it now.
And sorry, I'm not dropping this feature. It's essential for taking over the keys for projects that were hosted on RubyForge, I don't want a situation to arise where people can't trust the gems on Gemcutter because they were pushed by random people.
The real solution is to make sure your rubyforge_project in the gemspec is set properly, which most gems that exist under multiple one giant project (like seattlerb) do.
Thanks, I knew about the error in the gem too --one reason I needed to push a new gem. I have a couple more like that. Happened b/c they were standalone at first before I moved them into a single group.
Concerning RubyForge, I see. You don't want people to push gems for ones already owned on Rubyforge. Totally agree with you there. Still, you needn't migrate gems from Rubyforge to Gemcutter in order to authenticate. If I push a gem and don't yet own it, and it's on RubyForge, why not just ask me for my RubyForge credentials then?
I had another though about this today. Couldn't the opposite come true too? That is, after someone pushes a gem to GemCutter that previously did not exist, couldn't someone release a gem of the same name on Rubyforge? Then ownership would be out of sync --indeed they could be two totally different programs.
-
It's an ugly mess, split it up, break it up into separate tasks.
Comments
-
0 votes
2 comments Created 4 months ago by redingerSome things I had to do the first time to get gemcutter runningdocsxComments
-
0 votes
2 comments Created 4 months ago by luislavenaGemcutter is identifying platforms as part of the versioning.bugxTake mongrel as example:
http://gemcutter.org/gems/mongrel
Gemcutter considers 1.1.5-x86-mingw32 as being the latest version, but that is not true. 1.1.5 is the latest version, and that version contains gems for 4 platforms:
Pure ruby
i386-mingw32
JRuby
i386-mswin32I believe that gem platform is not being parsed properly and differently or separated of the version itself.
Comments
In the redo_indexing branch I've created a separate platform column on the Version table, so hopefully this should be fixed once all of the gemspecs are reprocessed.
-
Show: # of gems, # of downloads
Rubygem.sum("downloads"), and # of users.Comments
tristandunn
Sat Oct 03 22:13:23 -0700 2009
| link
I added a simple statistics page: http://github.com/tristandunn/gemcutter/commit/b0d9dc18ee0f88d306e257e9aad495653e60018e
Awesome! I'm a total sucker for graphs so I added one in. Hopefully this will get cooler once we start tracking downloads better. http://gemcutter.org/stats
-
0 votes
1 comment Created 4 months ago by qrushLook up rubyforge project on more than just the current versionbugx -
On the page for my vizir gem (http://gemcutter.org/gems/vizir), it says the homepage is http://github.com/priteau/vizir
It was the case in the 0.2.4 gemspec.However the new gemspec (0.2.6) that I pushed to Rubyforge last week points to a new homepage: http://priteau.github.com/vizir/
Maybe the import code now handles this, but it would be nice if it would be corrected without having to upload a new version of the gem.
Comments
Hmm, that's odd. I'll look into what's going on here, I bet it's not being handled properly.
I've also had this problem with http://gemcutter.org/gems/api_cache - looks like the homepage is not being updated when a new gemspec arrives. In my case I did a gem push directly to gemcutter.
-
Seeing this in the migration cron log:
Downloading ZenTest-3.0.0.gem... PGError: ERROR: value too long for type character varying(255) : INSERT INTO "versions" ("rubyforge_project", "updated_at", "number", "description", "summary", "authors", "rubygem_id", "created_at") VALUES(E'zentest', '2009-08-08 01:02:03.171070', E'3.0.0', E'ZenTest provides 3 different tools: zentest, unit_diff, and autotest. ZenTest scans your target and unit-test code and writes your missing code based on simple naming rules, enabling XP at a much quicker pace. ZenTest only works with Ruby and Test::Unit. unit_diff is a command-line filter to diff expected results from actual results and allow you to quickly see exactly what is wrong. autotest is a continous testing facility meant to be used during development. As soon as you save a file, autotest will run the corresponding dependent tests. There are two strategies intended for ZenTest: test conformance auditing and rapid XP. For auditing, ZenTest provides an excellent means of finding methods that have slipped through the testing process. I''ve run it against my own software and found I missed a lot in a well tested package. Writing those tests found 4 bugs I had no idea existed. ZenTest can also be used to evaluate generated code and execute your tests, allowing for very rapid development of both tests and implementation.', E'* Scans your ruby code and tests and generates missing methods for you. * Includes a very helpful filter for Test::Unit output called unit_diff. * Continually and intelligently test only those files you change with autotest. * Includes a LinuxJournal article on testing with ZenTest written by Pat Eyler.', E'Ryan Davis, Eric Hodel', 20244, '2006-03-06 08:00:00.000000') RETURNING "id"Comments
-
0 votes
2 comments Created 5 months ago by qrush@ddollarxMake gem index directory case insensitivebugx -
0 votes
install/uninstall should add/remove gemcutter.org as a primary source
1 comment Created 5 months ago by qrush -
Just do what the man said.
Comments
Basic process for this:
curl -o rubygems.html 'http://rubyforge.iasi.roedu.net/gems/'Gets a list of all rubygems available on that host. We'll have to parse that list and compare it against what is currently in the db.
Previously I was doing this with
rake gemcutter:import:parseand thenrake gemcutter:import:download, but these will need to be adapted to run on Heroku's nightly cron job.Perhaps the text file of all gems could be kept in s3 for easy comparison against the latest coming down from Rubyforge.
Just use
gem list -r -a -s http://gems.rubyforge.org. This doesn't get platform versions though, which blows. Need to look into this more. -
Perhaps the summary/description for the gem, last update, etc.
Comments
Aaron and Eric did a bunch of work on a full-text search for search.rubygems.org a while ago: I think it may have used Postgres' full-text stuff to provide a really good search. Might want to ping them about it.
-
There's no way currently to do this.
Comments
Just need a really simple way to do this, it can be improved for launch.
bcardarella
Mon Aug 03 20:01:19 -0700 2009
| link
I'll get this
No worries, I didn't want to step on your toes if you had started on it.
Edit: Oops, I guess this was a message reply. In any case, I'll take care of it.
Done. Use
gem help ownerfor details. Thegemcommand needs some documentation on the website.I need this. How do I get it to work? Is there any way to just delete the gem from gemcutter and add it from another owner?
gem help owner doesn't work for me. What do I need to build / install?
It hasn't been pushed up to gemcutter.org yet as far as I know.
After that happens, you'll also need a new version of the gemcutter gem that will be built and published around the same time.
I'll push a new version of the gemcutter gem tonight and make sure the site's updated...for now I can add another email manually if you let me know here.
Thanks guys - I'm sure I can wait until you've pushed the updates. Do you envisage adding this kind of functionality on the web UI at any point, or is it going to stay at the console?
matt: For now I'd like to keep most of the interaction with gemcutter on the command line. If there's a lot of pressing demand for it we can move it out to forms on the site, but I think if we're working with
gemwe should should just use the command and not have to hassle with the site.My philosophy so far is: gem commands are for producers, the site is for consumers.
-
0 votes
1 comment Created 5 months ago by qrushDon't allow gems to have an update date beyond the current one.bugx -
gem list -rresults in:
*** REMOTE GEMS ***ERROR: http://gemcutter.org does not appear to be a repository ERROR: While executing gem ... (Gem::RemoteFetcher::FetchError) bad response Not Found 404 (http://gemcutter.org/yaml)Comments
I think I accidentally blew away the gem index when I deployed...I need to fix the capistrano scripts so that doesn't happen. Anyway, it should work now.
I can't seem to reproduce what blew away the index...if this crops up again for you let me know. Thanks!
-
Uploading a gem returns an error message, although it shows the gem uploaded to the site afterwards (so it did work).
message:
Pushing gem to Gemcutter... ERROR: While executing gem ... (NoMethodError) undefined method `strip' for nil:NilClass`Comments
Odd...I think I need to make sure the error backtrace is printed out to the console. Thanks!
The latest release of the Gemcutter gem should print out the error message so you can check it out. Let me know if this happens again in a new issue.
-
0 votes
1 comment Created 6 months ago by qrushRe-pushing version doesn't update existing versionbugx -
stty definitely won't work on Windows. The Heroku gem has this implemented, look at porting that over to the Gemcutter gem and testing it on a Windows machine.
Comments
luislavena
Tue Oct 27 15:20:47 -0700 2009
| link
A workaround to that will be rely on HighLine gem that offers cross platform input:
http://github.com/JEG2/highline
More precisely:
http://github.com/JEG2/highline/blob/master/examples/password.rb
I really think we'll have to vendor some stuff for this inside of the gemcutter plugins...since they'll be merged into RubyGems we can't rely on an external lib. :/
luislavena
Tue Oct 27 17:55:50 -0700 2009
| link
Sound fair, wanted to point to an existing tool that deal with it.
Vendoring highline will be a bit too much, so perhaps we can do a cross platform minimal implementation that just swallow the typed characters ;-)
-
See what's necessary to get this working, if it's as simple as dropping in prerelease_specs into the Hostess then let's do that.
Comments
-
Make sure to handle this when creating a new gem.
Comments
-
Provide some screenshots for this process and make it look decent. Also, move this into the app itself instead of the wiki.
Comments
-
Flesh out version one of the API, and make sure it's somewhat extensible so it can be upgraded.
Comments
For v1:
Supported formats: yaml, json, xml
Methods:
/gems.{yaml,json,xml}list of all gems/gems/<gem>.{yaml,json,xml}data about the latest gem/gems/<gem>/versionlatest version string/gems/<gem>/versions.{yaml,json,xml}list all versions/gems/<gem>-<version>.{yaml,json,xml}data about this gem version
Other ideas:
- API calls for each of the links (homepage, source code, etc) that could hook into a gem plugin.
- Access the # downloads and latest update date through the API
- Definitely have this in a namespaced controller since there will be more than one version of the api
It would be nice if
/gems/<gem>.jsonincluded information about dependencies, just like on the regular gem pages, e.g. http://gemcutter.org/gems/dm-core -
Handle projects that want to move over from RubyForge to Gemcutter full time.
Proposed way to do this:
Generate a token on the Rubygem model and have them upload to RubyForge, then check RubyForge for it.Comments
The token is now on the ownership model, and this has started to take shape in the migrate view. Just need to hook it up to RubyForge.
Almost there! Just need to hook this up to cron, and spin off a delayed job when a user requests one. We'll also need a 'status' on the ownership to show if the job has started or not.
Now going to use
gem migrateinstead of uploading news items to rubyforge.
- @ddollar▾
- @qrush▾
- @tristandunn▾
- backlog▾
- bug▾
- design▾
- docs▾
- feature▾
- patch▾
- subdomains▾
- Apply to Selection
-
Change Color…
Preview:preview
- Rename…
- Delete
I believe this might be a known issue...is the homepage in your gemspec a valid URL? If it is, gist your gemspec and I'll look further into it.
This could be the same issue I am seeing with gem version 1.3.5, where it fails to generate the gem complaining that ""http://rubyforge.org/projects/vincenty/"" is not a URI. Version 1.3.1 of gem didn't do this.
I didn't create the gemspec manually. I'm using Hoe. The gemspec has
s.homepage = %q{"http://rubyforge.org/projects/vincenty/"}
Which is valid.
Actually, that is odd. Hoe quotes a quoted string.
That was it. I extracted the gemspec from the gem and found that the URL was double quoted. Changing that fixed the problem and the gem uploads. This is a Hoe bug when it generates the gemspec.
Or my fault. Hoe gets the URL from the README.txt file. I had quotes around the URL in that file and the problem goes away when I remove those quotes. They probably should never have been there, but it has never caused a problem until now.
Great, going to close this issue then since this is already a known issue.