Re: p5-Bit-Vector SHA256 Checksum mismatch (was PERL problem installing SQLgrey)

2013-03-04 Thread Trond Endrestøl
On Fri, 1 Mar 2013 14:06+0100, Wolfgang Riegler wrote: > SQLgrey is the only one failing because of the dependency for > p5-Bit-Vector. I tried it several times. Even downloading manually > to /usr/ports/distfiles doesn't work. I test the sha256 checksum > manually, and it is correct. I came a

p5-Bit-Vector SHA256 Checksum mismatch (was PERL problem installing SQLgrey)

2013-03-04 Thread Wolfgang Riegler
Hi, I have the same problem. I use poudriere to package all needed software for my servers. SQLgrey is the only one failing because of the dependency for p5-Bit-Vector. I tried it several times. Even downloading manually to /usr/ports/distfiles doesn't work. I test the sha256 checksum manually

math/p5-Bit-Vector size error (was PERL problem installing SQLgrey)

2013-02-21 Thread parv
in message <51253e9d.901a.28c09d00.5088e...@go2france.com>, wrote lcon...@go2france.com thusly... > > > freebsd 9.0 > > portsnap fetch update ... > ===> Installing for sqlgrey-1.8.0 ... > ===> sqlgrey-1.8.0 depends on package: p5-Date-Calc>=0 - not found > ===>Verifying install for p5-Date-

Re: PERL problem installing SQLgrey

2013-02-21 Thread Matthew Seaman
On 20/02/2013 21:22, lcon...@go2france.com wrote: > ===> p5-Date-Calc-6.3 depends on package: p5-Bit-Vector>=7.1 - not found > ===>Verifying install for p5-Bit-Vector>=7.1 in > /usr/ports/math/p5-Bit-Vector > ===> Extracting for p5-Bit-Vector-7.2_2 > => SHA256 Checksum mismatch for Bit-Vecto

PERL problem installing SQLgrey

2013-02-20 Thread lconrad
freebsd 9.0 portsnap fetch update ... completed successfully cd /usr/ports/mail/sqlgrey make install ===> Installing for sqlgrey-1.8.0 ===> sqlgrey-1.8.0 depends on package: p5-Net-Server>=0 - found ===> sqlgrey-1.8.0 depends on package: p5-IO-Multiplex>=0 - found ===> sqlgrey-1.8.0

Re: Perl Problem After Upgrade to 5.12.4

2011-07-08 Thread Tim Daneliuk
On 7/8/2011 8:39 AM, Jerry said this: > On Fri, 08 Jul 2011 08:12:16 -0500 > Tim Daneliuk articulated: > >> I was able to work around this by: >> >> 1) Uninstalling spamassassin and perl 5.12 >> 2) Upgrading to perl 5.14 >> 3) Running perl-after-upgrade >> 4) Reinstalling spamassassin > > That is

Re: Perl Problem After Upgrade to 5.12.4

2011-07-08 Thread Jerry
On Fri, 08 Jul 2011 08:12:16 -0500 Tim Daneliuk articulated: > I was able to work around this by: > > 1) Uninstalling spamassassin and perl 5.12 > 2) Upgrading to perl 5.14 > 3) Running perl-after-upgrade > 4) Reinstalling spamassassin That is not exactly the method prescribed in UPDATING: 201

Re: Perl Problem After Upgrade to 5.12.4

2011-07-08 Thread Tim Daneliuk
On 7/8/2011 6:52 AM, Jerry said this: > On Fri, 08 Jul 2011 13:00:24 +0200 > SoCruel.NU FreeBSD Questions Mailbox articulated: > >> On Wed, 06 Jul 2011 10:01:21 -0500, Tim Daneliuk wrote: >>> Ideas anyone? >>> >>> I am trying to rebuild SpamAssassin after a perl upgrade to 5.12.4 >>> and >>> get

Re: Perl Problem After Upgrade to 5.12.4

2011-07-08 Thread Jerry
On Fri, 08 Jul 2011 13:00:24 +0200 SoCruel.NU FreeBSD Questions Mailbox articulated: > On Wed, 06 Jul 2011 10:01:21 -0500, Tim Daneliuk wrote: > > Ideas anyone? > > > > I am trying to rebuild SpamAssassin after a perl upgrade to 5.12.4 > > and > > get this (I DID run perl-after-upgrade prior to

Re: Perl Problem After Upgrade to 5.12.4

2011-07-08 Thread SoCruel.NU FreeBSD Questions Mailbox
On Wed, 06 Jul 2011 10:01:21 -0500, Tim Daneliuk wrote: Ideas anyone? I am trying to rebuild SpamAssassin after a perl upgrade to 5.12.4 and get this (I DID run perl-after-upgrade prior to this): ===> p5-Encode-Detect-1.01 depends on file: /usr/local/lib/perl5/site_perl/5.12.4/Module/Build

Re: Perl Problem After Upgrade to 5.12.4

2011-07-07 Thread Peter Vereshagin
God love is hard to find. You got lucky freebsd-questions! 2011/07/06 10:01:21 -0500 Tim Daneliuk => To FreeBSD Mailing List : TD> ===> p5-Module-Build-0.3800_1 depends on package: p5-Parse-CPAN-Meta>=1.44.01 - found TD> ! Parse::CPAN::Meta (1.40) is installed, but we need version >= 1.44

Perl Problem After Upgrade to 5.12.4

2011-07-06 Thread Tim Daneliuk
Ideas anyone? I am trying to rebuild SpamAssassin after a perl upgrade to 5.12.4 and get this (I DID run perl-after-upgrade prior to this): ===> p5-Encode-Detect-1.01 depends on file: /usr/local/lib/perl5/site_perl/5.12.4/Module/Build.pm - not found ===>Verifying install for /usr/local/l

Re: perl problem

2006-08-07 Thread Giorgos Keramidas
On 2006-08-03 10:50, RJ45 <[EMAIL PROTECTED]> wrote: > Hello using imapsync to make a transition from imapuw to a > cyrus server make the imapsync perl process to die on FreeBSD > 6.1 because it uses more than 512MB of memory. > > this does not happen using imapsync with the same transfer > operat

perl problem

2006-08-03 Thread RJ45
Hello using imapsync to make a transition from imapuw to a cyrus server make the imapsync perl process to die on FreeBSD 6.1 because it uses more than 512MB of memory. this does not happen using imapsync with the same transfer operations on hte same mailboxes on a Linux fedora box the memory

Perl problem upgrading net-snmp

2005-06-12 Thread Ian Moore
f required though. I assume it's a perl problem and have tried googling for a solution. I found some stuff about the Undefined symbol "perl_get_sv" error, but haven't found anything that's helped me fix it so far. A possible solution I thought might be to pkg_delet

Re: a strange perl problem?

2002-11-08 Thread Matthew Seaman
On Thu, Nov 07, 2002 at 10:47:10PM -0800, Vincent Chen wrote: > Hi, all > > I wrote a perl script to destroy gif interface. It has > a line looks like this: > > system("ifconfig","gif0","destroy"); > > yes, this script is running suidperl and has suid bit > set. > > The problem is this script w

a strange perl problem?

2002-11-07 Thread Vincent Chen
Hi, all I wrote a perl script to destroy gif interface. It has a line looks like this: system("ifconfig","gif0","destroy"); yes, this script is running suidperl and has suid bit set. The problem is this script work fine if called under shell prompt but not working if called by a suidperl CGI.