Hi Marc,
I have a VPS, so I should be able to update perl modules as I'd like
to.
Is there some dependency tree that is causing the HTTP::Message
(and/or HTTP::Request) module to be held back? Rather than use
the local::lib approach, I'd just like to get the latest and greatest
code
on my server. Have you run into my problem before?
In case it made any difference, I tried both:
$twit->update($tweet);
my $res = $twit->update({ status => $tweet });
and still got:
HTTP::Message content not bytes at /usr/lib/perl5/site_perl/5.8.8/HTTP/
Request/Common.pm line 90
in both cases. Would love to get this fixed! I really appreciate
that
you wrote Net::Twitter, it's been awesome.
Thanks,
David
On Sep 24, 11:10 am, Marc Mims <marc.m...@gmail.com> wrote:
> * sftriman <dal...@gmail.com> [100923 07:19]:
>
>
>
> > I see - well, I'm using cPanel and tried, got this:
>
> > Installing Perl Module "HTTP::Message"
>
> > Method: Perl Expect
> > Testing connection speed...(using fast method)...Done
> > Ping:0 (ticks) Testing connection speed to cpan.erlbaum.net using
> > pureperl...(14957.14 bytes/s)...Done
> > Ping:0 (ticks) Testing connection speed to mirrors.24-7-solutions.net
> > using pureperl...(103966.67 bytes/s)...Done
> > Ping:0 (ticks) Testing connection speed to cpan.belfry.net using
> > pureperl...(157050.00 bytes/s)...Done
> > Three usable mirrors located
> > Mirror Check passed for cpan.belfry.net (/index.html)
> > commit: wrote '/usr/lib/perl5/5.8.8/CPAN/Config.pm'
> > CPAN: Storable loaded ok (v2.21)
> > Going to read /home/.cpan/Metadata
> > Database was generated on Wed, 22 Sep 2010 00:34:03 GMT
> > cPCPAN: Module (HTTP::Message) holdback (5.837 held back to 5.810)
> > HTTP::Message is up to date (5.810).
> > perlmod--Install done
>
> > So not sure what to do.
>
> Take a look at
> local::lib:http://search.cpan.org/~getty/local-lib-1.006007/lib/local/lib.pm
>
> You should be able to install your own, local modules in your home
> directory.
>
> -Marc
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
