Tim Daneliuk writes:
> > Are you sure you are using perl-after-upgrade correctly? You do
> > understand that just running:
> >
> > # perl-after-upgrade
> >
> > doesn't actually modify anything on disk: instead it shows you what
> > needs to be done. To actually effect the change you
On 12/21/2011 09:28 AM, Matthew Seaman wrote:
On 21/12/2011 14:59, Tim Daneliuk wrote:
Almost every time there is a perl upgrade, it manages to break
Mailscanner even after running perl-after-upgrade. The solution
ends up being a reinstall of Mailscanner, but this is a real pain,
because you
On 21/12/2011 14:59, Tim Daneliuk wrote:
> Almost every time there is a perl upgrade, it manages to break
> Mailscanner even after running perl-after-upgrade. The solution
> ends up being a reinstall of Mailscanner, but this is a real pain,
> because you have to delete and rei
On 12/21/2011 03:59 PM, Tim Daneliuk wrote:
> Almost every time there is a perl upgrade, it manages to break
> Mailscanner even after running perl-after-upgrade. The solution
> ends up being a reinstall of Mailscanner, but this is a real pain,
> because you have to delete and rei
Almost every time there is a perl upgrade, it manages to break
Mailscanner even after running perl-after-upgrade. The solution
ends up being a reinstall of Mailscanner, but this is a real pain,
because you have to delete and reinstall every dependent perl
package used by Mailscanner.
Does
Friday, 12 February 2010 at 21:03:54 +, Matthew Seaman said:
> On 12/02/2010 20:50, Adam Vande More wrote:
> > On Fri, Feb 12, 2010 at 2:44 PM, Peter Harrison
> > wrote:
> >
> >> Up till now I've kept Perl on my machine at 5.8.9. I now see from UPDATING
> >> that upgrading to 5.10 is recommend
On Fri, Feb 12, 2010 at 3:26 PM, Peter Harrison
wrote:
>
> I don't need 5.10, but I was prompted to think about upgrading from
> 20100205.
>
> I was trying to follow 20090328, I ran
>
> pkgdb -Ff (no problem)
> then
> portupgrade -o lang/per5.10 -f perl-5.8.9
>
> which generated the error given.
>
Friday, 12 February 2010 at 14:50:56 -0600, Adam Vande More said:
> On Fri, Feb 12, 2010 at 2:44 PM, Peter Harrison
> wrote:
>
> > Up till now I've kept Perl on my machine at 5.8.9. I now see from UPDATING
> > that upgrading to 5.10 is recommended.
> >
> > However, when I follow the instructions,
On Fri, Feb 12, 2010 at 3:07 PM, Adam Vande More wrote:
> On Fri, Feb 12, 2010 at 3:03 PM, Matthew Seaman <
> m.sea...@black-earth.co.uk> wrote:
>
>>
>> Err... he's following the right instructions.
>>
>
> ports/UPDATING does not recommend to upgrade.
>
I mean does not "recommend" going from 5.8
On Fri, Feb 12, 2010 at 3:03 PM, Matthew Seaman
wrote:
>
> Err... he's following the right instructions.
>
ports/UPDATING does not recommend to upgrade.
--
Adam Vande More
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailma
On 12/02/2010 20:50, Adam Vande More wrote:
> On Fri, Feb 12, 2010 at 2:44 PM, Peter Harrison
> wrote:
>
>> Up till now I've kept Perl on my machine at 5.8.9. I now see from UPDATING
>> that upgrading to 5.10 is recommended.
>>
>> However, when I follow the instructions, I get the following error:
On Fri, Feb 12, 2010 at 2:44 PM, Peter Harrison
wrote:
> Up till now I've kept Perl on my machine at 5.8.9. I now see from UPDATING
> that upgrading to 5.10 is recommended.
>
> However, when I follow the instructions, I get the following error:
>
> laptop# portupgrade -o lang/perl5.10 -f perl-5.8.
Up till now I've kept Perl on my machine at 5.8.9. I now see from UPDATING that
upgrading to 5.10 is recommended.
However, when I follow the instructions, I get the following error:
laptop# portupgrade -o lang/perl5.10 -f perl-5.8.9_3
---> Upgrading 'perl-5.8.9_3' to 'perl-5.10.1' (lang/perl5.1
Hi Jerry,
Jerry wrote:
Perl-5.10 was released to the public over a year ago. Another year
transpired before it was released into the ports system. There was an
immediate problem that was corrected when the maintainer switched to
'bison' from 'YACC'. Other than that, it has performed flawlessly a
On Sat, 9 May 2009 08:31:45 -0500 (CDT)
Lars Eighner wrote:
>On Sat, 9 May 2009, Jos Chrispijn wrote:
>
>> Lars Eighner wrote:
>>> On Sat, 9 May 2009, Jos Chrispijn wrote:
>>>
>>> You must be new around here.
>> Yes, I am L-)
>>> The process described in UPDATING for upgrading to Perl 5.10 is
>>
Lars Eighner wrote:
On Sat, 9 May 2009, Matthew Seaman wrote:
I concur. If you do the pkg_info thing and the list of stuff
depending on
perl is very short, by all means upgrade before it gets long.
After having some investigation on this subject, it comes clear to me
that Perl is a very imp
On Sat, 9 May 2009, Matthew Seaman wrote:
However, I expect the consensus on the minimum supported version to change
over time and more use to be made of 5.10 specific features, so I'd certainly
recommend installing brand new machines with perl-5.10 in order to minimize
the potential for future
On Sat, 9 May 2009, Jos Chrispijn wrote:
Lars Eighner wrote:
On Sat, 9 May 2009, Jos Chrispijn wrote:
You must be new around here.
Yes, I am L-)
The process described in UPDATING for upgrading to Perl 5.10 is relatively
painless compared to previous perl upgrades. So much stuff depends upon
Jos Chrispijn wrote:
Lars Eighner wrote:
On Sat, 9 May 2009, Jos Chrispijn wrote:
The process described in UPDATING for upgrading to Perl 5.10 is
relatively
painless compared to previous perl upgrades. So much stuff depends upon
perl that:
Do you recommend having Perl updated or should I
Lars Eighner wrote:
On Sat, 9 May 2009, Jos Chrispijn wrote:
You must be new around here.
Yes, I am L-)
The process described in UPDATING for upgrading to Perl 5.10 is
relatively
painless compared to previous perl upgrades. So much stuff depends upon
perl that:
[snip]
Do you recommend havi
On Sat, 9 May 2009, Jos Chrispijn wrote:
Not that I am that paranoid, but can someone tell me why Perl 5.8 is not
automatically updated to 5.10 thru the ports, but (accordingly by UPDATING)
has to be updated by some manual interaction?
You must be new around here.
The process described in UP
On Sat, 09 May 2009 13:05:32 +0200
Jos Chrispijn wrote:
> Not that I am that paranoid, but can someone tell me why Perl 5.8 is
> not automatically updated to 5.10 thru the ports, but (accordingly by
> UPDATING) has to be updated by some manual interaction?
That's the way the port system works.
Not that I am that paranoid, but can someone tell me why Perl 5.8 is not
automatically updated to 5.10 thru the ports, but (accordingly by
UPDATING) has to be updated by some manual interaction?
--
Jos Chrispijn
___
freebsd-questions@freebsd.org mail
On Tuesday 14 April 2009 05:20:35 Ruben de Groot wrote:
> On Sun, Apr 12, 2009 at 12:05:50PM -0700, David Southwell typed:
> > On Saturday 11 April 2009 17:20:56 Chris Rees wrote:
> > > > I hope it is not too far off topic but:
> > > >
> > > > Can anyone tell me how to fix this one:
> > > >
> > > >
On Sun, Apr 12, 2009 at 12:05:50PM -0700, David Southwell typed:
> On Saturday 11 April 2009 17:20:56 Chris Rees wrote:
> > > I hope it is not too far off topic but:
> > >
> > > Can anyone tell me how to fix this one:
> > >
> > > Stale dependency: bsdpan-Pod-Perldoc-3.15 -> perl-5.8.9_2 (lang/perl5
--On April 12, 2009 2:05:50 PM -0500 David Southwell
wrote:
>
> I hope it is not too far off topic but:
It is, so note the change of subject
>
> Can anyone tell me how to fix this one:
>
> Stale dependency: bsdpan-Pod-Perldoc-3.15 -> perl-5.8.9_2
> (lang/perl5.8): can't convert nil into s
On Saturday 11 April 2009 17:20:56 Chris Rees wrote:
> 2009/4/11 David Southwell :
> > On Friday 10 April 2009 11:43:33 kime...@gmail.com wrote:
> >> Paul Schmehl wrote:
> >> > --On Friday, April 10, 2009 11:17:00 -0500 Paul Schmehl
> >> >
> >> > wrote:
> >> >> According to /usr/ports/UPDATING, if
2009/4/11 David Southwell :
> On Friday 10 April 2009 11:43:33 kime...@gmail.com wrote:
>> Paul Schmehl wrote:
>> > --On Friday, April 10, 2009 11:17:00 -0500 Paul Schmehl
>> >
>> > wrote:
>> >> According to /usr/ports/UPDATING, if you want to upgrade to perl5.10,
>> >> you do
>> >> the following:
On 6/28/05, John Larson <[EMAIL PROTECTED]> wrote:
> I recently upgraded to perl 5.8.5.. I then issued the
> use.perl port command. I then issued the portupgrade
> 'p5-*' command as root. DBI cannot be found in the
> @INC array. what am I missing.
> John Larson
> South Lake Tahoe CA
Can you tell
I recently upgraded to perl 5.8.5.. I then issued the
use.perl port command. I then issued the portupgrade
'p5-*' command as root. DBI cannot be found in the
@INC array. what am I missing.
John Larson
South Lake Tahoe CA
Yah
It all started with a simple perl upgrade from 5.8.0 to 5.8.6.
Unfortunately, DB_File fails to build properly.
I am running FreeBSD 4.10 Stable #1
Here's the resu.llts of the make test
make test
PERL_DL_NONLAZY=1 /usr/local/bin/suidperl "-MExtUtils::Comman
On Mon, Feb 07, 2005 at 12:02:08PM -0500, dave wrote:
> Hello,
> I just updated ports after being away for two weeks. The update process
> itself went fine, my problem came when i ran the command to update
> perl-dependent ports as suggested in /usr/ports/UPDATING. I got a bunch of
> failed upd
On Monday 07 February 2005 09:02 am, "dave" <[EMAIL PROTECTED]>
wrote:
> Hello,
> I just updated ports after being away for two weeks. The update
> process itself went fine, my problem came when i ran the command to
> update perl-dependent ports as suggested in /usr/ports/UPDATING. I
> got a b
Hello,
I just updated ports after being away for two weeks. The update process
itself went fine, my problem came when i ran the command to update
perl-dependent ports as suggested in /usr/ports/UPDATING. I got a bunch of
failed updates, php4-extensions, and any of my p5* ports, apache2,
subvers
> -Original Message-
> In the immortal words of "Brent Wiese" <[EMAIL PROTECTED]>...
> > Am I missing some environment variable somewhere or what?
>
> Did you run
> use.perl port
> after you upgraded the port?
D'oh!
See, I knew it was dumb. For some reason, I didn't think that needed to
In the immortal words of "Brent Wiese" <[EMAIL PROTECTED]>...
> Am I missing some environment variable somewhere or what?
Did you run
use.perl port
after you upgraded the port?
--
Tim Aslat <[EMAIL PROTECTED]>
Spyderweb Consulting
http://www.spyderweb.com.au
Phone: +61 0401088479
_
This is the sort of thing I know I should know, but I don't right now... Too
many other stresses...
Upgraded perl from 5.8.2 to 5.8.4 (both were ports).
I need to recompile a bunch of modules (for example, mod_perl).
But, most of them error out because they can't find perl 5.8.2 libraries.
Am I
"Jim Flowers" <[EMAIL PROTECTED]> writes:
> I just upgraded to perl-5.8.1 on my FreeBSD 4.9R system (5.8.0 threw an error
> on shared.bs) but after I had installed mysql-server which builds p5-DBI-137-
> 1.37 and p5-DBD-mysql-2.1026_1 as dependencies.
>
> In the past I have uninstalled perl modu
I just upgraded to perl-5.8.1 on my FreeBSD 4.9R system (5.8.0 threw an error
on shared.bs) but after I had installed mysql-server which builds p5-DBI-137-
1.37 and p5-DBD-mysql-2.1026_1 as dependencies.
In the past I have uninstalled perl modules and reinstalled them to get them
in the right pl
Does anyone know a way to upgrade perl (from 5.00503) to 5.8.0 without
loosing all currently install modules?
-Grant
Grant W. Peel
Server Admin
[EMAIL PROTECTED]
http://thenetnow.com
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message
40 matches
Mail list logo
