> Same thing happened to me. I fixed it with:
> LC_ALL="en_US.UTF-8" LANG="en_US.UTF-8" portmaster -r perl
> I did not use both of them but I can't remember which one did the trick.
> Andrei Vrincianu
Thanks for help, but the real answer came from my subsequent daily visit to
http://w
Hi,
Same thing happened to me. I fixed it with:
LC_ALL="en_US.UTF-8" LANG="en_US.UTF-8" portmaster -r perl
I did not use both of them but I can't remember which one did the trick.
Andrei Vrincianu
On Mon, Jun 17, 2013 at 7:54 AM, Thomas Mueller
wrote:
> I finished what I could of
> portmaste
I finished what I could of
portmaster -r perl
Last snag is graaphics/gegl and three ports that depend on graphics/gegl
graphics/gegl graphics/gimp-app graphics/xsane print/hplip
Last part of the log for "portmaster graphics/gegl" was
gmake[4]: Leaving directory
`/BETA1/usr/ports/gr
Edited inline correction
--- On Sun, 6/16/13, Jeffrey Bouquet wrote:
From: Jeffrey Bouquet
Subject: Re: Rebuild all ports for perl minor version update?
To: freebsd-ports@freebsd.org
Date: Sunday, June 16, 2013, 2:52 PM
--- On Sun, 6/16/13, Thomas Mueller wrote:
> From: Thomas Muel
--- On Sun, 6/16/13, Thomas Mueller wrote:
> From: Thomas Mueller
> Subject: Rebuild all ports for perl minor version update?
> To: freebsd-ports@freebsd.org
> So now I do the massive portmaster upgrade and am stopped by
> silly little things, like a conflict between the old
> They don't really need to be re-built, but it is the safest way to go. I
> never go that way as he risk is EXTREMELY low and the time savings are HUGE.
> I just posted a much quicker way in the thread on Broken SNMP::Info.
> Start with "portmaster p5-". Then go check on the remaining files (not
On Fri, Jun 14, 2013 at 3:12 AM, Thomas Mueller
wrote:
> from my priginal post:
>
> I see in the $PORTSDIR/UPDATING file that perl has been updated.
>
> perl5.16 has been updated from 5.16.2 to 5.16.3 .
>
> Since this is only (?) a minor-version update, why should it be necessary
> to upgrade all
On Fri, Jun 14, 2013 at 06:40:03AM -0400, Jerry wrote:
> On Fri, 14 Jun 2013 12:10:17 +0200 Baptiste Daroussin articulated:
> >
> > This is not a FreeBSD "specific" problem given that Marc Espie is
> > from OpenBSD and so was speaking of problems found on OpenBSD. using
> > google I found the said
On 6/14/2013 13:21, John Marino wrote:
I despise languages that aren't backwards compatible, so if 5.18
actually broke compatibility intentionally then I for one would vote for
staying on 5.16 for a long, long time. I am reserving judgement for the
full story.
I just realize that Perl default
On 6/14/2013 12:40, Jerry wrote:
Just so I am understanding this correctly, the problem is not with
Perl-5.18, but rather applications that were written for earlier
versions that may not have in fact been written in tight compliance
with the specifications of the earlier versions and those proble
On Fri, 14 Jun 2013 04:52:08 -0500
Matthew D. Fuller articulated:
> On Fri, Jun 14, 2013 at 01:12:09AM -0700 I heard the voice of
> Thomas Mueller, and lo! it spake thus:
> >
> > In that case, why didn't they go to perl 5.18?
>
> I should hope that lang/perl5.16 _NEVER_ goes to 5.18 8-}
The p
On Fri, 14 Jun 2013 12:10:17 +0200
Baptiste Daroussin articulated:
> On Fri, Jun 14, 2013 at 05:49:41AM -0400, Jerry wrote:
> > On Fri, 14 Jun 2013 10:18:31 +0200
> > John Marino articulated:
> >
> > > According to OpenBSD's Marc Espie on a pkgsrc list, a lot of
> > > established scripts will bre
Le 14/06/2013 10:12, Thomas Mueller a écrit :
> I see in the $PORTSDIR/UPDATING file that perl has been updated.
>
> perl5.16 has been updated from 5.16.2 to 5.16.3 .
>
> Since this is only (?) a minor-version update, why should it be necessary to
> upgrade all ports that depend on perl?
>
> po
from my priginal post:
I see in the $PORTSDIR/UPDATING file that perl has been updated.
perl5.16 has been updated from 5.16.2 to 5.16.3 .
Since this is only (?) a minor-version update, why should it be necessary to
upgrade all ports that depend on perl?
portmaster -r perl
In that case, why di
On Fri, Jun 14, 2013 at 05:49:41AM -0400, Jerry wrote:
> On Fri, 14 Jun 2013 10:18:31 +0200
> John Marino articulated:
>
> > According to OpenBSD's Marc Espie on a pkgsrc list, a lot of
> > established scripts will break on perl 5.18. Apparently it is not
> > highly backwards compatible.
> >
> >
On Fri, Jun 14, 2013 at 01:12:09AM -0700 I heard the voice of
Thomas Mueller, and lo! it spake thus:
>
> In that case, why didn't they go to perl 5.18?
I should hope that lang/perl5.16 _NEVER_ goes to 5.18 8-}
--
Matthew Fuller (MF4839) | fulle...@over-yonder.net
Systems/Network Admin
On Fri, 14 Jun 2013 10:18:31 +0200
John Marino articulated:
> According to OpenBSD's Marc Espie on a pkgsrc list, a lot of
> established scripts will break on perl 5.18. Apparently it is not
> highly backwards compatible.
>
> A large % of the perl packages would cease to build if they just
> mov
On 6/14/2013 10:12, Thomas Mueller wrote:
Since this is only (?) a minor-version update, why should it be necessary to
upgrade all ports that depend on perl?
In that case, why didn't they go to perl 5.18?
According to OpenBSD's Marc Espie on a pkgsrc list, a lot of established
scripts will br
I see in the $PORTSDIR/UPDATING file that perl has been updated.
perl5.16 has been updated from 5.16.2 to 5.16.3 .
Since this is only (?) a minor-version update, why should it be necessary to
upgrade all ports that depend on perl?
portmaster -r perl
In that case, why didn't they go to perl 5.1
19 matches
Mail list logo
