Hi Darío, Could you do what Lee recommends to check the files?
Regards 2012/7/24 Darío Javier Cravero <[email protected]> > Hi all, > > Is there any news on this? Did setting the encoding on the file fixed it > for you Ramón? > > I'm having the same issue right now and that wouldn't do the trick :(. > > Does somebody know if this is actually a net-ssh or a capistrano issue? > > Thanks, > Darío > > On Thursday, 20 October 2011 11:53:41 UTC+1, Rafa García wrote: >> >> Try to add on top of your recipe files: >> >> *# encoding: utf-8* >> >> >> I'm not sure if it's needed in latest Ruby 1.9.x versions but it doesn't >> take too much time to try. >> >> More info: http://yehudakatz.com/**2010/05/05/ruby-1-9-encodings-** >> a-primer-and-the-solution-for-**rails/<http://yehudakatz.com/2010/05/05/ruby-1-9-encodings-a-primer-and-the-solution-for-rails/> >> >> >> 2011/10/20 Lee Hambley <[email protected]> >> >>> Ramón, can you please Gist/pastie your /entire/ Capfile, deploy.rb and >>> the relevant stage files, I need to check what MRI 1.9 encoding headers you >>> have in the files. >>> >>> - Lee >>> >>> >>> 2011/10/20 Ramón Cahenzli <[email protected]> >>> >>>> Hi everyone, >>>> >>>> With Ruby 1.8, all our deployment recipes worked fine. But now on 1.9, >>>> they all fail due to the UTF-8 characters in them. I get this error on >>>> Capistrano 2.9.0: >>>> >>>> /usr/lib/ruby/gems/1.9.1/gems/**net-ssh-2.2.1/lib/net/ssh/**buffer.rb: >>>> 274:in `block in write': incompatible character encodings: ASCII-8BIT >>>> and UTF-8 (Encoding::CompatibilityError) >>>> >>>> As soon as any of my calls to run contain an UTF-8 character. For >>>> example: >>>> >>>> run "sed -i 's|CONTRACT_LENDING_PARTY_**STRING.*| >>>> CONTRACT_LENDING_PARTY_STRING = \"#{contract_lending_party_** >>>> string}\"|' >>>> #{configfile}" >>>> >>>> If CONTRACT_LENDING_PARTY_STRING contains an UTF-8 character, the step >>>> fails because run raises that CompatibilityError. The recipe files are >>>> UTF-8, the default locale on both the server and the client is UTF-8 >>>> as well, so I don't know what could be wrong here. Both systems are >>>> Debian GNU/Linux 6.0. >>>> >>>> Any ideas? >>>> >>>> Thanks, >>>> >>>> Ramón >>>> >>>> -- >>>> * You received this message because you are subscribed to the Google >>>> Groups "Capistrano" group. >>>> * To post to this group, send email to [email protected] >>>> * To unsubscribe from this group, send email to capistrano+unsubscribe@ >>>> **googlegroups.com <capistrano%[email protected]> For >>>> more options, visit this group at http://groups.google.com/** >>>> group/capistrano?hl=en<http://groups.google.com/group/capistrano?hl=en> >>> >>> >>> -- >>> * You received this message because you are subscribed to the Google >>> Groups "Capistrano" group. >>> * To post to this group, send email to [email protected] >>> * To unsubscribe from this group, send email to capistrano+unsubscribe@* >>> *googlegroups.com <capistrano%[email protected]> For more >>> options, visit this group at http://groups.google.com/** >>> group/capistrano?hl=en <http://groups.google.com/group/capistrano?hl=en> >>> >> >> -- > * You received this message because you are subscribed to the Google > Groups "Capistrano" group. > * To post to this group, send email to [email protected] > * To unsubscribe from this group, send email to > [email protected] For more options, visit this > group at http://groups.google.com/group/capistrano?hl=en > -- * You received this message because you are subscribed to the Google Groups "Capistrano" group. * To post to this group, send email to [email protected] * To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano?hl=en
