Your message dated Wed, 11 Jan 2012 18:14:44 -0200 with message-id <20120111201444.gq32...@debian.org> and subject line Re: [DRE-maint] Bug#609753: Sort of a solution has caused the Debian Bug report #609753, regarding missing dependencies to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 609753: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=609753 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: capistrano Version: 2.5.9-1 Severity: serious -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi, I installed capistrano and tried "cap deploy": /usr/lib/ruby/1.8/capistrano/configuration/loading.rb:152:in `require': no such file to load -- rubygems (LoadError) from /usr/lib/ruby/1.8/capistrano/configuration/loading.rb:152:in `require' from Capfile:1:in `load' from /usr/lib/ruby/1.8/capistrano/configuration/loading.rb:172:in `load_from_file' from /usr/lib/ruby/1.8/capistrano/configuration/loading.rb:89:in `load' ....SNIP... after installing rubygems1.8 version 1.3.7-3 and another "cap deploy": /usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require': no such file to load -- railsless-deploy (LoadError) from /usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in `require' from /usr/lib/ruby/1.8/capistrano/configuration/loading.rb:152:in `require' from Capfile:3:in `load' from /usr/lib/ruby/1.8/capistrano/configuration/loading.rb:172:in `load_from_file' from /usr/lib/ruby/1.8/capistrano/configuration/loading.rb:89:in `load' ....SNIP... Please do the world a favour and don't put ruby applications in Debian! Ruby seems to be a world of ever breaking crap and you shouldn't encourage its use by packaging it. Sorry for the harsh tone. Best regards, Thomas Koch - -- System Information: Debian Release: 6.0 APT prefers stable APT policy: (1000, 'stable'), (990, 'unstable'), (700, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-4-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages capistrano depends on: ii libhighline-ruby1.8 1.5.2-1 High-level interactive IO Ruby 1.8 ii libnet-scp-ruby1.8 1.0.2-2 pure ruby implementation of the sc ii libnet-sftp2-ruby1.8 2.0.3-1 Ruby implementation of the SFTP pr ii libnet-ssh-gateway-ruby1.8 1.0.1-2 Ruby library for tunneling connect ii libnet-ssh2-ruby1.8 2.0.15-1 Ruby implementation of the SSH2 cl ii ruby1.8 1.8.7.302-2 Interpreter of object-oriented scr capistrano recommends no packages. capistrano suggests no packages. - -- no debconf information -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQIcBAEBCAAGBQJNLWX5AAoJEAf8SJEEK6Za0qgP/iffSo07wXtky7gm7pcknMV6 /QB9bOfUtcUp1Jut3d3Urz0XCEeQovDsfsadb5wT0wex0+VAirjO3FzhPAdexdLx B0FggsFYzXRPoaW2l7BMbkw15lrB6yMqESobPZUJGsu8pOAV1Y9MwMfWeT2jKVK6 qv/Q6o5kGLYqxQe/G0l25iOynzOf3+xN4dfySYUdcF2JQwL4vdq8W/8RFMq2qK0x z2Q3PO4UEWLVnxeExvlpYPUz5kBNI6bZhPXtO1SL/VkZmG0Ojb1XAI4prIn/XJzq hIMW42jLNOnsiYm4DKbplblKePMLSVY//ETlkgJsav9fgEDYBTAHa2Cm/sfiTKGc JvrC0sM6jawBcTN4TXfG1e/Q6xAfgLbpB3lr77hh013yvKXMpgNYJnAwv4qwOOVL U/Ok9FVSIi5ggf1+XXZL6Lj1pMXF3vH930z/A1ZTJcB0ow/fZf4MN8L1VUkUSeJ3 DgyvE2LYD3B60k446uz1sOyHrazQ+m+gwD1lR9gWXJe6vIZKNblVYVoBTubc15U1 6lcV2+5BKl1WSkY9xVZOa0qw++09TsBN4SH6wuW1xXIJCkdD1JeovqyIX0M7C+Ia Lv3/vPnMOlB5z4umq7itTYoZThpHiGlqfFdwS1ha8xx3KH4CtYC4MLdqgmCuZ4vT LbkZfOxXEny5RYuV4W0D =zAdn -----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---Hi, Scott Kitterman escreveu isso aí: > Resolving this bug might look something like the attached patch. I'm not > sure > how often capistrano is used without rails, so it might better be a suggests. > > I also know it's possible to do non-rails deployments without the railsless- > deploy gem, so the proposed description is not 100% correct. > > Food for thought for the new maintainers. I don't propose applying the patch > as is. This could have been a problem on previous releases, but in its current version capistrano *does not* use that railsless-deploy library whatsoever [1], and works perfectly on non-Rails apps. [1] $ apt-get source capistrano Reading package lists... Done Building dependency tree Reading state information... Done NOTICE: 'capistrano' packaging is maintained in the 'Git' version control system at: git://git.debian.org/pkg-ruby-extras/capistrano.git Need to get 124 kB of source archives. Get:1 http://ftp.br.debian.org/debian/ unstable/main capistrano 2.9.0-1 (dsc) [1517 B] Get:2 http://ftp.br.debian.org/debian/ unstable/main capistrano 2.9.0-1 (tar) [117 kB] Get:3 http://ftp.br.debian.org/debian/ unstable/main capistrano 2.9.0-1 (diff) [5259 B] Fetched 124 kB in 1s (110 kB/s) dpkg-source: info: extracting capistrano in capistrano-2.9.0 dpkg-source: info: unpacking capistrano_2.9.0.orig.tar.gz dpkg-source: info: unpacking capistrano_2.9.0-1.debian.tar.gz dpkg-source: info: applying 0001-Remove-unecessary-explicit-rubygems-access.patch dpkg-source: info: applying 0002-Remove-bundler-rubygems-stuff-from-test-code.patch $ cd capistrano-2.9.0/ $ grep -r railsless . $ # ^^ nothing! Since there is nothing to be fixed here, I am closing this bug. -- Antonio Terceiro <terce...@debian.org>
signature.asc
Description: Digital signature
--- End Message ---
