https://www.redmine.org/https://www.redmine.org/favicon.ico?16793021292013-02-17T12:50:36ZRedmineRedmine - Feature #13194: I'm losthttps://www.redmine.org/issues/13194?journal_id=458102013-02-17T12:50:36ZJean-Philippe Langjp_lang@yahoo.fr
<ul></ul><blockquote>
<p>You specified: shoulda (> 3.3.2) and shoulda (> 2.11)".</p>
</blockquote>
<p>Redmine depends on shoulda 3.3.2 but it looks like you have an extra dependency on this gem. Do you have any plugin with a Gemfile (eg. <code>/plugins/*/Gemfile</code>)?</p> Redmine - Feature #13194: I'm losthttps://www.redmine.org/issues/13194?journal_id=458112013-02-17T13:18:14ZJean-Claude Wippler
<ul><li><strong>File</strong> <a href="/attachments/9076">redmine-upgrade-log.txt</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/9076/redmine-upgrade-log.txt">redmine-upgrade-log.txt</a> added</li></ul><p>Merci, Jean-Philippe, you've nailed it. I upgraded that plugin (a custom one developed for our forum by a friend), and now everything is progressing.</p>
<p>For reference, the history of every step I ended up taking, and a full log of the stuff flying by on the terminal screen. It's not so important, but illustrates how people like me stumble around in the dark at times. Keep in mind that almost nothing of that output makes sense to me (even though I'm totally familiar with Debian). As you can see in here, some issues take several steps to resolve - again, without having a clue what "nokogiri" is, for example:</p>
<pre><code>svn update<br /> git pull<br /> rake db:migrate RAILS_ENV=production<br /> bundle update<br /> gem list<br /> ls -a ~<br /> vi /root/.gem/specs/rubygems.org%80/latest_specs.4.8 <br /> git branch<br /> ls<br /> ls -ltr<br /> vi README.rdoc <br /> git log<br /> ls -l<br /> rake db:migrate RAILS_ENV=production<br /> ls plugins/*/gem*<br /> ls plugins/*/Gem*<br /> vi plugins/jl_question/Gemfile <br /> rake db:migrate RAILS_ENV=production<br /> bundle install<br /> bundle update<br /> gem install nokogiri -v '1.5.6<br /> gem install nokogiri -v '1.5.6'<br /> apt-get install libxslt-ruby<br /> gem install nokogiri -v '1.5.6'<br /> apt-get install libxslt1-dev<br /> gem install nokogiri -v '1.5.6'<br /> bundle update<br /> rake db:migrate RAILS_ENV=production<br /> rake tmp:cache:clear<br /> rake tmp:sessions:clear<br /> /etc/init.d/apache2 restart</code></pre>
<p>Feel free to close this issue, although I do hope it does plant some seeds for future docs. And thank you for the spot-on help.</p>
<p>-jcw</p> Redmine - Feature #13194: I'm losthttps://www.redmine.org/issues/13194?journal_id=458142013-02-17T17:43:50ZJan Niggemann (redmine.org team member)jan.niggemann@redmine.org
<ul></ul><p>I agree that all these gems, bundler, rake, ... can be confusing for people not familiar with rails, but what exactly can be improved in <a class="wiki-page" href="https://www.redmine.org/projects/redmine/wiki/RedmineUpgrade">RedmineUpgrade</a>?<br />I have the same gut feeling as you, that documentation can be improved. I just don't know how. We have a lot of docs in the wiki, some really good, lots rather outdated, but how can we manage to make them more useable?</p> Redmine - Feature #13194: I'm losthttps://www.redmine.org/issues/13194?journal_id=460342013-02-25T03:51:35ZIan Epperson
<ul></ul><p>I have a love/hate relationship with plugins for this very same reason - they seem to be the biggest stumbling blocks to upgrading. Each plugin developer gets to dictate exactly one version of some library, which may conflict the version another plugin developer decided to use. I've had plugins that look interesting but I can't get to install due to these conflicts.</p>
<p>Perhaps Redmine developers can create a method to coordinate plugin dependancies? Make specific versions of dependancies the "Redmine official" used one? If that's feasible, perhaps have a test install environment where these official dependancies are required, and if a plugin can't be installed with those requirements, it's rejected somehow?</p> Redmine - Feature #13194: I'm losthttps://www.redmine.org/issues/13194?journal_id=486172013-04-15T13:43:46ZDerric Atzrott
<ul></ul><p>I second third and fourth this request.</p>
<p>Documentation of all sorts is in a terrible shape for Redmine. From the point of view of a Sysadmin the documentation is terrible, and even from the developer standpoint I find the documentation terrible.</p>
<p>It seems the answer to every problem involves looking up arcane ruby and rails magic. Having to ask questions on Stack Exchange shouldn't be something that I find myself contemplating every time I have to make some sort of change to my setup, the documentation should provide the answers I need.</p>
<p>Perhaps a shell script could be written that runs the commands needed for an upgrade and spits out somewhat more useful error messages for non-ruby types?</p> Redmine - Feature #13194: I'm losthttps://www.redmine.org/issues/13194?journal_id=491612013-05-06T23:36:57ZJean-Baptiste Barth
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Closed</i></li><li><strong>Resolution</strong> set to <i>Invalid</i></li></ul><p><a class="user active" href="https://www.redmine.org/users/2893">Ian Little</a>: the idea was once proposed of having official plugins, but it just takes too much effort for a small team. The fundamentals of redmine plugins evolved a bit from 1.x to 2.x but that shouldn't break on every minor release. Which it does, in reality, for various reasons, some very surprising. The very problem of the whole redmine plugins ecosystem is that most of them are not tested at all. In most cases we wouldn't even know how to automatically test that they don't fall in a 500 error with the next upgrade, but that's hard to automate if the plugin author didn't write some basic tests. I'd have some ideas to improve that but for now I stick with my own plugins only cause it bit me in the past, same as you.</p>
<p>@Derric: wow, that's a criticism. The wiki is open to everyone with a redmine account basically, so if you have precise idea on what to do on some pages, go! If it's more of a general trend, feel free to open an issue with your analysis on the subject ; maybe we just need a "ruby concepts for non-rubyists" page, as Opscode did with their "ruby for non-rubyists" in the Chef wiki. Assign the issue directly to me, I'd be happy to think about it with you and spend some time to fix things that need to be fixed. I find the few "official" docs (the ones maintained by the team, like <a class="wiki-page" href="https://www.redmine.org/projects/redmine/wiki/RedmineInstall">RedmineInstall</a>, <a class="wiki-page" href="https://www.redmine.org/projects/redmine/wiki/Rest_api">Rest_api</a>, ..) quite correct. As a sysadmin I find them linear enough with the required details to check prerequisites. But any precise/constructive criticism is welcome! I strongly encourage you to open a new issue with your thoughts.</p>
<p>@Jean-Claude: as this issue is solved I close the issue, thanks for the feedback!</p>