Databases
StackOverflow2013
Postsdbo
POAny other way to circumvent the Illformed requirement YAML::Syck::DefaultKey errors then to upgrade RubyGems?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POAny other way to circumvent the Illformed requirement YAML::Syck::DefaultKey errors then to upgrade RubyGems?
    primarykey
    data
    text
    <p>I am getting <code>Invalid gemspec in [path/to/vendor/bundle/spree_api-1.0.0.gemspec]: Illformed requirement ["#&lt;YAML::Syck::DefaultKey:0x2ac381f81938&gt; 1.0.0"]</code> for several gems (all Spree, and its spree_* requirements). I have reported the issue with both spree (whom, I suspect, changed their build-line; and with the hoster, site5, who has an outdated version of RubyGems, 1.6.2)</p> <p><a href="https://stackoverflow.com/questions/9004804/invalid-gemspec-illformed-requirement-yamlsyckdefaultkey0xb5f9c990-3">Several</a> <a href="https://stackoverflow.com/questions/8962752/how-do-i-fix-rails-installation-errors">questions</a> on stackoverflow have solutions for this, but none are applicable to me. </p> <ol> <li>I cannot use RVM to upgrade to other versions of Ruby, because the (v)host has passenger installed, which AFAIK only allows running one Ruby version. I have no access to the Passenger Setup, other then trough a <code>.htaccess</code> in my <code>public</code> folder.</li> <li>I cannot do <code>gem update --system</code>, because that requires <em>sudo</em>, which I don't have.</li> </ol> <p>I am curious why this error occurs: Is it something that can be solved by building the gem myself (e.g. from git), rather then fetching it from rubygems.org.</p> <p>Is it maybe something that can be solved by packaging the gems on my development machine? I don't encounter the problem there, and other then the RubyGems version,my dev machine has the exact same Ruby version installed (there I can use rvm just fine).</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USberkes
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POAny other way to circumvent the Illformed requirement YAML::Syck::DefaultKey errors then to upgrade RubyGems?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POAny other way to circumvent the Illformed requirement YAML::Syck::DefaultKey errors then to upgrade RubyGems?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POAny other way to circumvent the Illformed requirement YAML::Syck::DefaultKey errors then to upgrade RubyGems?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI managed to get passed this problem by using `:git => 'some/git/url'` in the Gemfile; bundler can then handle the gem correctly. Still very much interested in the reason behind this error though.
      singulars
      1. POAny other way to circumvent the Illformed requirement YAML::Syck::DefaultKey errors then to upgrade RubyGems?
      1. USberkes
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload