Dear All,
Munin stopped working after I switched to Perl 5.16 on FreeBSD 9.1. I rebuilt
all ports that depend on Perl. What did I do wrong?
Can't locate IO/Socket/INET6.pm in @INC (@INC contains:
/usr/local/lib/perl5/5.16/BSDPAN /usr/local/lib/perl5/site_perl/5.16/mach
Jack Stone ja...@sage-american.com writes:
uname -a FreeBSD mail.sagedata.net 7.0-RELEASE-p9 FreeBSD
7.0-RELEASE-p9 #2: Sun Jan 18 19:59:27 CST 2009
Running perl5.10 (yeah, old!)
This is a production server.
Been playing catchup on ports including perl as UPDATING recommends:
portupgrade
On 8/29/2012 8:27 AM, Lowell Gilbert wrote:
Jack Stone ja...@sage-american.com writes:
uname -a FreeBSD mail.sagedata.net 7.0-RELEASE-p9 FreeBSD
7.0-RELEASE-p9 #2: Sun Jan 18 19:59:27 CST 2009
Running perl5.10 (yeah, old!)
This is a production server.
Been playing catchup on ports including
On 8/29/12 8:08 AM, Jack Stone wrote:
On 8/29/2012 8:27 AM, Lowell Gilbert wrote:
Jack Stone ja...@sage-american.com writes:
uname -a FreeBSD mail.sagedata.net 7.0-RELEASE-p9 FreeBSD
7.0-RELEASE-p9 #2: Sun Jan 18 19:59:27 CST 2009
Running perl5.10 (yeah, old!)
This is a production server.
On 8/29/12 10:59 AM, David Newman wrote:
On 8/29/12 8:08 AM, Jack Stone wrote:
On 8/29/2012 8:27 AM, Lowell Gilbert wrote:
Jack Stone ja...@sage-american.com writes:
uname -a FreeBSD mail.sagedata.net 7.0-RELEASE-p9 FreeBSD
7.0-RELEASE-p9 #2: Sun Jan 18 19:59:27 CST 2009
Running perl5.10
Jack Stone ja...@sage-american.com writes:
Actually, on other servers with the same upgrading needs, perl-5.12
installed without any issue. My intention is to upgrade perl in
increments to get well past EOL.
You're somewhat on your own, then; I can't test any of my ideas before
suggesting
On 8/29/2012 1:32 PM, Lowell Gilbert wrote:
Jack Stone ja...@sage-american.com writes:
Actually, on other servers with the same upgrading needs, perl-5.12
installed without any issue. My intention is to upgrade perl in
increments to get well past EOL.
You're somewhat on your own, then; I
On 8/29/2012 1:32 PM, Lowell Gilbert wrote:
Jack Stone ja...@sage-american.com writes:
Actually, on other servers with the same upgrading needs, perl-5.12
installed without any issue. My intention is to upgrade perl in
increments to get well past EOL.
You're somewhat on your own, then; I
uname -a FreeBSD mail.sagedata.net 7.0-RELEASE-p9 FreeBSD
7.0-RELEASE-p9 #2: Sun Jan 18 19:59:27 CST 2009
Running perl5.10 (yeah, old!)
This is a production server.
Been playing catchup on ports including perl as UPDATING recommends:
portupgrade -o lang/perl5.12 -f perl-5.10.\*
That has
Mark Kane wrote:
Hi everyone. I finally did a big portupgrade on a 4.9-RELEASE system
today and I'm having some problems with Perl.
I got it updated to 5.8.7 (was 5.6.x before), ran use.perl port, and
ran the perl-after-upgrade script which were all said in UPDATING. Now
it's time to force
Michael C. Shultz wrote:
On Saturday 26 November 2005 22:20, Mark Kane wrote:
Michael C. Shultz wrote:
On Saturday 26 November 2005 19:25, Michael C. Shultz wrote:
On Saturday 26 November 2005 18:48, Mark Kane wrote:
Michael C. Shultz wrote:
On Saturday 26 November 2005 17:13, Mark Kane
On Sunday 27 November 2005 12:29, Mark Kane wrote:
Michael C. Shultz wrote:
On Saturday 26 November 2005 22:20, Mark Kane wrote:
Michael C. Shultz wrote:
On Saturday 26 November 2005 19:25, Michael C. Shultz wrote:
On Saturday 26 November 2005 18:48, Mark Kane wrote:
Michael C. Shultz
Michael C. Shultz wrote:
On Sunday 27 November 2005 12:29, Mark Kane wrote:
Michael C. Shultz wrote:
On Saturday 26 November 2005 22:20, Mark Kane wrote:
Michael C. Shultz wrote:
On Saturday 26 November 2005 19:25, Michael C. Shultz wrote:
On Saturday 26 November 2005 18:48, Mark Kane
On Sunday 27 November 2005 12:42, Mark Kane wrote:
Michael C. Shultz wrote:
On Sunday 27 November 2005 12:29, Mark Kane wrote:
Michael C. Shultz wrote:
On Saturday 26 November 2005 22:20, Mark Kane wrote:
Michael C. Shultz wrote:
On Saturday 26 November 2005 19:25, Michael C. Shultz wrote:
Michael C. Shultz wrote:
On Sunday 27 November 2005 12:42, Mark Kane wrote:
Michael C. Shultz wrote:
On Sunday 27 November 2005 12:29, Mark Kane wrote:
Michael C. Shultz wrote:
On Saturday 26 November 2005 22:20, Mark Kane wrote:
Michael C. Shultz wrote:
On Saturday 26 November 2005 19:25,
On Sunday 27 November 2005 12:54, Mark Kane wrote:
Michael C. Shultz wrote:
On Sunday 27 November 2005 12:42, Mark Kane wrote:
Michael C. Shultz wrote:
On Sunday 27 November 2005 12:29, Mark Kane wrote:
Michael C. Shultz wrote:
On Saturday 26 November 2005 22:20, Mark Kane wrote:
Michael
% positive that the old version that was
installed with 4.9 would work for the new software either.
The main goal was to update those other programs and at the same time it
would get Perl as well. I have never had bad problems like this when
upgrading Perl on any other machine, so I did not expect
never had bad problems like this when
upgrading Perl on any other machine, so I did not expect this.
As for upgrading to 4.11, I am a little nervous about doing this
remotely. Aside from there not being an official documented way to do
this remotely (everything I have seen in the handbook
Hi everyone. I finally did a big portupgrade on a 4.9-RELEASE system
today and I'm having some problems with Perl.
I got it updated to 5.8.7 (was 5.6.x before), ran use.perl port, and
ran the perl-after-upgrade script which were all said in UPDATING. Now
it's time to force upgrade/recompile the
On Saturday 26 November 2005 17:13, Mark Kane wrote:
Hi everyone. I finally did a big portupgrade on a 4.9-RELEASE system
today and I'm having some problems with Perl.
I got it updated to 5.8.7 (was 5.6.x before), ran use.perl port, and
ran the perl-after-upgrade script which were all said in
# Mark Kane:
[ upgrade perl 5.6.x-5.8.7 failed on 4-9R ]
=== p5-HTML-Tagset-3.10 depends on file: /usr/local/bin/perl5.8.7 - found
=== Configuring for p5-HTML-Tagset-3.10
/usr/libexec/ld-elf.so.1:
/usr/local/lib/perl5/5.8.7/mach/auto/Cwd/Cwd.so: Undefined symbol
perl_get_sv
Hm. Just a
Michael C. Shultz wrote:
On Saturday 26 November 2005 17:13, Mark Kane wrote:
Hi everyone. I finally did a big portupgrade on a 4.9-RELEASE system
today and I'm having some problems with Perl.
I got it updated to 5.8.7 (was 5.6.x before), ran use.perl port, and
ran the perl-after-upgrade
On Saturday 26 November 2005 18:48, Mark Kane wrote:
Michael C. Shultz wrote:
On Saturday 26 November 2005 17:13, Mark Kane wrote:
Hi everyone. I finally did a big portupgrade on a 4.9-RELEASE system
today and I'm having some problems with Perl.
I got it updated to 5.8.7 (was 5.6.x
On Saturday 26 November 2005 19:25, Michael C. Shultz wrote:
On Saturday 26 November 2005 18:48, Mark Kane wrote:
Michael C. Shultz wrote:
On Saturday 26 November 2005 17:13, Mark Kane wrote:
Hi everyone. I finally did a big portupgrade on a 4.9-RELEASE system
today and I'm having some
Michael C. Shultz wrote:
On Saturday 26 November 2005 19:25, Michael C. Shultz wrote:
On Saturday 26 November 2005 18:48, Mark Kane wrote:
Michael C. Shultz wrote:
On Saturday 26 November 2005 17:13, Mark Kane wrote:
Hi everyone. I finally did a big portupgrade on a 4.9-RELEASE system
today
On Saturday 26 November 2005 22:20, Mark Kane wrote:
Michael C. Shultz wrote:
On Saturday 26 November 2005 19:25, Michael C. Shultz wrote:
On Saturday 26 November 2005 18:48, Mark Kane wrote:
Michael C. Shultz wrote:
On Saturday 26 November 2005 17:13, Mark Kane wrote:
Hi everyone. I
Zan wrote:
uname -m = i386
which -a perl =
/usr/local/bin/perl
/usr/bin/perl
Please show:
uname -m
which -a perl
On Tuesday, August 30, 2005, at 01:30 P:M, Lowell Gilbert wrote:
Zan [EMAIL PROTECTED] writes:
in my /usr/local/bin I can clearly see that there is a newer version
of
, or if it's even possible
to upgrade Perl properly without a reboot.
There is no reason to reboot just to upgrade perl properly.
Rebooting does nothing in regard to upgrading perl, rather you just
cause inconvenience to yourself.
- Parv
the machine, or if it's even possible
to upgrade Perl properly without a reboot.
There is no reason to reboot just to upgrade perl properly.
Rebooting does nothing in regard to upgrading perl, rather you just
cause inconvenience to yourself.
- Parv
Yes, I stand corrected. Which is why
Please don't top-post.
Zan [EMAIL PROTECTED] writes:
On Tuesday, August 30, 2005, at 01:30 P:M, Lowell Gilbert wrote:
Zan [EMAIL PROTECTED] writes:
in my /usr/local/bin I can clearly see that there is a newer version
of perl (5.8.0) already there, but when I type 'perl -v' I see that
Hello,
Would you please help me?
in my /usr/local/bin I can clearly see that there is a newer version of
perl (5.8.0) already there, but when I type 'perl -v' I see that I'm
running off of 5.0. Is there anything else I can do besides trying the
use.perl port command? Because that doesn't
Zan wrote:
Hello,
Would you please help me?
in my /usr/local/bin I can clearly see that there is a newer version of
perl (5.8.0) already there, but when I type 'perl -v' I see that I'm
running off of 5.0.
5.8 is from ports. 5.0.6. i think, is system based
Is there anything else I can do
Zan [EMAIL PROTECTED] writes:
in my /usr/local/bin I can clearly see that there is a newer version
of perl (5.8.0) already there, but when I type 'perl -v' I see that
I'm running off of 5.0. Is there anything else I can do besides trying
the use.perl port command? Because that doesn't seem to
uname -m = i386
which -a perl =
/usr/local/bin/perl
/usr/bin/perl
Please show:
uname -m
which -a perl
On Tuesday, August 30, 2005, at 01:30 P:M, Lowell Gilbert wrote:
Zan [EMAIL PROTECTED] writes:
in my /usr/local/bin I can clearly see that there is a newer version
of perl (5.8.0)
Zan wrote:
5.8 is from ports. 5.0.6. i think, is system based
In my 'usr/local/BIN' perl5.8.0 already exists.
ok
you need to install the perl from ports before using use.perl port.
What I want to know is how to switch to 5.8.0 WITHOUT using use.perl
port because I already tried that,
I'm trying to upgrade all of my Perl modules installed through CPAN to
FreeBSD-port one's, but I'm running into a few difficulties with the
following ports:
bsdpan-DB_File-1.810 DB_File - Perl5 access to Berkeley DB version 1.x
bsdpan-PerlIO-via-QuotedPrint-0.06 PerlIO::via::QuotedPrint
Hi!
I'm upgrading perl 5.8 from the ports on a FreeBSD 5.3 machine, the
problem is that alot of my installed modules doesn't work after the
update (just a minor update from 5.8.2 to 5.8.6), probably becuase the
@INC changed and did not include the mach directory of 5.8.2. Is this
right ? Why
On Mon, Feb 28, 2005 at 01:34:30PM +0100, Stefan Cars wrote:
Hi!
I'm upgrading perl 5.8 from the ports on a FreeBSD 5.3 machine, the
problem is that alot of my installed modules doesn't work after the
update (just a minor update from 5.8.2 to 5.8.6), probably becuase the
@INC changed
Stefan Cars wrote:
Hi!
I'm upgrading perl 5.8 from the ports on a FreeBSD 5.3 machine, the
problem is that alot of my installed modules doesn't work after the
update (just a minor update from 5.8.2 to 5.8.6), probably becuase the
@INC changed and did not include the mach directory of 5.8.2
I have a 4.7-based system I use as a mail gateway. Yesterday I
did a portupgrade of perl from 5.6.1 to 5.6.2. Today I find that
I have no incoming mail, due to mimedefang no longer functioning:
Feb 9 09:56:39 highland mimedefang-multiplexor[91186]: Slave 0 stderr: Can't
locate MIME/Base64.pm in
Jim Hatfield wrote:
I have a 4.7-based system I use as a mail gateway. Yesterday I
did a portupgrade of perl from 5.6.1 to 5.6.2. Today I find that
I have no incoming mail, due to mimedefang no longer functioning:
But pkg_info shows p5-MIME-Base64 as present!
And it is, but not on any of the
On Wed, 9 Feb 2005 10:07:59 - , in local.freebsd.questions you
wrote:
I have a 4.7-based system I use as a mail gateway. Yesterday I
did a portupgrade of perl from 5.6.1 to 5.6.2. Today I find that
I have no incoming mail, due to mimedefang no longer functioning:
Bang my head against a wall
Karl Agee wrote:
Freebsd 4.11-pre. I am working on learning perl, and have perl 5.00x
that is in the base system when I installed 4.10-Release. Since most of
the learning materials out there are based on later verisions esp since
5.6.x some of the features arent in this older version.
I am
--On Thursday, December 30, 2004 7:54 PM -0800 Karl Agee
[EMAIL PROTECTED] wrote:
Freebsd 4.11-pre. I am working on learning perl, and have perl 5.00x
that is in the base system when I installed 4.10-Release. Since most of
the learning materials out there are based on later verisions esp since
On Fri, Dec 31, 2004 at 12:46:09PM +0100, Erik Norgaard wrote:
I haven't found big differences between 5.6 and 5.8, so I'd suggest you
use 5.8. The main reason to stick with an older version is that you
might develop scripts for platforms where the newer are not available.
I've noticed some
Freebsd 4.11-pre. I am working on learning perl, and have perl 5.00x that
is in the base system when I installed 4.10-Release. Since most of the
learning materials out there are based on later verisions esp since 5.6.x
some of the features arent in this older version.
I am considering
Karl Agee wrote:
Freebsd 4.11-pre. I am working on learning perl, and have perl 5.00x
that is in the base system when I installed 4.10-Release. Since most
of the learning materials out there are based on later verisions esp
since 5.6.x some of the features arent in this older version.
I am
Karl Agee wrote:
Freebsd 4.11-pre. I am working on learning perl, and have perl 5.00x
that is in the base system when I installed 4.10-Release. Since most
of the learning materials out there are based on later verisions esp
since 5.6.x some of the features arent in this older version.
I am
I'm sure this is a silly question, but. I know about use.perl and
so forth for the 4.x series.
Yesterday I installed FreeBSD 5.2.1, and the active Perl port
is /usr/ports/lang/perl, which is v. 5.6.1. I'd like to upgrade
to 5.8.2, which is in /usr/ports/lang/perl5.8 and thus I can't
just do
On Thu, Apr 01, 2004 at 10:05:35AM -0500, Jesse Sheidlower wrote:
Yesterday I installed FreeBSD 5.2.1, and the active Perl port
is /usr/ports/lang/perl, which is v. 5.6.1. I'd like to upgrade
to 5.8.2, which is in /usr/ports/lang/perl5.8 and thus I can't
just do portupgrade perl.
You can
On Thu, 2004-04-01 at 17:05, Jesse Sheidlower wrote:
I'm sure this is a silly question, but. I know about use.perl and
so forth for the 4.x series.
Yesterday I installed FreeBSD 5.2.1, and the active Perl port
is /usr/ports/lang/perl, which is v. 5.6.1. I'd like to upgrade
to 5.8.2, which
On Thursday 01 April 2004 07:05 am, Jesse Sheidlower wrote:
I'm sure this is a silly question, but. I know about use.perl and
so forth for the 4.x series.
Yesterday I installed FreeBSD 5.2.1, and the active Perl port
is /usr/ports/lang/perl, which is v. 5.6.1. I'd like to upgrade
to 5.8.2,
I once saw, and used, a portupgrade command line to upgrade *all* installed
perl modules. It went something like:
$ portupgrade p5-\*
However, when I try the command now I just get an error message. Can anyone
tell me the proper command?
--
Roger
portupgrade :p5-
On Mon, Dec 22, 2003 at 05:55:17PM +0700, Roger Merritt wrote:
I once saw, and used, a portupgrade command line to upgrade *all* installed
perl modules. It went something like:
$ portupgrade p5-\*
However, when I try the command now I just get an error message. Can
Roger Merritt [EMAIL PROTECTED] writes:
I once saw, and used, a portupgrade command line to upgrade *all*
installed perl modules. It went something like:
$ portupgrade p5-\*
However, when I try the command now I just get an error message. Can
anyone tell me the proper command?
That one
At 01:41 AM 12/23/03, you wrote:
Roger Merritt [EMAIL PROTECTED] writes:
I once saw, and used, a portupgrade command line to upgrade *all*
installed perl modules. It went something like:
$ portupgrade p5-\*
However, when I try the command now I just get an error message. Can
anyone tell me
At 08:48 PM 12/22/03, you wrote:
$ portupgrade p5-\*
However, when I try the command now I just get an error message. Can
anyone
tell me the proper command?
#portupgrade p5-* (as root)
That gives me:
[EMAIL PROTECTED]:~]# portupgrade p5-*
portupgrade: No match.
[EMAIL PROTECTED]:~]#
On Tue, Dec 23, 2003 at 07:42:53AM +0700, Roger Merritt wrote:
At 08:48 PM 12/22/03, you wrote:
$ portupgrade p5-\*
However, when I try the command now I just get an error message. Can
anyone
tell me the proper command?
#portupgrade p5-* (as root)
That gives me:
[EMAIL
in message [EMAIL PROTECTED], wrote Jez Hancock
thusly...
On Tue, Dec 23, 2003 at 07:42:53AM +0700, Roger Merritt wrote:
At 08:48 PM 12/22/03, you wrote:
$ portupgrade p5-\*
However, when I try the command now I just get an error
message. Can anyone tell me the proper command?
Howdy,
I'm looking for the appropriate portupgrade magic to handle these sorts
of situations automatically:
You may wish to ``make deinstall'' and install this port again
by ``make reinstall'' to upgrade it properly.
If you really wish to overwrite the old port of
On Mon, Nov 17, 2003 at 09:14:31AM -0600, Tillman Hodgson wrote:
Whats the best way to ensure that all perl modules are properly and
automatically upgrade when perl itself is upgraded?
I've since discovered that I can shorten the time somewhat by using
`pkg_info -R perl-5.6.1_14` and then
Hi,
I am currently running freebsd 5.0-current and so do not have the perl
installation as core. Perl 5.6.1 was installed as a dependency when I
installed irssi from ports and everything has been using this since. I
assume because this is the version mentioned in /etc/make.conf:
On Sun, Jan 26, 2003 at 12:50:36PM +, Matt wrote:
I am currently running freebsd 5.0-current and so do not have the perl
installation as core. Perl 5.6.1 was installed as a dependency when I
installed irssi from ports and everything has been using this since. I
assume because this is
63 matches
Mail list logo
