Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: hollunder@lavabit.com
To: "sup-talk" <sup-talk@rubyforge.org>
Subject: [sup-talk] small patch and build error
Date: Fri, 18 Nov 2011 19:33:08 -0500 (EST)	[thread overview]
Message-ID: <29426.143.205.216.123.1321662788.squirrel@lavabit.com> (raw)
In-Reply-To: <1321649693-sup-3146@stapelberg.de>

[-- Attachment #1: Type: text/plain, Size: 731 bytes --]

Hi there again,
I have a small patch as well. This one is against sup-next and fixes a
path issue in the rakefile ("cannot load such file -- sup-files") and a
deprecation warning ("WARNING: rake/gempackagetask is deprecated.  Use
rubygems/package_task instead")

However, I don't manage to build sup-next, this time with:
/usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': iconv will
be deprecated in the future, use String#encode instead.
/usr/lib/ruby/gems/1.9.1/gems/gettext-2.1.0/lib/gettext/runtime/locale_path.rb:20:
Use RbConfig instead of obsolete and deprecated Config.
rake aborted!
invalid date format in specification: "2011-11-19 01:30:45 +0100"

I don't quite know how to fix this one.

Regards,
Philipp

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: rakefile.patch --]
[-- Type: text/x-patch; name="rakefile.patch", Size: 386 bytes --]

--- ../sup-next/Rakefile	2011-11-19 01:15:01.091850944 +0100
+++ Rakefile	2011-11-19 01:25:10.155791337 +0100
@@ -31,9 +31,9 @@
 
 $:.push "lib"
 require 'rubygems'
-require "sup-files"
-require "sup-version"
-require 'rake/gempackagetask.rb'
+require "./sup-files"
+require "./sup-version"
+require 'rubygems/package_task.rb'
 
 spec = Gem::Specification.new do |s|
   s.name = %q{sup}

[-- Attachment #3: Type: text/plain, Size: 140 bytes --]

_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk

  reply	other threads:[~2011-11-19  2:02 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-07  9:17 [sup-talk] exception --- RuntimeError from thread: poll after loading inbox hollunder
2011-11-07 21:27 ` Tero Tilus
2011-11-08  9:57   ` hollunder
2011-11-09 19:25     ` Gaute Hope
2011-11-09 19:52       ` Gaute Hope
2011-11-18 19:34         ` hollunder
2011-11-21 20:36           ` Gaute Hope
2011-11-21 20:16             ` Philipp Überbacher
2011-11-21 21:18               ` Michael Stapelberg
2011-11-21 22:15                 ` Philipp Überbacher
2011-11-21 22:24                   ` Michael Stapelberg
2011-11-22  8:39                     ` Philipp Überbacher
2011-11-21 23:48                   ` Gaute Hope
     [not found]                     ` <1321953145-sup-1447@eris>
2011-11-22 15:10                       ` Gaute Hope
2011-11-18 20:55         ` Michael Stapelberg
2011-11-19  0:33           ` hollunder [this message]
2011-11-21 20:29             ` [sup-talk] small patch and build error Gaute Hope
2011-11-29 20:39         ` [sup-talk] exception --- RuntimeError from thread: poll after loading inbox Johannes Janosovits
2011-11-29 22:19           ` Johannes Janosovits
2011-12-17 18:47         ` Hamish D
2011-11-08 13:39 ` Mark Alexander

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=29426.143.205.216.123.1321662788.squirrel@lavabit.com \
    --to=hollunder@lavabit.com \
    --cc=sup-talk@rubyforge.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox