Perl packages fails to build
Hi all, Using freebsd 9.2 amd64 and poudriere, perl fails to build: /bin/mkdir -p /wrkdirs/usr/ports/lang/perl5.14/work/stage/usr/local/lib/perl5/5.14/BSDPAN/. install -o root -g wheel -m 444 /wrkdirs/usr/ports/lang/perl5.14/work/BSDPAN-2007/BSDPAN.pm /wrkdirs/usr/ports/lang/perl5.14/work/stage/usr/local/lib/perl5/5.14/BSDPAN/BSDPAN.pm /bin/mkdir -p /wrkdirs/usr/ports/lang/perl5.14/work/stage/usr/local/lib/perl5/5.14/BSDPAN/BSDPAN install -o root -g wheel -m 444 /wrkdirs/usr/ports/lang/perl5.14/work/BSDPAN-2007/BSDPAN/Override.pm /wrkdirs/usr/ports/lang/perl5.14/work/stage/usr/local/lib/perl5/5.14/BSDPAN/BSDPAN/Override.pm /bin/mkdir -p /wrkdirs/usr/ports/lang/perl5.14/work/stage/usr/local/lib/perl5/5.14/BSDPAN/. install -o root -g wheel -m 444 /wrkdirs/usr/ports/lang/perl5.14/work/BSDPAN-2007/Config.pm /wrkdirs/usr/ports/lang/perl5.14/work/stage/usr/local/lib/perl5/5.14/BSDPAN/Config.pm /bin/mkdir -p /wrkdirs/usr/ports/lang/perl5.14/work/stage/usr/local/lib/perl5/5.14/BSDPAN/ExtUtils install -o root -g wheel -m 444 /wrkdirs/usr/ports/lang/perl5.14/work/BSDPAN-2007/ExtUtils/MM_Unix.pm /wrkdirs/usr/ports/lang/perl5.14/work/stage/usr/local/lib/perl5/5.14/BSDPAN/ExtUtils/MM_Unix.pm /bin/mkdir -p /wrkdirs/usr/ports/lang/perl5.14/work/stage/usr/local/lib/perl5/5.14/BSDPAN/ExtUtils install -o root -g wheel -m 444 /wrkdirs/usr/ports/lang/perl5.14/work/BSDPAN-2007/ExtUtils/MakeMaker.pm /wrkdirs/usr/ports/lang/perl5.14/work/stage/usr/local/lib/perl5/5.14/BSDPAN/ExtUtils/MakeMaker.pm /bin/mkdir -p /wrkdirs/usr/ports/lang/perl5.14/work/stage/usr/local/lib/perl5/5.14/BSDPAN/ExtUtils install -o root -g wheel -m 444 /wrkdirs/usr/ports/lang/perl5.14/work/BSDPAN-2007/ExtUtils/Packlist.pm /wrkdirs/usr/ports/lang/perl5.14/work/stage/usr/local/lib/perl5/5.14/BSDPAN/ExtUtils/Packlist.pm > Compressing man pages ===> Installing for perl-5.14.4_1 ===> Checking if lang/perl5.14 already installed ===> Registering installation for perl-5.14.4_1 pkg-static: lstat(/wrkdirs/usr/ports/lang/perl5.14/work/stage/usr/local/lib/perl5/5.14/man/man3/): No such file or directory pkg-static: lstat(/wrkdirs/usr/ports/lang/perl5.14/work/stage/usr/local/lib/perl5/5.14/man/): No such file or directory pkg-static: lstat(/wrkdirs/usr/ports/lang/perl5.14/work/stage/usr/local/lib/perl5/site_perl/5.14/mach/sys/): No such file or directory pkg-static: lstat(/wrkdirs/usr/ports/lang/perl5.14/work/stage/usr/local/lib/perl5/site_perl/5.14/mach/machine/): No such file or directory pkg-static: lstat(/wrkdirs/usr/ports/lang/perl5.14/work/stage/usr/local/lib/perl5/site_perl/5.14/mach/auto/): No such file or directory pkg-static: lstat(/wrkdirs/usr/ports/lang/perl5.14/work/stage/usr/local/lib/perl5/site_perl/5.14/auto/): No such file or directory *** [fake-pkg] Error code 74 Stop in /usr/ports/lang/perl5.14. ===> Cleaning for perl-5.14.4_1 build of /usr/ports/lang/perl5.14 ended at Thu Oct 3 13:07:33 UTC 2013 build time: 00:05:13 Any idea?? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Perl error in Munin after upgrading Perl
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 /usr/local/lib/perl5/site_perl/5.16 /usr/local/lib/perl5/5.16/mach /usr/local/lib/perl5/5.16 .) at /usr/local/lib/perl5/site_perl/5.16/Munin/Master/Node.pm line 18. BEGIN failed--compilation aborted at /usr/local/lib/perl5/site_perl/5.16/Munin/Master/Node.pm line 18. Compilation failed in require at /usr/local/lib/perl5/site_perl/5.16/Munin/Master/UpdateWorker.pm line 17. BEGIN failed--compilation aborted at /usr/local/lib/perl5/site_perl/5.16/Munin/Master/UpdateWorker.pm line 17. Compilation failed in require at /usr/local/lib/perl5/site_perl/5.16/Munin/Master/Update.pm line 17. BEGIN failed--compilation aborted at /usr/local/lib/perl5/site_perl/5.16/Munin/Master/Update.pm line 17. Compilation failed in require at /usr/local/share/munin/munin-update line 14. BEGIN failed--compilation aborted at /usr/local/share/munin/munin-update line 14. Kees Jan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
perl threaded, python threaded
Hi, could anyone tell me why it is obviously that difficult to get perl or python working with threaded support? Each time I tested to use threaded feature in perl or python on different machines with different FreeBSD-versions something went wrong. When I switched back everything compiled smoothly. Maybe this was already discussed somewhere. Then please give me the link. Regards, kaltheat ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: perl-after-upgrade mistakenly thinks nothing needs to be done
Thanks for the replies; I really appreciate it.
Alexandre wrote:
> Have you followed steps described in perl-after-upgrade man page?
> $ man perl-after-upgrade
Yes, except for the last step (deleting old CONTENTS backups), since the
previous steps didn't seem to do what they should. As I said,
perl-after-upgrade thinks there's nothing to do. It doesn't report any
packages it can't handle. It handles them, but for some reason determines that
they are OK, despite the fact that the modules are all still sitting in the
old installation.
Anton Shterenlikht wrote:
> Have you done "portmaster 5-"?
> If not, do it.
I hadn't done that.
("portmaster 5-" doesn't work, but "portmaster p5-" does.)
UPDATING makes mention of this, but I didn't understand that it was saying it
was a required step. Specifically, this is what it says:
-
20120630:
AFFECTS: users of lang/perl*
AUTHOR: s...@freebsd.org
lang/perl5.16 is out. If you want to switch to it from, for example
lang/perl5.12, that is:
Portupgrade users:
0) Fix pkgdb.db (for safety):
pkgdb -Ff
1) Reinstall new version of Perl (5.16):
env DISABLE_CONFLICTS=1 portupgrade -o lang/perl5.16 -f perl-5.12.\*
2) Reinstall everything that depends on Perl:
portupgrade -fr perl
Portmaster users:
portmaster -o lang/perl5.16 lang/perl5.12
Conservative:
portmaster p5-
Comprehensive (but perhaps overkill):
portmaster -r perl-
Note: If the "perl-" glob matches more than one port you will need to
specify the name of the Perl directory in /var/db/pkg explicitly.
The default version for Perl has also been changed from 5.12 to 5.14.
-
Because of the way the portupgrade section is numbered, I thought the
portmaster section was giving me 3 options: regular, conservative,
comprehensive -- not two steps (1. portmaster -o, then 2. choose either the
conservative or comprehensive option).
...partly my reading comprehension failure, I guess. It makes no mention of
perl-after-upgrade, though.
My understanding is that perl-after-upgrade looks at what perl-dependent
packages are installed. As I can see by its output, this includes not just the
application packages like SpamAssassin and mrtg, but their requisite Perl
module packages as well, like HTML::Parser. Then, as these packages are found,
perl-after-upgrade moves things from the old Perl installation over to the
new, and does some other cleanup.
Maybe that's a flawed assumption, because it seems rather weird to me that
before running perl-after-upgrade, I'm expected to *first* to do a *full
upgrade or reinstall* of the modules.
Isn't that exactly what we're trying to avoid by running perl-after-upgrade?
Nothing in the perl-after-upgrade man page suggests this is necessary; in
fact, the intro implies the opposite.
> After this is done,
> how much have you got left under 5.12.4?
Not much of anything, just a man page, a few mrtg .pm files...
Naturally, running perl-after-upgrade at this point yields the same results as
before (0 moved, 0 modified, 0 adjusted for everything). But this time, that's
the expected output, I believe, given that I just reinstalled everything.
I guess I'm just completely confused about what perl-after-upgrade was
actually supposed to do, so it's difficult to suggest documentation updates.
At the very least, though, maybe change UPDATING to clarify that the
portmaster steps are a sequence, and mention perl-after-upgrade.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: perl-after-upgrade mistakenly thinks nothing needs to be done
Hi Mike, Have you followed steps described in perl-after-upgrade man page? $ man perl-after-upgrade Regards, Alexandre On Thu, Apr 11, 2013 at 3:08 PM, Mike Brown wrote: > Hi all, > > I'm running 8.3-RELEASE and thought I'd update Perl from 5.12 to 5.16. > Silly me. I updated my ports snapshot, and as per UPDATING, ran > > portmaster -o lang/perl5.16 lang/perl5.12 > > This went OK, so I then ran perl-after-upgrade, with and without -f. It > scans > the packages and finds everything it should, but insists nothing needs to > be > done, saying " 0 moved, 0 modified, 0 adjusted" for every one of them. At > the > end it says "Fixed 0 packages (0 files moved, 0 files modified)". > > Well of course this isn't right; all my modules are still sitting in the > 5.12.4 directory and are not getting moved over to the 5.16.2 one. This > naturally breaks everything depending on those modules. > > What's going wrong? Sorry if this is a novice question. > > Please let me know what I need to check. Thanks, > > Mike > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to " > freebsd-questions-unsubscr...@freebsd.org" > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: perl-after-upgrade mistakenly thinks nothing needs to be done
From: Mike Brown Subject: perl-after-upgrade mistakenly thinks nothing needs to be done To: freebsd-questions@freebsd.org Date: Thu, 11 Apr 2013 07:08:17 -0600 (MDT) Hi all, I'm running 8.3-RELEASE and thought I'd update Perl from 5.12 to 5.16. Silly me. I updated my ports snapshot, and as per UPDATING, ran portmaster -o lang/perl5.16 lang/perl5.12 This went OK, so I then ran perl-after-upgrade, with and without -f. It scans the packages and finds everything it should, but insists nothing needs to be done, saying " 0 moved, 0 modified, 0 adjusted" for every one of them. At the end it says "Fixed 0 packages (0 files moved, 0 files modified)". Well of course this isn't right; all my modules are still sitting in the 5.12.4 directory and are not getting moved over to the 5.16.2 one. This naturally breaks everything depending on those modules. What's going wrong? Sorry if this is a novice question. Please let me know what I need to check. Thanks, Mike Don't know the answer to your exact question. Have you done "portmaster 5-"? If not, do it. After this is done, how much have you got left under 5.12.4? Anton ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
perl-after-upgrade mistakenly thinks nothing needs to be done
Hi all, I'm running 8.3-RELEASE and thought I'd update Perl from 5.12 to 5.16. Silly me. I updated my ports snapshot, and as per UPDATING, ran portmaster -o lang/perl5.16 lang/perl5.12 This went OK, so I then ran perl-after-upgrade, with and without -f. It scans the packages and finds everything it should, but insists nothing needs to be done, saying " 0 moved, 0 modified, 0 adjusted" for every one of them. At the end it says "Fixed 0 packages (0 files moved, 0 files modified)". Well of course this isn't right; all my modules are still sitting in the 5.12.4 directory and are not getting moved over to the 5.16.2 one. This naturally breaks everything depending on those modules. What's going wrong? Sorry if this is a novice question. Please let me know what I need to check. Thanks, Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
ports issue: delete upstream perl dependencies by mistake
I did something dumb I think with ports on my box. In the process of upgrading Perl, for every package that depended on Perl, via pkgdb, I somehow managed to delete the fact that the package depends on Perl itself. So now I have a bunch of packages that no longer reference Perl in it's upstream dependency listing. e.g. $ pkg_info -R p5-Mail-SpamAssassin-3.3.2_8 Information for p5-Mail-SpamAssassin-3.3.2_8: $ How can I fix this? Short of deleting all the packages (which I don't even know all they are, except for the p5-ones) and rebuilding? Thanks in advance, Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: p5-Bit-Vector SHA256 Checksum mismatch (was PERL problem installing SQLgrey)
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 across the same problem using portupgrade the other day, this was actually a few weeks ago. My solution was to delete Bit-Vector-* from /usr/ports/distfiles and retry the portupgrade operation. The Bit-Vector-7.2.tar.gz file on my system is dated 2012-05-17T13:32:09+, has a size of 135586 bytes, and produce this SHA256 hash: SHA256 (Bit-Vector-7.2.tar.gz) = d60630f0eb033edabfe904416c6e7324fefff13699e97302361d1bad80f62e0f This seem consistent with the contents of the distinfo file. Make sure Bit-Vector-7.2.tar.gz is the only file in the distfiles directory with filenames beginning with "Bit-Vector-7.2". > Here the log from poudriere: # cat p5-Bit-Vector-7.2_2.log > > build started at Fri Mar 1 12:38:24 CET 2013 > port directory: /usr/ports/math/p5-Bit-Vector > building for: 9.1-RELEASE amd64 > maintained by: to...@freebsd.org > Makefile ident: $FreeBSD: ports/math/p5-Bit-Vector/Makefile,v 1.22 > 2013/01/22 09:50:13 svnexp Exp $ > ---Begin Environment--- > OSVERSION=901000 > UNAME_v=FreeBSD 9.1-RELEASE > UNAME_r=9.1-RELEASE > BLOCKSIZE=K > MAIL=/var/mail/root > PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/root/bin > STATUS=1 > PKG_EXT=txz > WITH_CCACHE_BUILD=yes > FORCE_PACKAGE=yes > tpid=15131 > POUDRIERE_BUILD_TYPE=bulk > PKGNG=1 > PKG_DELETE=/usr/local/sbin/pkg delete -y -f > PKG_ADD=/usr/local/sbin/pkg add > CCACHE_DIR=/var/cache/ccache > PWD=/mnt/system/DATEN/poudriere/basefs/data/logs/bulk/91amd64/hostportstree > LOGS=/mnt/system/DATEN/poudriere/basefs/data/logs > HOME=/root > USER=root > SKIPSANITY=0 > LOCALBASE=/usr/local > PACKAGE_BUILDING=yes > ---End Environment--- > > ---Begin OPTIONS List--- > ---End OPTIONS List--- > = > ===> p5-Bit-Vector-7.2_2 depends on file: /usr/local/sbin/pkg - not found > ===>Verifying install for /usr/local/sbin/pkg in /usr/ports/ports-mgmt/pkg > ===> Installing existing package /usr/ports/packages/All/pkg-1.0.8.txz > Installing pkg-1.0.8... done > If you are upgrading from the old package format, first run: > > # pkg2ng > ===> Returning to build of p5-Bit-Vector-7.2_2 > ===> p5-Bit-Vector-7.2_2 depends on file: /usr/local/bin/perl5.14.2 - not > found > ===>Verifying install for /usr/local/bin/perl5.14.2 in > /usr/ports/lang/perl5.14 > ===> Installing existing package /usr/ports/packages/All/perl-5.14.2_2.txz > Installing perl-5.14.2_2...Removing stale symlinks from /usr/bin... > Skipping /usr/bin/perl > Skipping /usr/bin/perl5 > Done. > Creating various symlinks in /usr/bin... > Symlinking /usr/local/bin/perl5.14.2 to /usr/bin/perl > Symlinking /usr/local/bin/perl5.14.2 to /usr/bin/perl5 > Done. > Cleaning up /etc/make.conf... Done. > Spamming /etc/make.conf... Done. > done > ===> Returning to build of p5-Bit-Vector-7.2_2 > ===> p5-Bit-Vector-7.2_2 depends on file: /usr/local/bin/perl5.14.2 - found > ===> p5-Bit-Vector-7.2_2 depends on package: p5-Carp-Clan>=0 - not found > ===>Verifying install for p5-Carp-Clan>=0 in /usr/ports/devel/p5-Carp-Clan > ===> Installing existing package > /usr/ports/packages/All/p5-Carp-Clan-6.04.txz > Installing p5-Carp-Clan-6.04... done > ===> Returning to build of p5-Bit-Vector-7.2_2 > ===> p5-Bit-Vector-7.2_2 depends on file: /usr/local/bin/perl5.14.2 - found > ===> p5-Bit-Vector-7.2_2 depends on file: /usr/local/bin/ccache - not found > ===>Verifying install for /usr/local/bin/ccache in /usr/ports/devel/ccache > ===> Installing existing package /usr/ports/packages/All/ccache-3.1.9.txz > Installing ccache-3.1.9...Create compiler links... > create symlink for cc > create symlink for cc (world) > create symlink for c++ > create symlink for c++ (world) > create symlink for gcc > create symlink for gcc (world) > create symlink for g++ > create symlink for g++ (world) > create symlink for clang > create symlink for clang (world) > create symlink for clang++ > create symlink for clang++ (world) > done > > NOTE: > Please read /usr/local/share/doc/ccache/ccache-howto-freebsd.txt for > information on using ccache with FreeBSD ports and src. > ===> Returning to build of p5-Bit-Vector-7.2_2 > == > ===> Cleaning for p5-Bit-Vector-7.2_2 > ==
p5-Bit-Vector SHA256 Checksum mismatch (was PERL problem installing SQLgrey)
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, and it is correct. Here the log from poudriere: # cat p5-Bit-Vector-7.2_2.log build started at Fri Mar 1 12:38:24 CET 2013 port directory: /usr/ports/math/p5-Bit-Vector building for: 9.1-RELEASE amd64 maintained by: to...@freebsd.org Makefile ident: $FreeBSD: ports/math/p5-Bit-Vector/Makefile,v 1.22 2013/01/22 09:50:13 svnexp Exp $ ---Begin Environment--- OSVERSION=901000 UNAME_v=FreeBSD 9.1-RELEASE UNAME_r=9.1-RELEASE BLOCKSIZE=K MAIL=/var/mail/root PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/root/bin STATUS=1 PKG_EXT=txz WITH_CCACHE_BUILD=yes FORCE_PACKAGE=yes tpid=15131 POUDRIERE_BUILD_TYPE=bulk PKGNG=1 PKG_DELETE=/usr/local/sbin/pkg delete -y -f PKG_ADD=/usr/local/sbin/pkg add CCACHE_DIR=/var/cache/ccache PWD=/mnt/system/DATEN/poudriere/basefs/data/logs/bulk/91amd64/hostportstree LOGS=/mnt/system/DATEN/poudriere/basefs/data/logs HOME=/root USER=root SKIPSANITY=0 LOCALBASE=/usr/local PACKAGE_BUILDING=yes ---End Environment--- ---Begin OPTIONS List--- ---End OPTIONS List--- = ===> p5-Bit-Vector-7.2_2 depends on file: /usr/local/sbin/pkg - not found ===>Verifying install for /usr/local/sbin/pkg in /usr/ports/ports-mgmt/pkg ===> Installing existing package /usr/ports/packages/All/pkg-1.0.8.txz Installing pkg-1.0.8... done If you are upgrading from the old package format, first run: # pkg2ng ===> Returning to build of p5-Bit-Vector-7.2_2 ===> p5-Bit-Vector-7.2_2 depends on file: /usr/local/bin/perl5.14.2 - not found ===>Verifying install for /usr/local/bin/perl5.14.2 in /usr/ports/lang/perl5.14 ===> Installing existing package /usr/ports/packages/All/perl-5.14.2_2.txz Installing perl-5.14.2_2...Removing stale symlinks from /usr/bin... Skipping /usr/bin/perl Skipping /usr/bin/perl5 Done. Creating various symlinks in /usr/bin... Symlinking /usr/local/bin/perl5.14.2 to /usr/bin/perl Symlinking /usr/local/bin/perl5.14.2 to /usr/bin/perl5 Done. Cleaning up /etc/make.conf... Done. Spamming /etc/make.conf... Done. done ===> Returning to build of p5-Bit-Vector-7.2_2 ===> p5-Bit-Vector-7.2_2 depends on file: /usr/local/bin/perl5.14.2 - found ===> p5-Bit-Vector-7.2_2 depends on package: p5-Carp-Clan>=0 - not found ===>Verifying install for p5-Carp-Clan>=0 in /usr/ports/devel/p5-Carp-Clan ===> Installing existing package /usr/ports/packages/All/p5-Carp-Clan-6.04.txz Installing p5-Carp-Clan-6.04... done ===> Returning to build of p5-Bit-Vector-7.2_2 ===> p5-Bit-Vector-7.2_2 depends on file: /usr/local/bin/perl5.14.2 - found ===> p5-Bit-Vector-7.2_2 depends on file: /usr/local/bin/ccache - not found ===>Verifying install for /usr/local/bin/ccache in /usr/ports/devel/ccache ===> Installing existing package /usr/ports/packages/All/ccache-3.1.9.txz Installing ccache-3.1.9...Create compiler links... create symlink for cc create symlink for cc (world) create symlink for c++ create symlink for c++ (world) create symlink for gcc create symlink for gcc (world) create symlink for g++ create symlink for g++ (world) create symlink for clang create symlink for clang (world) create symlink for clang++ create symlink for clang++ (world) done NOTE: Please read /usr/local/share/doc/ccache/ccache-howto-freebsd.txt for information on using ccache with FreeBSD ports and src. ===> Returning to build of p5-Bit-Vector-7.2_2 == ===> Cleaning for p5-Bit-Vector-7.2_2 = == = ===> p5-Bit-Vector-7.2_2 depends on file: /usr/local/sbin/pkg - found == = ===> p5-Bit-Vector-7.2_2 depends on file: /usr/local/sbin/pkg - found => SHA256 Checksum mismatch for Bit-Vector-7.2.tar.gz. ===> Refetch for 1 more times files: Bit-Vector-7.2.tar.gz ===> p5-Bit-Vector-7.2_2 depends on file: /usr/local/sbin/pkg - found => Bit-Vector-7.2.tar.gz doesn't seem to exist in /usr/ports/distfiles/. => Attempting to fetch ftp://ftp.cpan.org/pub/CPAN/modules/by-module/Bit/Bit-Vector-7.2.tar.gz fetch: ftp://ftp.cpan.org/pub/CPAN/modules/by-module/Bit/Bit-Vector-7.2.tar.gz: Unknown FTP error => Attempting to fetch http://www.cpan.dk/modules/by-module/Bit/Bit-Vector-7.2.tar.gz fetch: http://www.cpan.dk/modules/by-module/Bit/Bit-Vector-7.2.tar.gz: Requested Range Not Satisfiabl
math/p5-Bit-Vector size error (was PERL problem installing SQLgrey)
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-Calc>=0 in /usr/ports/devel/p5-Date-Calc > ===> 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-Vector-7.2.tar.gz. > > > and it can't find it anywhere else. > > bombs out with: > > fetch: > ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/Bit-Vector-7.2.tar.gz: > size mismatch: expected 135586, actual 137817 No error of that sort here (on FreeBSD 8.3-STABLE/i386 in Hawaii, USA). > => Couldn't fetch it - please try to retrieve this > => port manually into /usr/ports/distfiles/ and try again. > *** Error code 1 ... Here source was fetched from ... ftp://ftp.cpan.org/pub/CPAN/modules/by-module/Bit/Bit-Vector-7.2.tar.gz ... and port was built without fatal errors (lots of "warning: cast to pointer from integer of different size" though). -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: PERL problem installing SQLgrey
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-Vector-7.2.tar.gz. > > > and it can't find it anywhere else. > > bombs out with: > > fetch: > ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/Bit-Vector-7.2.tar.gz: > size mismatch: expected 135586, actual 137817 > => Couldn't fetch it - please try to retrieve this > => port manually into /usr/ports/distfiles/ and try again. > *** Error code 1 Did you try updating your ports to the latest and: cd /usr/ports/math/p5-Bit-Vector make distclean and then try and install sqlgrey again? If you get the same error repeatably, then it's possibly a bug in the p5-Bit-Vector port -- perhaps the distfile was changed, in which case the port maintainer would have to update the distinfo to match. In any case, if you're still having problems, please ask again on freebsd-po...@freebsd.org Cheers, Matthew ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
PERL problem installing SQLgrey
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 depends on package: p5-Pod-Parser>=0 - found ===> sqlgrey-1.8.0 depends on package: p5-DBD-mysql>=0 - found ===> sqlgrey-1.8.0 depends on package: p5-Date-Calc>=0 - not found ===>Verifying install for p5-Date-Calc>=0 in /usr/ports/devel/p5-Date-Calc ===> 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-Vector-7.2.tar.gz. and it can't find it anywhere else. bombs out with: fetch: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/Bit-Vector-7.2.tar.gz: size mismatch: expected 135586, actual 137817 => Couldn't fetch it - please try to retrieve this => port manually into /usr/ports/distfiles/ and try again. *** Error code 1 Stop in /usr/ports/math/p5-Bit-Vector. *** Error code 1 Stop in /usr/ports/math/p5-Bit-Vector. *** Error code 1 Stop in /usr/ports/devel/p5-Date-Calc. *** Error code 1 Stop in /usr/ports/mail/sqlgrey. *** Error code 1 but: cpanm Date::Calc Date::Calc is up to date. (6.3) cpanm Bit::Vector Bit::Vector is up to date. (7.2) thanks Len ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Mapping Perl module names to corresponding FreeBSD port names
I am, at long last, moving my main system over onto a new drive where I have just installed a fresh copy of 9.1-RELEASE, and where I have built and installed essentially all of the ports I had on my old (8.3-RELEASE) system... at least the ones that I am actually still actively using. A problem arises however in the case of the various p5-* (Perl) ports that I have installed on my old 8.3 system. How can I know which of these I really need to install on my new 9.1 system, you know, in order to make sure that all of my existing/old Perl scripts will continue to function? pkg_info says that I currently have 84 different p5-* ports installed on my old 8.3 system. The list of these is attached below. (I suspect that many/most of these I installed temporarily, just for some one-off task, and that I no longer need to have them installed, e.g. on my new system.) I keep all of my personal scripts and compiled programs in a directory I call /usr/local/rfg/bin. I have gone into that directory and done: grep '^use ' | sort -u in order to find all the the Perl module names that my various personal Perl scripts are using. The result is the following (which has been trimmed a bit to remove irrelevant fluff): use CGI::Lite; use Cwd; use Email::MIME; use Encode; use HTML::TreeBuilder; use IO::Handle; use LWP::Simple; use List::Util qw(min max); use Net::CIDR::Lite; use Net::DNS; use Time::localtime; use URI::Escape; So basically, on my new system, I need to install all of the p5-* FreeBSD ports that correspond to the above set of Perl modules. In order to do this, I need to somehow derive the corresponding FreeBSD p5-* port names from the Perl module names listed above. In some cases, the mapping is both straightforward and obvious, e.g.: CGI::Lite => p5-CGI-Lite Email::MIME => p5-Email-MIME Net::DNS=> p5-Net-DNS however in many other cases the correct mapping is not immediately obvious. So, I need to ask: Is there some simple automated way to map each of the above Perl module names into a corresponding FreeBSD p5-* port name? If not, is there a map published somewhere that I could just refer to in order to find the name of the specific FreeBSD port that corresponds to any given (CPAN-published) Perl module? List of currently installed p5-* packages = p5-AnyEvent p5-Authen-NTLM p5-CGI-Lite p5-CPAN-Meta p5-CPAN-Meta-Requirements p5-CPAN-Meta-YAML p5-Cairo p5-Compress-Raw-Bzip2 p5-Compress-Raw-Zlib p5-Convert-BinHex p5-Digest-HMAC p5-Email-Address p5-Email-Date-Format p5-Email-MIME p5-Email-MIME-ContentType p5-Email-MIME-Encodings p5-Email-MessageID p5-Email-Simple p5-Encode-Locale p5-Event p5-Event-ExecFlow p5-Event-RPC p5-ExtUtils-CBuilder p5-ExtUtils-Depends p5-ExtUtils-ParseXS p5-ExtUtils-PkgConfig p5-File-Listing p5-Font-AFM p5-Glib2 p5-Gtk2 p5-Gtk2-Ex-FormFactory p5-Gtk2-Ex-Simple-List p5-HTML-Form p5-HTML-Format p5-HTML-Parser p5-HTML-Tagset p5-HTML-Tree p5-HTTP-Cookies p5-HTTP-Daemon p5-HTTP-Date p5-HTTP-Message p5-HTTP-Negotiate p5-HTTP-Server-Simple p5-IO-Compress p5-IO-Socket-INET6 p5-IO-Socket-SSL p5-IO-stringy p5-JSON-PP p5-LWP-MediaTypes p5-Lchown p5-Locale-gettext p5-Locale-libintl p5-MIME-Base64 p5-MIME-Tools p5-MIME-Types p5-Mail-Tools p5-Module-Build p5-Module-Metadata p5-Net-CIDR-Lite p5-Net-DNS p5-Net-HTTP p5-Net-IP p5-Net-LibIDN p5-Net-SSLeay p5-Pango p5-Parse-CPAN-Meta p5-Perl-OSType p5-Socket6 p5-Storable p5-TimeDate p5-URI p5-Unicode-Map8 p5-Unicode-String p5-WWW-Mechanize p5-WWW-RobotRules p5-XML-NamespaceSupport p5-XML-Parser p5-XML-SAX p5-XML-SAX-Base p5-XML-SAX-Expat p5-XML-Simple p5-libwww p5-type1inst p5-version ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: poudriere upgade perl in jail
On 12/22/12 17:08, Patrick Lamaiziere wrote: Le Sat, 22 Dec 2012 16:56:09 +0100, Bas Smeelen a écrit : I have poudriere setup on a server to compile packages for my old laptop, mini, and some friends laptops and it works great. How can I upgrade the perl version of the poudriere jail to perl-5.16, it is now perl-5.14? I tried startied the jail with poudriere jail -s -j and then try jail command=portmaster -o lang/perl5.16 lang/perl5.14 but can't get this to work. Should I just wipe the jail, then recreate and first build perl5.16 in it before building the other packages? I think PERL_VERSION=5.16.X in the poudriere jail's make.conf will do the trick. Then you will have to rebuild all the poudriere packages (not sure if this is safe else) Alright. Thanks! That did it. It looks like it deleted all perl5.14 dependent packages and is rebuilding them now with perl5.16.2 Great :) Maybe I should have asked the question before spending a day figuring out how. Merci beaucoup. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: poudriere upgade perl in jail
Le Sat, 22 Dec 2012 16:56:09 +0100, Bas Smeelen a écrit : > I have poudriere setup on a server to compile packages for my old > laptop, mini, and some friends laptops and it works great. > > How can I upgrade the perl version of the poudriere jail to > perl-5.16, it is now perl-5.14? > > I tried startied the jail with poudriere jail -s -j and then try jail > command=portmaster -o lang/perl5.16 lang/perl5.14 but can't get this > to work. > > Should I just wipe the jail, then recreate and first build perl5.16 > in it before building the other packages? I think PERL_VERSION=5.16.X in the poudriere jail's make.conf will do the trick. Then you will have to rebuild all the poudriere packages (not sure if this is safe else) Regards. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
poudriere upgade perl in jail
I have poudriere setup on a server to compile packages for my old laptop, mini, and some friends laptops and it works great. How can I upgrade the perl version of the poudriere jail to perl-5.16, it is now perl-5.14? I tried startied the jail with poudriere jail -s -j and then try jail command=portmaster -o lang/perl5.16 lang/perl5.14 but can't get this to work. Should I just wipe the jail, then recreate and first build perl5.16 in it before building the other packages? I have read the man pages for poudriere and jail and searched the web for this, but can't get to the right solution. Thanks in advance. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: perl, rrdtool issue
> Actually I did portupgrade -rf, and still have the issue with that > bsdpan-RRDp-0.99.0. > And because of that my munin isn't working, I'm getting email like: > > "Can't locate Munin/Common/Defaults.pm in @INC (@INC contains: It seems that you need to reinstall Munin, not RRDtool. And from the error message, it still uses Perl 5.12 Olivier > /usr/local/lib/perl5/5.12.4/BSDPAN > /usr/local/lib/perl5/site_perl/5.12.4/mach > /usr/local/lib/perl5/site_perl/5.12.4 /usr/local/lib/perl5/5.12.4/mach > /usr/local/lib/perl5/5.12.4 .) at > /usr/local/lib/perl5/site_perl/5.12.4/Munin/Master/Update.pm line 14." > > > On 2012 November 15 Thursday at 8:37 AM, Olivier Nicole wrote: > > Laszlo, > > Yesterday I issued the following command which I regretted: portupgrade > -CPy, and this little tool installed perl 5.12 while perl 5.10 was already > on the system. Since then everything is messed up. > Now I deleted perl 5.10 and reinstalled perl 5.10 and everything which > depends on it and still have the following error: > > > What I usually do is upgrading every Perl packages after I upgraded Perl. > > Something like portupgrade -R perl should do. > > Or do it manually, one port at a time if you are afraid to break something > else. > > For having done it recently, from perl to rrdtool it's less than 10 > ports to get it back working. > > best regards, > > olivier > > # portversion -v > [Updating the pkgdb in /var/db/pkg ... - 626 packages > found (-1 +0) (...) done] > Stale dependency: bsdpan-RRDp-0.99.0 --> perl-5.10.1_7 -- manually run > 'pkgdb -F' to fix, or specify -O to force. > > I tried pkgdb -F but it can't fix, also tried to delete rrdtool and > reinstall, but still the same issue. I'm running 8.3-RELEASE-p3. > > Do you have any idea how to solve this issue? > > Thx! > Laszlo > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" > > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: perl, rrdtool issue
Actually I did portupgrade -rf, and still have the issue with that bsdpan-RRDp-0.99.0. And because of that my munin isn't working, I'm getting email like: "Can't locate Munin/Common/Defaults.pm in @INC (@INC contains: /usr/local/lib/perl5/5.12.4/BSDPAN /usr/local/lib/perl5/site_perl/5.12.4/mach /usr/local/lib/perl5/site_perl/5.12.4 /usr/local/lib/perl5/5.12.4/mach /usr/local/lib/perl5/5.12.4 .) at /usr/local/lib/perl5/site_perl/5.12.4/Munin/Master/Update.pm line 14." On 2012 November 15 Thursday at 8:37 AM, Olivier Nicole wrote: > Laszlo, > > > Yesterday I issued the following command which I regretted: portupgrade > > -CPy, and this little tool installed perl 5.12 while perl 5.10 was already > > on the system. Since then everything is messed up. > > Now I deleted perl 5.10 and reinstalled perl 5.10 and everything which > > depends on it and still have the following error: > > > > > What I usually do is upgrading every Perl packages after I upgraded Perl. > > Something like portupgrade -R perl should do. > > Or do it manually, one port at a time if you are afraid to break something > else. > > For having done it recently, from perl to rrdtool it's less than 10 > ports to get it back working. > > best regards, > > olivier > > > # portversion -v > > [Updating the pkgdb in /var/db/pkg ... - 626 packages > > found (-1 +0) (...) done] > > Stale dependency: bsdpan-RRDp-0.99.0 --> perl-5.10.1_7 -- manually run > > 'pkgdb -F' to fix, or specify -O to force. > > > > I tried pkgdb -F but it can't fix, also tried to delete rrdtool and > > reinstall, but still the same issue. I'm running 8.3-RELEASE-p3. > > > > Do you have any idea how to solve this issue? > > > > Thx! > > Laszlo > > ___ > > freebsd-questions@freebsd.org (mailto:freebsd-questions@freebsd.org) > > mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org > > (mailto:freebsd-questions-unsubscr...@freebsd.org)" > > > > ___ > freebsd-questions@freebsd.org (mailto:freebsd-questions@freebsd.org) mailing > list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org > (mailto:freebsd-questions-unsubscr...@freebsd.org)" > > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: perl, rrdtool issue
Laszlo, > Yesterday I issued the following command which I regretted: portupgrade -CPy, > and this little tool installed perl 5.12 while perl 5.10 was already on the > system. Since then everything is messed up. > Now I deleted perl 5.10 and reinstalled perl 5.10 and everything which > depends on it and still have the following error: What I usually do is upgrading every Perl packages after I upgraded Perl. Something like portupgrade -R perl should do. Or do it manually, one port at a time if you are afraid to break something else. For having done it recently, from perl to rrdtool it's less than 10 ports to get it back working. best regards, olivier > # portversion -v > [Updating the pkgdb in /var/db/pkg ... - 626 packages > found (-1 +0) (...) done] > Stale dependency: bsdpan-RRDp-0.99.0 --> perl-5.10.1_7 -- manually run 'pkgdb > -F' to fix, or specify -O to force. > > I tried pkgdb -F but it can't fix, also tried to delete rrdtool and > reinstall, but still the same issue. I'm running 8.3-RELEASE-p3. > > Do you have any idea how to solve this issue? > > Thx! > Laszlo > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
perl, rrdtool issue
Hi Guys, Yesterday I issued the following command which I regretted: portupgrade -CPy, and this little tool installed perl 5.12 while perl 5.10 was already on the system. Since then everything is messed up. Now I deleted perl 5.10 and reinstalled perl 5.10 and everything which depends on it and still have the following error: # portversion -v [Updating the pkgdb in /var/db/pkg ... - 626 packages found (-1 +0) (...) done] Stale dependency: bsdpan-RRDp-0.99.0 --> perl-5.10.1_7 -- manually run 'pkgdb -F' to fix, or specify -O to force. I tried pkgdb -F but it can't fix, also tried to delete rrdtool and reinstall, but still the same issue. I'm running 8.3-RELEASE-p3. Do you have any idea how to solve this issue? Thx! Laszlo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: make print-index error: Generating INDEX-9 - please wait..perl: not found
On 28/09/2012 21:27, Ed Flecko wrote: > Generating INDEX-9 - please wait..perl: not found > "Makefile", line 31: warning: "perl -V:archname" returned non-zero status > perl: not found > Done. > > O.K., I'm stumped...what's wrong? You need to install perl in order to build an INDEX from scratch. That's true if you use the default 'make index' target or my p5-FreeBSD-Portindex code. Building an INDEX is a fairly time consuming task, and honestly, most people don't need to do it. You can download a pre-built INDEX by 'make fetchindex' which will be perfectly adequate for the vast majority of users. What you don't get by using the pre-built INDEX is the effect of any local customizations or options settings. This means that the INDEX may disagree in detail about exactly what dependencies some ports have. However, the INDEX is not used as part of actually building anything, so those discrepancies are mere annoyances rather than real obstacles. And, indeed, you can build and install ports very happily without any sort of INDEX on your system at all. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
make print-index error: Generating INDEX-9 - please wait..perl: not found
I've done a clean install of FBSD 9, installed subversion from package, and then I have: svn co svn://svn.freebsd.org/ports/head/ /usr/ports svn co svn://svn.freebsd.org/base/releng/9.1 /usr/src svn co svn://svn.freebsd.org/doc/release/9.1.0/en_US.ISO8859-1 /usr/doc which all went just fine. Then I: cd /usr/ports make print-index and this is my result: Generating INDEX-9 - please wait..perl: not found "Makefile", line 31: warning: "perl -V:archname" returned non-zero status perl: not found Done. O.K., I'm stumped...what's wrong? Ed ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Upgrading perl
On 8/29/2012 1:32 PM, Lowell Gilbert wrote: Jack Stone 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 them to you. Wonder if I just deinstalled the old perl5-5.10 and then installed the perl5-12 would work. I can do that right from the port: make perl5-12 first to see if that works, then: # make deinstall (perl-5.10) then: make install clean I would be surprised if the perl-5.12 port will build for you; I think you'll get the same error. If not, then yes, it should work. What do you think? I've got to move up because an important perl program requires a minimum 5.12. Well, it's also possible that there's a local problem on that machine. You indicated that you used portupgrade for similar updates on similarly-aged machines, but I'll guess that they were only roughly similar. I'll guess that you built your own INDEX file; if not, you probably should (and the associated database for portupgrade). Compare the infrastructure in ports/Mk (and maybe /usr/share/mk) with the similar machines that succeeded, and look at the Makefile in perl5.12 to make sure it sets options properly. Good luck. AHAH! This just came out in ports UPDATING and maybe helps: 20120820: AFFECTS: users of ports-mgmt/portupgrade-devel AUTHOR: bdrew...@freebsd.org Due to a bug introduced in 20120601, portupgrade is unable to upgrade itself on FreeBSD 7.x. This has been fixed in 20120820. ports-mgmt/portupgrade is not affected. To upgrade, execute the following: # cd /usr/ports/ports-mgmt/portupgrade-devel && make deinstall install clean -- -- All the best, Jack ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Upgrading perl
On 8/29/2012 1:32 PM, Lowell Gilbert wrote: Jack Stone 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 them to you. Wonder if I just deinstalled the old perl5-5.10 and then installed the perl5-12 would work. I can do that right from the port: make perl5-12 first to see if that works, then: # make deinstall (perl-5.10) then: make install clean I would be surprised if the perl-5.12 port will build for you; I think you'll get the same error. If not, then yes, it should work. What do you think? I've got to move up because an important perl program requires a minimum 5.12. Well, it's also possible that there's a local problem on that machine. You indicated that you used portupgrade for similar updates on similarly-aged machines, but I'll guess that they were only roughly similar. I'll guess that you built your own INDEX file; if not, you probably should (and the associated database for portupgrade). Compare the infrastructure in ports/Mk (and maybe /usr/share/mk) with the similar machines that succeeded, and look at the Makefile in perl5.12 to make sure it sets options properly. Good luck. Hi Lowell and thanks for the good wishes! Yes, on the other servers which upgraded without issue are running the same freebsd-7.x, and the make files are identical for the perl-5.12. I just now ran a test on a test server of same vintage and it did build directly in the port just using "make" to see if it would work. It did. The trick is to DISABLE_CONFLICTS=YES in the /etc/make.conf. This still doesn't mean the important production server will cooperatebut will have to take a risk and try it. That server has a bootable clone that is run every day so I can rescue the server. I will just to make a fresh clone right before I try the perl upgradeso to minimize any loss of data. -- All the best, Jack ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Upgrading perl
Jack Stone 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 them to you. > Wonder if I just deinstalled the old perl5-5.10 and then installed the > perl5-12 would work. I can do that right from the port: make perl5-12 > first to see if that works, then: > # make deinstall (perl-5.10) then: make install clean I would be surprised if the perl-5.12 port will build for you; I think you'll get the same error. If not, then yes, it should work. > What do you think? I've got to move up because an important perl > program requires a minimum 5.12. Well, it's also possible that there's a local problem on that machine. You indicated that you used portupgrade for similar updates on similarly-aged machines, but I'll guess that they were only roughly similar. I'll guess that you built your own INDEX file; if not, you probably should (and the associated database for portupgrade). Compare the infrastructure in ports/Mk (and maybe /usr/share/mk) with the similar machines that succeeded, and look at the Makefile in perl5.12 to make sure it sets options properly. Good luck. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Upgrading perl
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 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 -o lang/perl5.12 -f perl-5.10.\* >>>> >>>> That has worked on other servers, but not this one. Anyone know what I >>>> need to do to clean this up?? >>>> >>>> But, can't get past this fatal error: >>>> mail# portupgrade -o lang/perl5.12 -f perl-5.10.\* >>>> "/usr/ports/Mk/bsd.options.mk", line 231: Error in archive >>>> specification: "WITHOUT_" >>>> "/usr/ports/Mk/bsd.options.mk", line 231: Error in archive >>>> specification: "WITHOUT_" >>>> make: fatal errors encountered -- cannot continue >>>> ** Makefile possibly broken: lang/perl5.12: >>> You're almost four years past the end-of-life on the release you're >>> running, so it's been left behind in terms of support. In this case it >>> looks (based on a *very* quick look) that you may be running into >>> changes in how make(1) actually works, in which case backporting the >>> ports functionality will be more work than it's worth. >>> >>> If the machine "can't" be updated, and assuming it's secure (which hard >>> to be sure about with old software on the Internet), you may be best off >>> leaving it alone. >>> >>> Good luck. >>> >>> >> Thanks for the reply. >> >> 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. >> >> Wonder if I just deinstalled the old perl5-5.10 and then installed the >> perl5-12 would work. I can do that right from the port: make perl5-12 >> first to see if that works, then: >> # make deinstall (perl-5.10) then: make install clean > > If you're using portmaster, you should be able to do something like the > following from /usr/ports: > > portmaster -o lang/perl5.16 lang/perl5.10 > portmaster p5- > > and perl automagically will upgrade. Sorry, I'd missed that you'd tried this and it isn't working. make has changed since the 7.0 days. I agree with Jack that you're better off leaving well enough alone. If you really need perl5.16+ capabilities you're much better off moving your program to a more recent version of FreeBSD. dn > > This is from /usr/ports/UPDATING. You can also find instructions for > portupgrade there. > > Don't know about dependencies with 7.0, though. > > dn > > >> >> What do you think? I've got to move up because an important perl program >> requires a minimum 5.12. > > > >> > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Upgrading perl
On 8/29/12 8:08 AM, Jack Stone wrote: > On 8/29/2012 8:27 AM, Lowell Gilbert wrote: >> Jack Stone 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 -o lang/perl5.12 -f perl-5.10.\* >>> >>> That has worked on other servers, but not this one. Anyone know what I >>> need to do to clean this up?? >>> >>> But, can't get past this fatal error: >>> mail# portupgrade -o lang/perl5.12 -f perl-5.10.\* >>> "/usr/ports/Mk/bsd.options.mk", line 231: Error in archive >>> specification: "WITHOUT_" >>> "/usr/ports/Mk/bsd.options.mk", line 231: Error in archive >>> specification: "WITHOUT_" >>> make: fatal errors encountered -- cannot continue >>> ** Makefile possibly broken: lang/perl5.12: >> You're almost four years past the end-of-life on the release you're >> running, so it's been left behind in terms of support. In this case it >> looks (based on a *very* quick look) that you may be running into >> changes in how make(1) actually works, in which case backporting the >> ports functionality will be more work than it's worth. >> >> If the machine "can't" be updated, and assuming it's secure (which hard >> to be sure about with old software on the Internet), you may be best off >> leaving it alone. >> >> Good luck. >> >> > Thanks for the reply. > > 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. > > Wonder if I just deinstalled the old perl5-5.10 and then installed the > perl5-12 would work. I can do that right from the port: make perl5-12 > first to see if that works, then: > # make deinstall (perl-5.10) then: make install clean If you're using portmaster, you should be able to do something like the following from /usr/ports: portmaster -o lang/perl5.16 lang/perl5.10 portmaster p5- and perl automagically will upgrade. This is from /usr/ports/UPDATING. You can also find instructions for portupgrade there. Don't know about dependencies with 7.0, though. dn > > What do you think? I've got to move up because an important perl program > requires a minimum 5.12. > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Upgrading perl
On 8/29/2012 8:27 AM, Lowell Gilbert wrote: Jack Stone 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 -o lang/perl5.12 -f perl-5.10.\* That has worked on other servers, but not this one. Anyone know what I need to do to clean this up?? But, can't get past this fatal error: mail# portupgrade -o lang/perl5.12 -f perl-5.10.\* "/usr/ports/Mk/bsd.options.mk", line 231: Error in archive specification: "WITHOUT_" "/usr/ports/Mk/bsd.options.mk", line 231: Error in archive specification: "WITHOUT_" make: fatal errors encountered -- cannot continue ** Makefile possibly broken: lang/perl5.12: You're almost four years past the end-of-life on the release you're running, so it's been left behind in terms of support. In this case it looks (based on a *very* quick look) that you may be running into changes in how make(1) actually works, in which case backporting the ports functionality will be more work than it's worth. If the machine "can't" be updated, and assuming it's secure (which hard to be sure about with old software on the Internet), you may be best off leaving it alone. Good luck. Thanks for the reply. 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. Wonder if I just deinstalled the old perl5-5.10 and then installed the perl5-12 would work. I can do that right from the port: make perl5-12 first to see if that works, then: # make deinstall (perl-5.10) then: make install clean What do you think? I've got to move up because an important perl program requires a minimum 5.12. -- -- All the best, Jack ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Upgrading perl
Jack Stone 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 -o lang/perl5.12 -f perl-5.10.\* > > That has worked on other servers, but not this one. Anyone know what I > need to do to clean this up?? > > But, can't get past this fatal error: > mail# portupgrade -o lang/perl5.12 -f perl-5.10.\* > "/usr/ports/Mk/bsd.options.mk", line 231: Error in archive > specification: "WITHOUT_" > "/usr/ports/Mk/bsd.options.mk", line 231: Error in archive > specification: "WITHOUT_" > make: fatal errors encountered -- cannot continue > ** Makefile possibly broken: lang/perl5.12: You're almost four years past the end-of-life on the release you're running, so it's been left behind in terms of support. In this case it looks (based on a *very* quick look) that you may be running into changes in how make(1) actually works, in which case backporting the ports functionality will be more work than it's worth. If the machine "can't" be updated, and assuming it's secure (which hard to be sure about with old software on the Internet), you may be best off leaving it alone. Good luck. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Upgrading perl
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 worked on other servers, but not this one. Anyone know what I need to do to clean this up?? But, can't get past this fatal error: mail# portupgrade -o lang/perl5.12 -f perl-5.10.\* "/usr/ports/Mk/bsd.options.mk", line 231: Error in archive specification: "WITHOUT_" "/usr/ports/Mk/bsd.options.mk", line 231: Error in archive specification: "WITHOUT_" make: fatal errors encountered -- cannot continue ** Makefile possibly broken: lang/perl5.12: ** Please report this to the maintainer for lang/perl5.12 No closing parenthesis in archive specification No closing parenthesis in archive specification /usr/local/sbin/portupgrade:1560:in `get_pkgname': Makefile broken (MakefileBrokenError) from /usr/local/sbin/portupgrade:631:in `block (4 levels) in main' from /usr/local/sbin/portupgrade:615:in `each' from /usr/local/sbin/portupgrade:615:in `block (3 levels) in main' from /usr/local/sbin/portupgrade:588:in `catch' from /usr/local/sbin/portupgrade:588:in `block (2 levels) in main' from /usr/local/lib/ruby/1.9/optparse.rb:1404:in `call' from /usr/local/lib/ruby/1.9/optparse.rb:1404:in `block (2 levels) in parse_in_order' from /usr/local/lib/ruby/1.9/optparse.rb:1399:in `catch' from /usr/local/lib/ruby/1.9/optparse.rb:1399:in `block in parse_in_order' from /usr/local/lib/ruby/1.9/optparse.rb:1347:in `catch' from /usr/local/lib/ruby/1.9/optparse.rb:1347:in `parse_in_order' from /usr/local/lib/ruby/1.9/optparse.rb:1341:in `order!' from /usr/local/lib/ruby/1.9/optparse.rb:1334:in `order' from /usr/local/sbin/portupgrade:565:in `block in main' from /usr/local/lib/ruby/1.9/optparse.rb:882:in `initialize' from /usr/local/sbin/portupgrade:236:in `new' from /usr/local/sbin/portupgrade:236:in `main' from /usr/local/sbin/portupgrade:2344:in `' All the best, Jack ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
JAIL - building perl 5.1? fails on 8.2-STABLE
Hello list,
I'm trying to build perl5.12 in a jail running on 8.2-STABLE, to
ultimately build php5.
I'm getting the following error:
Running Mkbootstrap for threads::shared ()
chmod 644 shared.bs
rm -f ../../lib/auto/threads/shared/shared.so
cc -shared -L/usr/local/lib -fstack-protector shared.o -o
../../lib/auto/threads/shared/shared.so
chmod 755 ../../lib/auto/threads/shared/shared.so
cp shared.bs ../../lib/auto/threads/shared/shared.bs
chmod 644 ../../lib/auto/threads/shared/shared.bs
LD_LIBRARY_PATH=/s/portbuild/usr/ports/lang/perl5.12/work/perl-5.12.4
./perl -f -Ilib pod/buildtoc --build-toc -q
LD_LIBRARY_PATH=/s/portbuild/usr/ports/lang/perl5.12/work/perl-5.12.4
./miniperl -Ilib minimod.pl > lib/ExtUtils/Miniperl.pm
cd x2p;
LD_LIBRARY_PATH=/s/portbuild/usr/ports/lang/perl5.12/work/perl-5.12.4
make s2p
"makefile", line 163: Need an operator
"makefile", line 166: Need an operator
No closing parenthesis in archive specification
There are a LOT MORE of these:
"makefile", line XXX: Need an operator
See the pastebin below for the full list:
http://pastebin.com/qAk4qXte
I've also tried perl5.10 and am getting the same errors:
written lib/Config.pod
updated lib/Config.pm
updated lib/Config_heavy.pl
LD_LIBRARY_PATH=/s/portbuild/usr/ports/lang/perl5.10/work/perl-5.10.1
./miniperl -Ilib lib/lib_pm.PL
Extracting lib.pm (with variable substitutions)
AutoSplitting perl library
LD_LIBRARY_PATH=/s/portbuild/usr/ports/lang/perl5.10/work/perl-5.10.1
./miniperl -Ilib -MAutoSplit -MFile::Find -e 'find ({no_chdir=>1, wanted
=> sub {autosplit_lib_modules($_) if /\.pm$/}}, "lib")'
make lib/re.pm
"makefile", line 1050: Need an operator
"makefile", line 1053: Need an operator
The jail's world was built and installed yesterday, although I can't
really tell when I last csup'd, possibly last week.
The config for perl5.12 is:
PERL_64BITINT
PTHREAD
USE_PERL
These are the mounts, seen from the host:
data/jail on /data/jail (zfs, local, nfsv4acls)
/data/jail/j/mroot on /data/jail/j/nanaya (nullfs, local, read-only)
/data/jail/js/nanaya on /data/jail/j/nanaya/s (nullfs, local)
The mount seen from the jail:
/data/jail/j/mroot on / (nullfs, local, read-only)
Anyone ever run into this kind of problem ?
I have to say I followed the procedure from the handbook regarding
having 1 "template" readonly jail with the world, and separate jails
with readwrite portions (etc, ports build...).
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: OT: perl mail problems
On 01/29/12 18:56, Matthew Seaman wrote: On 29/01/2012 08:11, Da Rock wrote: Thanks for the help guys. I've stepped away from php for security reasons; and the fact that I can integrate perl right into apache with mod_perl. Verb. Sap. Checkout PSGI if you're doing web-based perl things. See http://plackperl.org/ It means you can code up your web app using the Plack API using a simple built-in HTTP server and then deploy to your production systems using full-on mod_perl and apache. Or mod_psgi and apache. Or any one of about twenty different combinations -- whatever web server, plugin module, toolkit, etc. you already have deployed. Thanks Matthew. I'll look into that at some point, but I'm not entirely sure it will be necessary in my situation. I finally decided to scrap Mail::Box and go with Mail::IMAPClient instead as suggested (I didn't even bother with the workaround), and it worked immediately! So I'm stoked... much simpler to use. Should have called it Mail::IMAPSimple instead :) All that googling for nought! Mail::IMAPClient never really came up as a contender when searching perl imap - it was all about Mail::Box. Weird... Cheers ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: OT: perl mail problems
Matthew Seaman wrote: > Anything that works by connecting to an IMAP server and > downloading all the new messages to hold and read locally > really is missing the point. ... or is working around administrative issues, e.g. the mail recipient wants the mail stored locally, and the mail-server provides IMAP but not POP. BTW fetchmail is the canonical (although not the only) solution to this problem. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: OT: perl mail problems
On 29/01/2012 08:11, Da Rock wrote: > Thanks for the help guys. I've stepped away from php for security > reasons; and the fact that I can integrate perl right into apache with > mod_perl. Verb. Sap. Checkout PSGI if you're doing web-based perl things. See http://plackperl.org/ It means you can code up your web app using the Plack API using a simple built-in HTTP server and then deploy to your production systems using full-on mod_perl and apache. Or mod_psgi and apache. Or any one of about twenty different combinations -- whatever web server, plugin module, toolkit, etc. you already have deployed. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: OT: perl mail problems
On 01/29/12 02:13, Matthew Seaman wrote: On 28/01/2012 13:39, Da Rock wrote: I know this is not exactly FreeBSD related, but I'm in need of a monk that can enlighten me on a sacred incantation to connect perl to an imap server using Mail::Box modules :) If it helps people sleep, its all running only on FreeBSD systems... I have googled and searched, and googled some more, and tested, and then went back to the drawing board and googled yet again... there is simply no clear answer out there. All the docs are very disjointed from my reckoning- with no clear direction that explains how you get from a-b. I have enabled a connection (I think - based on my tests and logs), but I cannot get further than that. I have a Mail::Box::Manager instantiated, and then I have to use Mail::Box::IMAP4 to open a connection to the server. From there I need to get a list of the folders available- and thats where I get stymied. All the docs are pop3 based, or maildir based, or mbox. The imap is very sketchy... and what is out there says to basically connect, and then there is a jump to folders and messages with no idea of what is involved in between. Although I did see one complete example with pop3, but it won't work for imap. This is absolutely typical -- IMAP is frequently treated as POP-with-extra-bits, which really makes no sense whatsoever. There's a fundamental difference in behaviour to do with where the mail is actually stored. Anything that works by connecting to an IMAP server and downloading all the new messages to hold and read locally really is missing the point. I think there is a genuine effort to help make it easier to use and to abstract the backend, but it doesn't seem the coder has a handle on it themselves. They seem more familiar with filesystem based mail then the network ones- and then familiarity with pop3 rules. Therefore me, as a newb, has next to no hope of figuring it out... :/ One of the biggest problems is the username confuses any other module method than the Mail::Box::IMAP4 - the syntax is user@domain, and so if I use Mail::Box::Manager it will compile it into a url form ie imap4://user@domain:password@mail.server which it obviously barfs on and refuses to look beyond user@domain. Yeah, IMAP4 doesn't do URL-style things itself, so this is a fiction invented to appease the higher layers of Mail::Box. Unfortunately, '@' is of syntactic significance to URL schemes, making it difficult to incorporate usernames containing it. Hmmm can you substitute a hex encoded character string in that username? %40 should be the encoding for an @ character. That could work... I might have a crack at that. I thought pop3 would have trouble as well, you can use that username structure there too. I really seem to be missing something fundamental here. I'm only trying to create some tools which will handle some situations apparently only local to my systems, and improve my perl foo before I start creating modules of my own and testing mod_perl. If someone can help clear this up I'll be happy to communicate off list if that is necessary. Is all the e-mail you have to deal with stored on your IMAP4 server? If so, then using Mail::IMAPClient directly[*] might serve you better rather than through the Mail::Box and Mail::Transport classes. However, that's a much lower level interface and you'll need to be fairly au-fait with RFC 3501. (That's not as bad as it sounds: all it boils down to is finding what the command is called in the IMAP protocol when you want to achieve a particular effect.) Yes... I was dreading that a bit, but it does seem easier. I was hoping it would be more like Email::Simple, but it doesn't seem to be there yet. That said, I'll try that trick and see if it works first. One thing that I notice on a cursory reading of Mail::Box::IMAP4 is that it seems to assume things about the behaviour of the IMAP message store which aren't necessarily true for all different IMAP servers. (ICBW -- it was a /very/ cursory reading.) Usernames of the form 'n...@example.com' are one of those things you can do with IMAP which tend to come as a bit of a surprise to people used to other mailclient protocols. It seems to make some assumptions based on common uses, and I believe it said you can override others; but yes it is also "still under development" - a note which appears and disappears from time to time :S Thanks for the help guys. I've stepped away from php for security reasons; and the fact that I can integrate perl right into apache with mod_perl. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: OT: perl mail problems
On 28/01/2012 13:39, Da Rock wrote: I know this is not exactly FreeBSD related, but I'm in need of a monk that can enlighten me on a sacred incantation to connect perl to an imap server using Mail::Box modules :) If it helps people sleep, its all running only on FreeBSD systems... I have googled and searched, and googled some more, and tested, and then went back to the drawing board and googled yet again... there is simply no clear answer out there. All the docs are very disjointed from my reckoning- with no clear direction that explains how you get from a-b. I have enabled a connection (I think - based on my tests and logs), but I cannot get further than that. I have a Mail::Box::Manager instantiated, and then I have to use Mail::Box::IMAP4 to open a connection to the server. From there I need to get a list of the folders available- and thats where I get stymied. All the docs are pop3 based, or maildir based, or mbox. The imap is very sketchy... and what is out there says to basically connect, and then there is a jump to folders and messages with no idea of what is involved in between. Although I did see one complete example with pop3, but it won't work for imap. there's good php support for IMAP, documentation might be better http://uk.php.net/manual/en/function.imap-list.php (easily scripted via cli). Paul.. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: OT: perl mail problems
On 28/01/2012 13:39, Da Rock wrote: > I know this is not exactly FreeBSD related, but I'm in need of a monk > that can enlighten me on a sacred incantation to connect perl to an imap > server using Mail::Box modules :) If it helps people sleep, its all > running only on FreeBSD systems... > > I have googled and searched, and googled some more, and tested, and then > went back to the drawing board and googled yet again... there is simply > no clear answer out there. All the docs are very disjointed from my > reckoning- with no clear direction that explains how you get from a-b. > > I have enabled a connection (I think - based on my tests and logs), but > I cannot get further than that. I have a Mail::Box::Manager > instantiated, and then I have to use Mail::Box::IMAP4 to open a > connection to the server. From there I need to get a list of the folders > available- and thats where I get stymied. > > All the docs are pop3 based, or maildir based, or mbox. The imap is very > sketchy... and what is out there says to basically connect, and then > there is a jump to folders and messages with no idea of what is involved > in between. Although I did see one complete example with pop3, but it > won't work for imap. This is absolutely typical -- IMAP is frequently treated as POP-with-extra-bits, which really makes no sense whatsoever. There's a fundamental difference in behaviour to do with where the mail is actually stored. Anything that works by connecting to an IMAP server and downloading all the new messages to hold and read locally really is missing the point. > One of the biggest problems is the username confuses any other module > method than the Mail::Box::IMAP4 - the syntax is user@domain, and so if > I use Mail::Box::Manager it will compile it into a url form ie > imap4://user@domain:password@mail.server which it obviously barfs on and > refuses to look beyond user@domain. Yeah, IMAP4 doesn't do URL-style things itself, so this is a fiction invented to appease the higher layers of Mail::Box. Unfortunately, '@' is of syntactic significance to URL schemes, making it difficult to incorporate usernames containing it. Hmmm can you substitute a hex encoded character string in that username? %40 should be the encoding for an @ character. > I really seem to be missing something fundamental here. I'm only trying > to create some tools which will handle some situations apparently only > local to my systems, and improve my perl foo before I start creating > modules of my own and testing mod_perl. > > If someone can help clear this up I'll be happy to communicate off list > if that is necessary. Is all the e-mail you have to deal with stored on your IMAP4 server? If so, then using Mail::IMAPClient directly[*] might serve you better rather than through the Mail::Box and Mail::Transport classes. However, that's a much lower level interface and you'll need to be fairly au-fait with RFC 3501. (That's not as bad as it sounds: all it boils down to is finding what the command is called in the IMAP protocol when you want to achieve a particular effect.) One thing that I notice on a cursory reading of Mail::Box::IMAP4 is that it seems to assume things about the behaviour of the IMAP message store which aren't necessarily true for all different IMAP servers. (ICBW -- it was a /very/ cursory reading.) Usernames of the form 'n...@example.com' are one of those things you can do with IMAP which tend to come as a bit of a surprise to people used to other mailclient protocols. Cheers, Matthew [*] Mail::Box et al use Mail::IMAPClient behind the scenes. -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
OT: perl mail problems
I know this is not exactly FreeBSD related, but I'm in need of a monk that can enlighten me on a sacred incantation to connect perl to an imap server using Mail::Box modules :) If it helps people sleep, its all running only on FreeBSD systems... I have googled and searched, and googled some more, and tested, and then went back to the drawing board and googled yet again... there is simply no clear answer out there. All the docs are very disjointed from my reckoning- with no clear direction that explains how you get from a-b. I have enabled a connection (I think - based on my tests and logs), but I cannot get further than that. I have a Mail::Box::Manager instantiated, and then I have to use Mail::Box::IMAP4 to open a connection to the server. From there I need to get a list of the folders available- and thats where I get stymied. All the docs are pop3 based, or maildir based, or mbox. The imap is very sketchy... and what is out there says to basically connect, and then there is a jump to folders and messages with no idea of what is involved in between. Although I did see one complete example with pop3, but it won't work for imap. One of the biggest problems is the username confuses any other module method than the Mail::Box::IMAP4 - the syntax is user@domain, and so if I use Mail::Box::Manager it will compile it into a url form ie imap4://user@domain:password@mail.server which it obviously barfs on and refuses to look beyond user@domain. I really seem to be missing something fundamental here. I'm only trying to create some tools which will handle some situations apparently only local to my systems, and improve my perl foo before I start creating modules of my own and testing mod_perl. If someone can help clear this up I'll be happy to communicate off list if that is necessary. TIA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Perl Upgrade And Mailscanner Woes
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 need to run: > > > > # perl-after-upgrade -f > > > Aha! And the lights go on ... Nevermind. No, not "nevermind". While this seems like "upgrading for dummies", there are enough of them out there this _really_ needs to go in the upgrade message. Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Perl Upgrade And Mailscanner Woes
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 have to delete and reinstall every dependent perl
package used by Mailscanner.
Something is going wrong with your upgrade process. If you're doing a
minor version upgrade of perl (eg. from 5.x.y to 5.x.y+1), then almost
all perl modules (including XS) only need to be moved into the new
${LOCALBASE}/lib/perl5/site-perl/5.x.y+1 directory tree, which is
basically what perl-after-upgrade does.
A few packages which embed a perl interpreter would need recompiling,
but you could count those on the fingers of one hand.
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 need to run:
# perl-after-upgrade -f
Aha! And the lights go on ... Nevermind.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Perl Upgrade And Mailscanner Woes
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 reinstall every dependent perl
> package used by Mailscanner.
Something is going wrong with your upgrade process. If you're doing a
minor version upgrade of perl (eg. from 5.x.y to 5.x.y+1), then almost
all perl modules (including XS) only need to be moved into the new
${LOCALBASE}/lib/perl5/site-perl/5.x.y+1 directory tree, which is
basically what perl-after-upgrade does.
A few packages which embed a perl interpreter would need recompiling,
but you could count those on the fingers of one hand.
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 need to run:
# perl-after-upgrade -f
Then rebuild and reinstall any packages it says need rebuilding.
If it has worked properly then almost all of the contents of
${LOCALBASE}/lib/perl5/site-perl/5.x.y will be gone, and that whole
directory tree should be able to be deleted without consequence.
Of course if your update is from perl 5.x.y to 5.x+1.z then you really
do need to recompile and reinstall all perl modules and anything else
that depends on perl. perl-after-upgrade is not effective in this case.
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
JID: matt...@infracaninophile.co.uk Kent, CT11 9PW
signature.asc
Description: OpenPGP digital signature
Re: Perl Upgrade And Mailscanner Woes
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 reinstall every dependent perl > package used by Mailscanner. > > Does anyone have a better way? Hi After a major perl upgrade? portmaster -r perl- portmaster p5- portupgrade -fr perl Disclaimer: http://www.ose.nl/email ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Perl Upgrade And Mailscanner Woes
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 anyone have a better way? -- --- Tim Daneliuk ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
9.0-RC1 Perl tests fail
Thanks again for info about disabling 1394 :-) Easy. Now here's a harder one: Installing any version of Perl; I found I can install perl5.8, but my 8.2-RELEASE has a perfectly good Perl5.10. Each of my 9.0 Perl attempts perl5.10, 13 and 14 has Failed tests. Such a vast number of tests with so little info as to which feature my 98 or so failed tests comes from! CPAN shows its latest release as perl5-0.08 ! I suspect the Perl versions I've tried may be uniquely numbered for FreeBSD. Any help? Thanks for any help! Chuck Bacon -- c...@cape.com ABHOR SECRECY -- DEFEND PRIVACY ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Getting __errno_location when loading Perl XS module on FreeBSD
Hello I'm compiling a proprietary lib on FreeBSD that offers a Perl API via XS. The package comes with an ar archive for Linux 64 but I need to compile it and run it on FreeBSD. FreeBSD make process makes no complaints about the object files in the ar in the make process, and everything makes without an error. The lib compiles fine, but when the dynaloader is loading I get: /libexec/ld-elf.so.1: (undisclosed).so: Undefined symbol "__errno_location" Is this ld-elf complaining that it does not find the symbol in (undisclosed), or is it (undisclosed) not finding the symbol in it's dependencies? I've been trying to learn more about __errno_location but some say it's relates to the pthreads lib, some that it's libm and should be defined in errno.h, but nope, it's not defined in any .h in Linux or FreeBSD! As you can see, the lib build fine and satisfies all dependencies. Shouldn't the undefined symbol pop-up during linking of the shared object (during creation) instead than on dynamic linking? ldd blib/arch/auto/.so blib/arch/auto/Gateway/Gateway.so: libcurl.so.6 => /usr/local/lib/libcurl.so.6 (0x800c0) libssl.so.6 => /usr/lib/libssl.so.6 (0x800d54000) libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x800ea7000) libm.so.5 => /lib/libm.so.5 (0x8010b7000) libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x8011d7000) libc.so.7 => /lib/libc.so.7 (0x800647000) libcrypto.so.6 => /lib/libcrypto.so.6 (0x8012e5000) libz.so.5 => /lib/libz.so.5 (0x801585000) [download] Thanks in advance for any comments. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
linux-perl ?
Hi, I've been searching list archives regarding an old thread that talks about perl dbd oracle on fbsd: http://lists.freebsd.org/pipermail/freebsd-database/2006-October/000465.html My problem is not exactly the same but I need to proxy a specific proprietary perl library that uses xs and was built for linux. I agree with the conclusion of the thread, and I doubt there is a way that fbsd perl would be able to work with this lib directly. So, I was thinking of installing this "linux-perl" on compat and just proxy the lib methods via a daemon (even simple http web service) so I can use the lib through fbsd perl by mean of lwp, for example. This "linux-perl" is mentioned in the thread several times but I don't seem to find information about this anywhere else in the archive, and perl doesn't seem to be in the f10 compats either. I've STFW and I can't seem to find any other obvious reference to this linux-perl stuff. So what is this linux-perl they are talking about in this thread? Does anybody know how I can build/install a perl 5.10 or above that can run in the f10 compat layer? TIA! -- Alejandro Imass ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Why does Perl ExtUtils::MakeMaker install hang on FBSD Jail?
God love is hard to find. You got lucky freebsd-questions! 2011/08/04 13:23:04 -0400 Alejandro Imass => To FreeBSD Questions : AI> The MakeMaker build hangs in the test: INSTALL_BASE.t I had that same problem too, AI> the only person using the CPAN shell on an Jail ! ... but had no idea if it happens only in a jail. Looking at the ExtUtils/MakeMaker.pm instances in my $PREFIX/lib/perl5 I concluded that lang/perl5.X ports use to install several of them. That managed me to install the latest and greatest EU::MM from CPAN's .tar.gz (6,57 I think) and the only problem I have now is 'Need the 6.42 but we have an unknown version' warning but thiungs are just ok. You'd better ask in -perl@ list? 73! Peter pgp: A0E26627 (4A42 6841 2871 5EA7 52AB 12F8 0CE1 4AAC A0E2 6627) -- http://vereshagin.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Why does Perl ExtUtils::MakeMaker install hang on FBSD Jail?
Hi,
This post is related to this Perlmonks discussion:
http://perlmonks.org/?node_id=918414
But this particular post has to do with the FBSD part of the thread
The MakeMaker build hangs in the test: INSTALL_BASE.t
In this line, it never seems to return from the run() sub:
my $install_out = run("$make install");
If you eliminate this test, everything else works fine and you can
carry on with your business. The modules builds fine in the root
server where the jails are derived from so I'm guessing it has to do
with the way Jails handles that particular make install of Big-Dummy.
This is because I've tried to debug this and run() works correctly
several times before this line. So it is *very* wierd. But I can't be
the only person using the CPAN shell on an Jail !
Thanks
--
Alejandro Imass
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Perl Libs in FreeBSD CPAN and Ports
Hello, I generally use the CPAN shell mainly to get the latest version of CPAN modules but for modules that use XS I usually prefer using the port. Ports also seem to have pretty good versions of everything and I use these 2 mechanisms interchangeably. Anyway, my question is really to learn more on how these ports are maintained, etc. For example, in Debian Linux they have a Debian Perl policy, is there such a policy or something similar in FreeBSD so I can further read-up on the matter? Thanks, -- Alejandro Imass ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Perl Problem After Upgrade to 5.12.4
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 not exactly the method prescribed in UPDATING: You're right, of course - I ordinarily do this when I upgrade perl ... somehow it slipped my tiny and aging mind. Thanks for the reminder :) > > > 20110517: > AFFECTS: users of lang/perl* > AUTHOR: s...@freebsd.org > > lang/perl5.14 is out. If you want to switch to it from, for example > lang/perl5.12, that is: > > Portupgrade users: > 0) Fix pkgdb.db (for safety): > pkgdb -Ff > > 1) Reinstall new version of Perl (5.14): > env DISABLE_CONFLICTS=1 portupgrade -o lang/perl5.14 -f perl-5.12.\* > > 2) Reinstall everything that depends on Perl: > portupgrade -fr perl > > Portmaster users: > portmaster -o lang/perl5.14 lang/perl5.12 > > Conservative: > portmaster p5- > > Comprehensive (but perhaps overkill): > portmaster -r perl- > > Note: If the "perl-" glob matches more than one port you will need to > specify the name of the Perl directory in /var/db/pkg explicitly. > > > > I used the "portupgrade" method without incident. From what I have been > told, "perl-after-upgrade" != "env DISABLE_CONFLICTS=1 portupgrade -o > lang/perl5.14 -f perl-5.12.\*" > > As always, YMMV! > -- Tim Daneliuk tun...@tundraware.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Perl Problem After Upgrade to 5.12.4
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:
20110517:
AFFECTS: users of lang/perl*
AUTHOR: s...@freebsd.org
lang/perl5.14 is out. If you want to switch to it from, for example
lang/perl5.12, that is:
Portupgrade users:
0) Fix pkgdb.db (for safety):
pkgdb -Ff
1) Reinstall new version of Perl (5.14):
env DISABLE_CONFLICTS=1 portupgrade -o lang/perl5.14 -f perl-5.12.\*
2) Reinstall everything that depends on Perl:
portupgrade -fr perl
Portmaster users:
portmaster -o lang/perl5.14 lang/perl5.12
Conservative:
portmaster p5-
Comprehensive (but perhaps overkill):
portmaster -r perl-
Note: If the "perl-" glob matches more than one port you will need to
specify the name of the Perl directory in /var/db/pkg explicitly.
I used the "portupgrade" method without incident. From what I have been
told, "perl-after-upgrade" != "env DISABLE_CONFLICTS=1 portupgrade -o
lang/perl5.14 -f perl-5.12.\*"
As always, YMMV!
--
Jerry ✌
jerry+f...@seibercom.net
Disclaimer: off-list followups get on-list replies or ignored.
Do not CC this poster. Please do not ignore the "Reply-To" header.
http://www.catb.org/~esr/faqs/smart-questions.html
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Perl Problem After Upgrade to 5.12.4
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 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/lib/perl5/site_perl/5.12.4/Module/Build.pm in >>> /usr/ports/devel/p5-Module-Build >>> ===> License check disabled, port has not defined LICENSE >>> ===> Extracting for p5-Module-Build-0.3800_1 >>> => SHA256 Checksum OK for Module-Build-0.3800.tar.gz. >>> ===> p5-Module-Build-0.3800_1 depends on file: >>> /usr/local/bin/perl5.12.4 - found >>> ===> Patching for p5-Module-Build-0.3800_1 >>> ===> p5-Module-Build-0.3800_1 depends on file: >>> /usr/local/bin/perl5.12.4 - found >>> ===> p5-Module-Build-0.3800_1 depends on package: >>> p5-CPAN-Meta>=2.110420 - found >>> ===> p5-Module-Build-0.3800_1 depends on package: >>> p5-Module-Metadata>=1.02 - found >>> ===> p5-Module-Build-0.3800_1 depends on package: >>> p5-Parse-CPAN-Meta>=1.44.01 - found >>> ===> p5-Module-Build-0.3800_1 depends on package: >>> p5-Perl-OSType>=1.000 - found >>> ===> p5-Module-Build-0.3800_1 depends on package: >>> p5-version>=0.87 >>> - found >>> ===> p5-Module-Build-0.3800_1 depends on file: >>> /usr/local/bin/perl5.12.4 - found >>> ===> Configuring for p5-Module-Build-0.3800_1 >>> *** BOOTSTRAPPING Perl::OSType *** >>> *** BOOTSTRAPPING version *** >>> *** BOOTSTRAPPING Module::Metadata *** >>> Checking prerequisites... >>> requires: >>> ! CPAN::Meta is not installed >>> build_requires: >>> ! Parse::CPAN::Meta (1.40) is installed, but we need version >>>> = 1.4401 >>> >>> ERRORS/WARNINGS FOUND IN PREREQUISITES. You may wish to install >>> the versions >>> of the modules indicated above before proceeding with this >>> installation >>> >>> Could not create MYMETA files >>> Creating new 'Build' script for 'Module-Build' version '0.3800' >>> Copied META.yml to MYMETA.yml for bootstrapping >>> >>> These additional prerequisites must be installed: >>> requires: >>> ! Perl::OSType (we need version 1.00) >>> ! version (we need version 0.87) >>> ! Module::Metadata (we need version 1.02) >>> ===> Building for p5-Module-Build-0.3800_1 >>> Can't locate Perl/OSType.pm in @INC (@INC contains: t/lib t/bundled >>> lib /usr/local/lib/perl5/5.12.4/BSDPAN >>> /usr/local/lib/perl5/site_perl/5.12.4/mach >>> /usr/local/lib/perl5/site_perl/5.12.4 >>> /usr/local/lib/perl5/5.12.4/mach >>> /usr/local/lib/perl5/5.12.4 .) at lib/Module/Build.pm line 13. >>> BEGIN failed--compilation aborted at lib/Module/Build.pm line 13. >>> Compilation failed in require at Build line 42. >>> BEGIN failed--compilation aborted at Build line 42. >>> *** Error code 2 >>> >>> Stop in /usr1/ports/devel/p5-Module-Build. >>> *** Error code 1 >>> >>> Stop in /usr1/ports/converters/p5-Encode-Detect. >>> *** Error code 1 >>> >>> Stop in /usr1/ports/mail/p5-Mail-SpamAssassin. >>> *** Error code 1 >>> >>> Stop in /usr1/ports/mail/p5-Mail-SpamAssassi >> >> Hello Tim, list, >> >> I have the same problem on one of my boxes. Cannot upgrade >> p5-Module-Build-0.3800 port because of this. > > Has anyone filed a PR against this problem? > 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 I still cannot build remmina. There seems to be some hocus pocus having to do with missing dependent perl XML parser libs. Sigh. I can't wait until the planet either: a) Migrates 100% to python or b) Learns to do batteries included packaging like python. -- Tim Daneliuk tun...@tundraware.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Perl Problem After Upgrade to 5.12.4
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 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/lib/perl5/site_perl/5.12.4/Module/Build.pm in > > /usr/ports/devel/p5-Module-Build > > ===> License check disabled, port has not defined LICENSE > > ===> Extracting for p5-Module-Build-0.3800_1 > > => SHA256 Checksum OK for Module-Build-0.3800.tar.gz. > > ===> p5-Module-Build-0.3800_1 depends on file: > > /usr/local/bin/perl5.12.4 - found > > ===> Patching for p5-Module-Build-0.3800_1 > > ===> p5-Module-Build-0.3800_1 depends on file: > > /usr/local/bin/perl5.12.4 - found > > ===> p5-Module-Build-0.3800_1 depends on package: > > p5-CPAN-Meta>=2.110420 - found > > ===> p5-Module-Build-0.3800_1 depends on package: > > p5-Module-Metadata>=1.02 - found > > ===> p5-Module-Build-0.3800_1 depends on package: > > p5-Parse-CPAN-Meta>=1.44.01 - found > > ===> p5-Module-Build-0.3800_1 depends on package: > > p5-Perl-OSType>=1.000 - found > > ===> p5-Module-Build-0.3800_1 depends on package: > > p5-version>=0.87 > > - found > > ===> p5-Module-Build-0.3800_1 depends on file: > > /usr/local/bin/perl5.12.4 - found > > ===> Configuring for p5-Module-Build-0.3800_1 > > *** BOOTSTRAPPING Perl::OSType *** > > *** BOOTSTRAPPING version *** > > *** BOOTSTRAPPING Module::Metadata *** > > Checking prerequisites... > > requires: > > ! CPAN::Meta is not installed > > build_requires: > > ! Parse::CPAN::Meta (1.40) is installed, but we need version > > >= 1.4401 > > > > ERRORS/WARNINGS FOUND IN PREREQUISITES. You may wish to install > > the versions > > of the modules indicated above before proceeding with this > > installation > > > > Could not create MYMETA files > > Creating new 'Build' script for 'Module-Build' version '0.3800' > > Copied META.yml to MYMETA.yml for bootstrapping > > > > These additional prerequisites must be installed: > > requires: > > ! Perl::OSType (we need version 1.00) > > ! version (we need version 0.87) > > ! Module::Metadata (we need version 1.02) > > ===> Building for p5-Module-Build-0.3800_1 > > Can't locate Perl/OSType.pm in @INC (@INC contains: t/lib t/bundled > > lib /usr/local/lib/perl5/5.12.4/BSDPAN > > /usr/local/lib/perl5/site_perl/5.12.4/mach > > /usr/local/lib/perl5/site_perl/5.12.4 > > /usr/local/lib/perl5/5.12.4/mach > > /usr/local/lib/perl5/5.12.4 .) at lib/Module/Build.pm line 13. > > BEGIN failed--compilation aborted at lib/Module/Build.pm line 13. > > Compilation failed in require at Build line 42. > > BEGIN failed--compilation aborted at Build line 42. > > *** Error code 2 > > > > Stop in /usr1/ports/devel/p5-Module-Build. > > *** Error code 1 > > > > Stop in /usr1/ports/converters/p5-Encode-Detect. > > *** Error code 1 > > > > Stop in /usr1/ports/mail/p5-Mail-SpamAssassin. > > *** Error code 1 > > > > Stop in /usr1/ports/mail/p5-Mail-SpamAssassi > > Hello Tim, list, > > I have the same problem on one of my boxes. Cannot upgrade > p5-Module-Build-0.3800 port because of this. Has anyone filed a PR against this problem? -- Jerry ✌ jerry+f...@seibercom.net Disclaimer: off-list followups get on-list replies or ignored. Do not CC this poster. Please do not ignore the "Reply-To" header. http://www.catb.org/~esr/faqs/smart-questions.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Perl Problem After Upgrade to 5.12.4
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.pm - not found ===>Verifying install for /usr/local/lib/perl5/site_perl/5.12.4/Module/Build.pm in /usr/ports/devel/p5-Module-Build ===> License check disabled, port has not defined LICENSE ===> Extracting for p5-Module-Build-0.3800_1 => SHA256 Checksum OK for Module-Build-0.3800.tar.gz. ===> p5-Module-Build-0.3800_1 depends on file: /usr/local/bin/perl5.12.4 - found ===> Patching for p5-Module-Build-0.3800_1 ===> p5-Module-Build-0.3800_1 depends on file: /usr/local/bin/perl5.12.4 - found ===> p5-Module-Build-0.3800_1 depends on package: p5-CPAN-Meta>=2.110420 - found ===> p5-Module-Build-0.3800_1 depends on package: p5-Module-Metadata>=1.02 - found ===> p5-Module-Build-0.3800_1 depends on package: p5-Parse-CPAN-Meta>=1.44.01 - found ===> p5-Module-Build-0.3800_1 depends on package: p5-Perl-OSType>=1.000 - found ===> p5-Module-Build-0.3800_1 depends on package: p5-version>=0.87 - found ===> p5-Module-Build-0.3800_1 depends on file: /usr/local/bin/perl5.12.4 - found ===> Configuring for p5-Module-Build-0.3800_1 *** BOOTSTRAPPING Perl::OSType *** *** BOOTSTRAPPING version *** *** BOOTSTRAPPING Module::Metadata *** Checking prerequisites... requires: ! CPAN::Meta is not installed build_requires: ! Parse::CPAN::Meta (1.40) is installed, but we need version >= 1.4401 ERRORS/WARNINGS FOUND IN PREREQUISITES. You may wish to install the versions of the modules indicated above before proceeding with this installation Could not create MYMETA files Creating new 'Build' script for 'Module-Build' version '0.3800' Copied META.yml to MYMETA.yml for bootstrapping These additional prerequisites must be installed: requires: ! Perl::OSType (we need version 1.00) ! version (we need version 0.87) ! Module::Metadata (we need version 1.02) ===> Building for p5-Module-Build-0.3800_1 Can't locate Perl/OSType.pm in @INC (@INC contains: t/lib t/bundled lib /usr/local/lib/perl5/5.12.4/BSDPAN /usr/local/lib/perl5/site_perl/5.12.4/mach /usr/local/lib/perl5/site_perl/5.12.4 /usr/local/lib/perl5/5.12.4/mach /usr/local/lib/perl5/5.12.4 .) at lib/Module/Build.pm line 13. BEGIN failed--compilation aborted at lib/Module/Build.pm line 13. Compilation failed in require at Build line 42. BEGIN failed--compilation aborted at Build line 42. *** Error code 2 Stop in /usr1/ports/devel/p5-Module-Build. *** Error code 1 Stop in /usr1/ports/converters/p5-Encode-Detect. *** Error code 1 Stop in /usr1/ports/mail/p5-Mail-SpamAssassin. *** Error code 1 Stop in /usr1/ports/mail/p5-Mail-SpamAssassi Hello Tim, list, I have the same problem on one of my boxes. Cannot upgrade p5-Module-Build-0.3800 port because of this. Cheers, Lars. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Perl Problem After Upgrade to 5.12.4
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.4401 if you use to updatedb(8) try to search for dupes: locate Parse/CPAN/Meta.pm If there is no dupes, look at the $VERSION inside that module 73! Peter pgp: A0E26627 (4A42 6841 2871 5EA7 52AB 12F8 0CE1 4AAC A0E2 6627) -- http://vereshagin.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Perl Problem After Upgrade to 5.12.4
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/lib/perl5/site_perl/5.12.4/Module/Build.pm in /usr/ports/devel/p5-Module-Build ===> License check disabled, port has not defined LICENSE ===> Extracting for p5-Module-Build-0.3800_1 => SHA256 Checksum OK for Module-Build-0.3800.tar.gz. ===> p5-Module-Build-0.3800_1 depends on file: /usr/local/bin/perl5.12.4 - found ===> Patching for p5-Module-Build-0.3800_1 ===> p5-Module-Build-0.3800_1 depends on file: /usr/local/bin/perl5.12.4 - found ===> p5-Module-Build-0.3800_1 depends on package: p5-CPAN-Meta>=2.110420 - found ===> p5-Module-Build-0.3800_1 depends on package: p5-Module-Metadata>=1.02 - found ===> p5-Module-Build-0.3800_1 depends on package: p5-Parse-CPAN-Meta>=1.44.01 - found ===> p5-Module-Build-0.3800_1 depends on package: p5-Perl-OSType>=1.000 - found ===> p5-Module-Build-0.3800_1 depends on package: p5-version>=0.87 - found ===> p5-Module-Build-0.3800_1 depends on file: /usr/local/bin/perl5.12.4 - found ===> Configuring for p5-Module-Build-0.3800_1 *** BOOTSTRAPPING Perl::OSType *** *** BOOTSTRAPPING version *** *** BOOTSTRAPPING Module::Metadata *** Checking prerequisites... requires: ! CPAN::Meta is not installed build_requires: ! Parse::CPAN::Meta (1.40) is installed, but we need version >= 1.4401 ERRORS/WARNINGS FOUND IN PREREQUISITES. You may wish to install the versions of the modules indicated above before proceeding with this installation Could not create MYMETA files Creating new 'Build' script for 'Module-Build' version '0.3800' Copied META.yml to MYMETA.yml for bootstrapping These additional prerequisites must be installed: requires: ! Perl::OSType (we need version 1.00) ! version (we need version 0.87) ! Module::Metadata (we need version 1.02) ===> Building for p5-Module-Build-0.3800_1 Can't locate Perl/OSType.pm in @INC (@INC contains: t/lib t/bundled lib /usr/local/lib/perl5/5.12.4/BSDPAN /usr/local/lib/perl5/site_perl/5.12.4/mach /usr/local/lib/perl5/site_perl/5.12.4 /usr/local/lib/perl5/5.12.4/mach /usr/local/lib/perl5/5.12.4 .) at lib/Module/Build.pm line 13. BEGIN failed--compilation aborted at lib/Module/Build.pm line 13. Compilation failed in require at Build line 42. BEGIN failed--compilation aborted at Build line 42. *** Error code 2 Stop in /usr1/ports/devel/p5-Module-Build. *** Error code 1 Stop in /usr1/ports/converters/p5-Encode-Detect. *** Error code 1 Stop in /usr1/ports/mail/p5-Mail-SpamAssassin. *** Error code 1 Stop in /usr1/ports/mail/p5-Mail-SpamAssassi -- Tim Daneliuk tun...@tundraware.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: pkg-add - package insists on old version of Perl
in message <4e08aca7.5080...@gracenpeace.net>, wrote Joe in MPLS thusly... > > I am trying to install the Amanda server package. I am running FreeBSD > 8.2 with Perl 5.12.3. > > The package lists Perl 5.10.1 as a dependency and since my newer version > of Perl conlicts with the older version the install fails. pkg_add with > "-f" just tries to force the installation of the older Perl and fails. > > How do I get the package to install and use the Perl I already have? I'd > rather not downgrade Perl. pkg_add should not fail itself in installing a package ... -f, --force Force installation to proceed even if prerequisite packages are not installed or the requirements script fails. Although pkg_add will still try to find and auto-install missing prerequisite packages, a failure to find one will not be fatal. ... then, just to confirm, pkg_add did not succeed in installing the desired package in the end? I wonder if using -F ... -F Already installed packages are not an error. ... would install perl 5.10 too in addition to 5.12, or install of 5.10 would be skipped?. - parv -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: pkg-add - package insists on old version of Perl
On 27/06/2011 17:15, Joe in MPLS wrote: > I am trying to install the Amanda server package. I am running FreeBSD > 8.2 with Perl 5.12.3. > > The package lists Perl 5.10.1 as a dependency and since my newer version > of Perl conlicts with the older version the install fails. pkg_add with > "-f" just tries to force the installation of the older Perl and fails. > > How do I get the package to install and use the Perl I already have? I'd > rather not downgrade Perl. Unfortunately, you don't. Not with packages at least. This version mis-match thing is a known limitation with FreeBSD pkgs: changes are under development, but nowhere near ready for primetime yet. Instead, install amanda from ports. Ports will automatically adapt to the version of perl you already have installed, and generally do what you want. Amanda is not (as I recall) something with a huge dependency list, nor is it a particularly enormous program in its own right, so compiling the port shouldn't be too onerous. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
pkg-add - package insists on old version of Perl
I am trying to install the Amanda server package. I am running FreeBSD 8.2 with Perl 5.12.3. The package lists Perl 5.10.1 as a dependency and since my newer version of Perl conlicts with the older version the install fails. pkg_add with "-f" just tries to force the installation of the older Perl and fails. How do I get the package to install and use the Perl I already have? I'd rather not downgrade Perl. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Installing X11 gives perl version conflict
perryh> running 8.1-RELEASE (and not 8-STABLE) [ ... ] perryh> /packages-8.1-release/ AH HA The .message file contains the solution (I hope): "packages-*-release directories are built from the ports collection shipped with the release, and are not updated thereafter. packages-*-stable and packages-*-current are updated roughly once a week." "stable" should be renamed "bleeding-edge" to warn dunderheads like me that think stable means stable rather than unstable. And maybe web browsers should automagically display the .message file. THANK YOU !!! If only debugging X11 were so easy... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Installing X11 gives perl version conflict
RW wrote: > If building isn't an option then it's better to stick to one > release trees at a time. Unfortunately, it seems that pkg_add(1) does not make that as easy as one might prefer. I discovered recently that, even though I am running 8.1-RELEASE (and not 8-STABLE), "pkg_add -r" fetches from ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8.1-release/Latest/, rather than from the frozen-at-release -- and thus self-consistent -- collection in .../All/ One way around this is to set PACKAGESITE to, for example, ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8.1-release/All/ (making any necessary adjustments to the mirror and release names). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Installing X11 gives perl version conflict
On Fri, 24 Jun 2011, Michael Powell wrote: d...@safeport.com wrote: On Fri, 24 Jun 2011, Randal L. Schwartz wrote: "Dieter" == Dieter BSD writes: Dieter> Attempt to install package xf86-video-fbdev-0.4.2.tbz Dieter> gives conflict between perl-5.10.1_3 and perl-5.12.3 Dieter> even when installing into clean directory tree. Packages seem like a great idea when you get started, but they're all built with the default configs, and those don't necessarily line up. Always build from source. Always build from source. When you installed 5.12 Perl, it put a marker in /etc/make.conf such that had you built the xf86-video-fbdev from source, it would have depended on 5.12 Perl, not the 5.10 Perl baked in to the default package. Do that, and all will be well. Yes, I had to learn this the hard way a year ago, so now I pass along that knowledge. :) I had the same error. Can the Make files either have this as a warning or change the dependency to be any Perl5, or whatever the 'real' dependency is? This was not an issue before Perl was removed from the base system and Xorg was split into its 200 (or so) component parts. Read /usr/ports/Mk/bsd.perl.mk. I think mostly many of the variables contained within may be set in /etc/make.conf and can be picked up at build time by make. Particularly interesting were PERL_VERSION, PERL_PORT, and USE_PERL, for example. Reading down into the contents will point to how the variables get used. C o o l- thanks Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Installing X11 gives perl version conflict
RW> The problem as I see it is that he is installing packages that RW> aren't built from the same tree. One of the dependencies of RW> xf86-video-fbdev-0.4.2 was built when perl 5.10 was the default RW> and one after the default switched to perl 5.12. RW> If building isn't an option then it's better to stick to one RW> release trees at a time. I think you are correct. How does one stick to one release tree? As I recall the CD/DVDs have a very small subset of ports/packages. The ftp sites have the full set, but are not static. Some packages disappear, so you have no choice but to use a newer version. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Installing X11 gives perl version conflict
Dieter> Attempt to install package xf86-video-fbdev-0.4.2.tbz Dieter> gives conflict between perl-5.10.1_3 and perl-5.12.3 Dieter> even when installing into clean directory tree. Randal> Packages seem like a great idea when you get started, Randal> but they're all built with the default configs, and Randal> those don't necessarily line up. Randal> Always build from source. Always build from source. Except that I switched from ports to packages awhile back because I was having so many problems building ports, and packages was, until now, working much better. I'm not even sure if I need xf86-video-fbdev or not? I was just trying to make Xorg happy. A few lines grepped from dmesg: port 0xac00-0xacff mem 0xfa00-0xfaff,0xfdfff000-0xfdff irq 19 at device 5.0 on pci1 sc0: VGA <16 virtual consoles, flags=0x100> at port 0x3c0-0x3df iomem 0xa-0xb on isa0 port 0x60,0x64 irq 1 on acpi0 irq 1 on atkbdc0 kbd0 at atkbd0 irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 # Xorg -configure -logverbose 100 (--) PCI:*(0:1:5:0) 1002:4752:1002:8008 ATI Technologies Inc Rage XL rev 39, Mem @ 0xfa00/16777216, 0xfdfff000/4096, I/O @ 0xac00/256, BIOS @ 0x/65536 [ ... ] List of video drivers: ati radeon r128 (II) LoadModule: "ati" (II) Loading /usr/local/lib/xorg/modules/drivers/ati_drv.so (II) Module ati: vendor="X.Org Foundation" compiled for 1.7.7, module version = 6.14.1 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 6.0 (II) LoadModule: "radeon" (II) Loading /usr/local/lib/xorg/modules/drivers/radeon_drv.so (II) Module radeon: vendor="X.Org Foundation" compiled for 1.7.7, module version = 6.14.1 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 6.0 (II) LoadModule: "r128" (II) Loading /usr/local/lib/xorg/modules/drivers/r128_drv.so (II) Module r128: vendor="X.Org Foundation" compiled for 1.7.7, module version = 6.8.1 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 6.0 (II) Primary Device is: PCI 01@00:05:0 No devices to configure. Configuration failed. No devices? What about sc0 ? Google found several suggestions to just try Xorg without -configure, so: # Xorg -logverbose 100 (II) Cannot locate a core pointer device. (II) Cannot locate a core keyboard device. (II) The server relies on HAL to provide the list of input devices. If no devices become available, reconfigure HAL or disable AutoAddDevices. [ ... ] (II) LoadModule: "mach64" (WW) Warning, couldn't open module mach64 (II) UnloadModule: "mach64" (EE) Failed to load module "mach64" (module does not exist, 0) (II) LoadModule: "vesa" (WW) Warning, couldn't open module vesa (II) UnloadModule: "vesa" (EE) Failed to load module "vesa" (module does not exist, 0) (II) LoadModule: "fbdev" (WW) Warning, couldn't open module fbdev (II) UnloadModule: "fbdev" (EE) Failed to load module "fbdev" (module does not exist, 0) (EE) No drivers available. Fatal server error: no screens found The console said: Starting dbus. Starting hald. ps says: messagebus 924 0.0 0.0 8124 1420 ?? Is 9:29PM 0:00.00 /usr/local/bin/dbus-daemon --system ps doesn't find a hald running? I have no clue how to reconfigure HAL or disable AutoAddDevices. Can't I just tell Xorg to use sc0 kbd0 and psm0 ? The man pages don't mention how to do this. I'm also not sure which driver it should be using. The r128 man page doesn't explicitly list the RAGE XL. Xorg without -configure doesn't mention r128. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Installing X11 gives perl version conflict
On Fri, 24 Jun 2011 11:20:46 -0400 Michael Powell wrote: > Read /usr/ports/Mk/bsd.perl.mk. I think mostly many of the variables > contained within may be set in /etc/make.conf and can be picked up at > build time by make. Particularly interesting were PERL_VERSION, > PERL_PORT, and USE_PERL, for example. Reading down into the contents > will point to how the variables get used. I don't think any of this is very relevant - except as general background . The problem as I see it is that he is installing packages that aren't built from the same tree. One of the dependencies of xf86-video-fbdev-0.4.2 was built when perl 5.10 was the default and one after the default switched to perl 5.12. If building isn't an option then it's better to stick to one release trees at a time. That still leave the problem to dealing with vulnerabilities as best you can, but there is not a simple answer. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Installing X11 gives perl version conflict
d...@safeport.com wrote: > On Fri, 24 Jun 2011, Randal L. Schwartz wrote: > >>>>>>> "Dieter" == Dieter BSD writes: >> >> Dieter> Attempt to install package xf86-video-fbdev-0.4.2.tbz >> Dieter> gives conflict between perl-5.10.1_3 and perl-5.12.3 >> Dieter> even when installing into clean directory tree. >> >> Packages seem like a great idea when you get started, but they're all >> built with the default configs, and those don't necessarily line up. >> >> Always build from source. Always build from source. >> >> When you installed 5.12 Perl, it put a marker in /etc/make.conf such >> that had you built the xf86-video-fbdev from source, it would have >> depended on 5.12 Perl, not the 5.10 Perl baked in to the default >> package. Do that, and all will be well. >> >> Yes, I had to learn this the hard way a year ago, so now I pass along >> that knowledge. :) >> > I had the same error. Can the Make files either have this as a warning or > change the dependency to be any Perl5, or whatever the 'real' dependency > is? This was not an issue before Perl was removed from the base system and > Xorg was split into its 200 (or so) component parts. > Read /usr/ports/Mk/bsd.perl.mk. I think mostly many of the variables contained within may be set in /etc/make.conf and can be picked up at build time by make. Particularly interesting were PERL_VERSION, PERL_PORT, and USE_PERL, for example. Reading down into the contents will point to how the variables get used. -Mike [snip] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Installing X11 gives perl version conflict
On Fri, 24 Jun 2011, Randal L. Schwartz wrote: "Dieter" == Dieter BSD writes: Dieter> Attempt to install package xf86-video-fbdev-0.4.2.tbz Dieter> gives conflict between perl-5.10.1_3 and perl-5.12.3 Dieter> even when installing into clean directory tree. Packages seem like a great idea when you get started, but they're all built with the default configs, and those don't necessarily line up. Always build from source. Always build from source. When you installed 5.12 Perl, it put a marker in /etc/make.conf such that had you built the xf86-video-fbdev from source, it would have depended on 5.12 Perl, not the 5.10 Perl baked in to the default package. Do that, and all will be well. Yes, I had to learn this the hard way a year ago, so now I pass along that knowledge. :) I had the same error. Can the Make files either have this as a warning or change the dependency to be any Perl5, or whatever the 'real' dependency is? This was not an issue before Perl was removed from the base system and Xorg was split into its 200 (or so) component parts. For me using an 80MHz processor with 512MB of memory (a perfectly good workstation BTW runs KDE-lite just fine) building is not an option. If I started June 1, I might be done in time for the fireworks :) My solution was just to start from scratch (about 2-3 hours). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Installing X11 gives perl version conflict
>>>>> "Dieter" == Dieter BSD writes: Dieter> Attempt to install package xf86-video-fbdev-0.4.2.tbz Dieter> gives conflict between perl-5.10.1_3 and perl-5.12.3 Dieter> even when installing into clean directory tree. Packages seem like a great idea when you get started, but they're all built with the default configs, and those don't necessarily line up. Always build from source. Always build from source. When you installed 5.12 Perl, it put a marker in /etc/make.conf such that had you built the xf86-video-fbdev from source, it would have depended on 5.12 Perl, not the 5.10 Perl baked in to the default package. Do that, and all will be well. Yes, I had to learn this the hard way a year ago, so now I pass along that knowledge. :) -- Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 http://www.stonehenge.com/merlyn/> Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc. See http://methodsandmessages.posterous.com/ for Smalltalk discussion ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Spamassassin not working after update of Perl
So true. I have processed as you suggested and will follow that + the
UPDATING suggestion as well in future.
Just got on wrong track that this scenario should be used with 5.14 to
5.14.x as well.
FYI:
After running
sa-update -D
sa-update --nogpg
spamassassin --lint -D
freshclam
I got at the end a warning, saying:
warn: Use of uninitialized value $opt{"syslog-socket"} in lc at
/usr/local/bin/spamd line 44
Found out that this is a minor thing and fixed *in* 3.3.2 and *in* trunk.
BR,
Jos Chrispijn
Damien Fleuriot:
Normally, any special care to be taken while upgrading your port should
be noted in UPDATING.
However, it's always prudent to rebuild dependencies when upgrading a
port, because you never know what changed (unless you take the time to
check the changelog + source code).
On 6/24/11 12:33 PM, Jos Chrispijn wrote:
Hi Damien,
What I don't understand is that if I already are on 15.4 and there is an
update to 15.4.1 I have to perform always a 'portupgrade -fr perl' to
have this work?
Normally this only goes for 15.3 to 15.4 (full version upgrade) or do I
miss something here?
Thanks for your help
Jos Chrispijn
Damien Fleuriot:
On 6/23/11 3:51 PM, Jos Chrispijn wrote:
I have updated my Perl version yesterday but now my Spamd doesn't work
anymore.
Can someone hint me how to solve this?
thanks,
Jos Chrispijn
Pls see output:
Can't locate Net/DNS.pm in @INC (@INC contains:
/usr/local/lib/perl5/site_perl/5.14.0 /usr/local/lib/perl5/5.14.1/BSDPAN
/usr/local/lib/perl5/site_perl/5.14.1/mach
/usr/local/lib/perl5/site_perl/5.14.1 /usr/local/lib/perl5/5.14.1/mach
/usr/local/lib/perl5/5.14.1) at /usr/local/bin/sa-update line 80.
BEGIN failed--compilation aborted at /usr/local/bin/sa-update line 80.
Can't locate Net/DNS.pm in @INC (@INC contains:
/usr/local/lib/perl5/site_perl/5.14.0 /usr/local/lib/perl5/5.14.1/BSDPAN
/usr/local/lib/perl5/site_perl/5.14.1/mach
/usr/local/lib/perl5/site_perl/5.14.1 /usr/local/lib/perl5/5.14.1/mach
/usr/local/lib/perl5/5.14.1) at /usr/local/bin/sa-update line 80.
BEGIN failed--compilation aborted at /usr/local/bin/sa-update line 80.
Can't locate NetAddr/IP.pm in @INC (@INC contains:
/usr/local/lib/perl5/site_perl/5.14.0 /usr/local/lib/perl5/5.14.1/BSDPAN
/usr/local/lib/perl5/site_perl/5.14.1/mach
/usr/local/lib/perl5/site_perl/5.14.1 /usr/local/lib/perl5/5.14.1/mach
/usr/local/lib/perl5/5.14.1) at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/NetSet.pm
line 25.
BEGIN failed--compilation aborted at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/NetSet.pm
line 25.
Compilation failed in require at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/Conf.pm line 86.
BEGIN failed--compilation aborted at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/Conf.pm line 86.
Compilation failed in require at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin.pm line 71.
BEGIN failed--compilation aborted at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin.pm line 71.
Compilation failed in require at /usr/local/bin/spamassassin line 80.
BEGIN failed--compilation aborted at /usr/local/bin/spamassassin line
80.
ClamAV update process started at Thu Jun 23 15:43:00 2011
main.cld is up to date (version: 53, sigs: 846214, f-level: 53, builder:
sven)
daily.cld is up to date (version: 13231, sigs: 130699, f-level: 60,
builder: arnaud)
bytecode.cld is up to date (version: 143, sigs: 40, f-level: 60,
builder: edwin)
spamd not running? (check /var/run/spamd/spamd.pid).
Starting spamd.
Can't locate NetAddr/IP.pm in @INC (@INC contains:
/usr/local/lib/perl5/site_perl/5.14.0 /usr/local/lib/perl5/5.14.1/BSDPAN
/usr/local/lib/perl5/site_perl/5.14.1/mach
/usr/local/lib/perl5/site_perl/5.14.1 /usr/local/lib/perl5/5.14.1/mach
/usr/local/lib/perl5/5.14.1) at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/NetSet.pm
line 25.
BEGIN failed--compilation aborted at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/NetSet.pm
line 25.
Compilation failed in require at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/Conf.pm line 86.
BEGIN failed--compilation aborted at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/Conf.pm line 86.
Compilation failed in require at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin.pm line 71.
BEGIN failed--compilation aborted at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin.pm line 71.
Compilation failed in require at /usr/local/bin/spamd line 85.
BEGIN failed--compilation aborted at /usr/local/bin/spamd line 85.
Can't locate NetAddr/IP.pm in @INC (@INC contains:
/usr/local/lib/perl5/site_perl/5.14.0 /usr/local/lib/perl5/5.14.1/BSDPAN
/usr/local/lib/perl5/site_perl/5.14.1/mach
/usr/local/lib/perl5/site_perl/5.14.1 /usr/local/lib/perl5/5.14.1/mach
/usr/local/lib/perl5/5.14.1) at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/NetSet.pm
line 25.
BEGIN failed--compilation aborted at
/usr/local/lib/perl5/site_perl/5.
Re: Spamassassin not working after update of Perl
So true. I have processed as you suggested and will follow that + the
UPDATING suggestion as well in future.
Just got on wrong track that this scenario should be used with 5.14 to
5.14.x as well.
FYI:
After running
sa-update -D
sa-update --nogpg
spamassassin --lint -D
freshclam
I got at the end a warning, saying:
warn: Use of uninitialized value $opt{"syslog-socket"} in lc at
/usr/local/bin/spamd line 44
Found out that this is a minor thing and fixed *in* 3.3.2 and *in* trunk.
BR,
Jos Chrispijn
Damien Fleuriot:
Normally, any special care to be taken while upgrading your port should
be noted in UPDATING.
However, it's always prudent to rebuild dependencies when upgrading a
port, because you never know what changed (unless you take the time to
check the changelog + source code).
On 6/24/11 12:33 PM, Jos Chrispijn wrote:
Hi Damien,
What I don't understand is that if I already are on 15.4 and there is an
update to 15.4.1 I have to perform always a 'portupgrade -fr perl' to
have this work?
Normally this only goes for 15.3 to 15.4 (full version upgrade) or do I
miss something here?
Thanks for your help
Jos Chrispijn
Damien Fleuriot:
On 6/23/11 3:51 PM, Jos Chrispijn wrote:
I have updated my Perl version yesterday but now my Spamd doesn't work
anymore.
Can someone hint me how to solve this?
thanks,
Jos Chrispijn
Pls see output:
Can't locate Net/DNS.pm in @INC (@INC contains:
/usr/local/lib/perl5/site_perl/5.14.0 /usr/local/lib/perl5/5.14.1/BSDPAN
/usr/local/lib/perl5/site_perl/5.14.1/mach
/usr/local/lib/perl5/site_perl/5.14.1 /usr/local/lib/perl5/5.14.1/mach
/usr/local/lib/perl5/5.14.1) at /usr/local/bin/sa-update line 80.
BEGIN failed--compilation aborted at /usr/local/bin/sa-update line 80.
Can't locate Net/DNS.pm in @INC (@INC contains:
/usr/local/lib/perl5/site_perl/5.14.0 /usr/local/lib/perl5/5.14.1/BSDPAN
/usr/local/lib/perl5/site_perl/5.14.1/mach
/usr/local/lib/perl5/site_perl/5.14.1 /usr/local/lib/perl5/5.14.1/mach
/usr/local/lib/perl5/5.14.1) at /usr/local/bin/sa-update line 80.
BEGIN failed--compilation aborted at /usr/local/bin/sa-update line 80.
Can't locate NetAddr/IP.pm in @INC (@INC contains:
/usr/local/lib/perl5/site_perl/5.14.0 /usr/local/lib/perl5/5.14.1/BSDPAN
/usr/local/lib/perl5/site_perl/5.14.1/mach
/usr/local/lib/perl5/site_perl/5.14.1 /usr/local/lib/perl5/5.14.1/mach
/usr/local/lib/perl5/5.14.1) at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/NetSet.pm
line 25.
BEGIN failed--compilation aborted at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/NetSet.pm
line 25.
Compilation failed in require at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/Conf.pm line 86.
BEGIN failed--compilation aborted at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/Conf.pm line 86.
Compilation failed in require at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin.pm line 71.
BEGIN failed--compilation aborted at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin.pm line 71.
Compilation failed in require at /usr/local/bin/spamassassin line 80.
BEGIN failed--compilation aborted at /usr/local/bin/spamassassin line
80.
ClamAV update process started at Thu Jun 23 15:43:00 2011
main.cld is up to date (version: 53, sigs: 846214, f-level: 53, builder:
sven)
daily.cld is up to date (version: 13231, sigs: 130699, f-level: 60,
builder: arnaud)
bytecode.cld is up to date (version: 143, sigs: 40, f-level: 60,
builder: edwin)
spamd not running? (check /var/run/spamd/spamd.pid).
Starting spamd.
Can't locate NetAddr/IP.pm in @INC (@INC contains:
/usr/local/lib/perl5/site_perl/5.14.0 /usr/local/lib/perl5/5.14.1/BSDPAN
/usr/local/lib/perl5/site_perl/5.14.1/mach
/usr/local/lib/perl5/site_perl/5.14.1 /usr/local/lib/perl5/5.14.1/mach
/usr/local/lib/perl5/5.14.1) at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/NetSet.pm
line 25.
BEGIN failed--compilation aborted at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/NetSet.pm
line 25.
Compilation failed in require at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/Conf.pm line 86.
BEGIN failed--compilation aborted at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/Conf.pm line 86.
Compilation failed in require at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin.pm line 71.
BEGIN failed--compilation aborted at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin.pm line 71.
Compilation failed in require at /usr/local/bin/spamd line 85.
BEGIN failed--compilation aborted at /usr/local/bin/spamd line 85.
Can't locate NetAddr/IP.pm in @INC (@INC contains:
/usr/local/lib/perl5/site_perl/5.14.0 /usr/local/lib/perl5/5.14.1/BSDPAN
/usr/local/lib/perl5/site_perl/5.14.1/mach
/usr/local/lib/perl5/site_perl/5.14.1 /usr/local/lib/perl5/5.14.1/mach
/usr/local/lib/perl5/5.14.1) at
/usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/NetSet.pm
line 25.
BEGIN failed--compilation aborted at
/usr/local/lib/perl5/site_perl/5.
Re: Spamassassin not working after update of Perl
Normally, any special care to be taken while upgrading your port should be noted in UPDATING. However, it's always prudent to rebuild dependencies when upgrading a port, because you never know what changed (unless you take the time to check the changelog + source code). On 6/24/11 12:33 PM, Jos Chrispijn wrote: > Hi Damien, > > What I don't understand is that if I already are on 15.4 and there is an > update to 15.4.1 I have to perform always a 'portupgrade -fr perl' to > have this work? > Normally this only goes for 15.3 to 15.4 (full version upgrade) or do I > miss something here? > > Thanks for your help > Jos Chrispijn > > Damien Fleuriot: >> On 6/23/11 3:51 PM, Jos Chrispijn wrote: >>> I have updated my Perl version yesterday but now my Spamd doesn't work >>> anymore. >>> Can someone hint me how to solve this? >>> >>> thanks, >>> Jos Chrispijn >>> >>> Pls see output: >>> >>> Can't locate Net/DNS.pm in @INC (@INC contains: >>> /usr/local/lib/perl5/site_perl/5.14.0 /usr/local/lib/perl5/5.14.1/BSDPAN >>> /usr/local/lib/perl5/site_perl/5.14.1/mach >>> /usr/local/lib/perl5/site_perl/5.14.1 /usr/local/lib/perl5/5.14.1/mach >>> /usr/local/lib/perl5/5.14.1) at /usr/local/bin/sa-update line 80. >>> BEGIN failed--compilation aborted at /usr/local/bin/sa-update line 80. >>> >>> Can't locate Net/DNS.pm in @INC (@INC contains: >>> /usr/local/lib/perl5/site_perl/5.14.0 /usr/local/lib/perl5/5.14.1/BSDPAN >>> /usr/local/lib/perl5/site_perl/5.14.1/mach >>> /usr/local/lib/perl5/site_perl/5.14.1 /usr/local/lib/perl5/5.14.1/mach >>> /usr/local/lib/perl5/5.14.1) at /usr/local/bin/sa-update line 80. >>> BEGIN failed--compilation aborted at /usr/local/bin/sa-update line 80. >>> >>> Can't locate NetAddr/IP.pm in @INC (@INC contains: >>> /usr/local/lib/perl5/site_perl/5.14.0 /usr/local/lib/perl5/5.14.1/BSDPAN >>> /usr/local/lib/perl5/site_perl/5.14.1/mach >>> /usr/local/lib/perl5/site_perl/5.14.1 /usr/local/lib/perl5/5.14.1/mach >>> /usr/local/lib/perl5/5.14.1) at >>> /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/NetSet.pm >>> line 25. >>> >>> BEGIN failed--compilation aborted at >>> /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/NetSet.pm >>> line 25. >>> Compilation failed in require at >>> /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/Conf.pm line 86. >>> BEGIN failed--compilation aborted at >>> /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/Conf.pm line 86. >>> Compilation failed in require at >>> /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin.pm line 71. >>> BEGIN failed--compilation aborted at >>> /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin.pm line 71. >>> Compilation failed in require at /usr/local/bin/spamassassin line 80. >>> BEGIN failed--compilation aborted at /usr/local/bin/spamassassin line >>> 80. >>> ClamAV update process started at Thu Jun 23 15:43:00 2011 >>> main.cld is up to date (version: 53, sigs: 846214, f-level: 53, builder: >>> sven) >>> daily.cld is up to date (version: 13231, sigs: 130699, f-level: 60, >>> builder: arnaud) >>> bytecode.cld is up to date (version: 143, sigs: 40, f-level: 60, >>> builder: edwin) >>> spamd not running? (check /var/run/spamd/spamd.pid). >>> Starting spamd. >>> >>> Can't locate NetAddr/IP.pm in @INC (@INC contains: >>> /usr/local/lib/perl5/site_perl/5.14.0 /usr/local/lib/perl5/5.14.1/BSDPAN >>> /usr/local/lib/perl5/site_perl/5.14.1/mach >>> /usr/local/lib/perl5/site_perl/5.14.1 /usr/local/lib/perl5/5.14.1/mach >>> /usr/local/lib/perl5/5.14.1) at >>> /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/NetSet.pm >>> line 25. >>> >>> BEGIN failed--compilation aborted at >>> /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/NetSet.pm >>> line 25. >>> Compilation failed in require at >>> /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/Conf.pm line 86. >>> BEGIN failed--compilation aborted at >>> /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/Conf.pm line 86. >>> Compilation failed in require at >>> /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin.pm line 71. >>> BEGIN failed--compilation aborted at >>> /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin.pm line 71. >>> Compilation failed in require at /usr/local/bin/spamd li
perl modules included in core perl distribution dupe the portinstalled ones
Concrete jungle, oh freebsd-questions, you've got to do your best... I'm sorry I put this not into the -perl@ list because there are too many robots there. As far as I see the secondary major number change of the perl version can lead the user to the strange situations as more and more modules are being included into the perl distrinution itself. Combined with the previously installed version from ports they don't seem to be taken care of even by perl-after-upgrade(1). I've just struggled with the recurring problem of (dualvar|weaken|etc) 'is only available with the XS version of Scalar::Util' with a kind of a very simple solution of pkg_delete of p5-Scalar-List-Utils for perl5.14. By far there is a lot of such a modules, next aforeknown is CGI.pm. Although it's not an XS module to make such a size of a trouble but I'm pretty sure there are the ones there. Is it a known thing for me to quickly detect those duplicate modules packages and delete tthem and fix the packages dependent on them or it's a stuff to be made yet? Thank you. 73! Peter pgp: A0E26627 (4A42 6841 2871 5EA7 52AB 12F8 0CE1 4AAC A0E2 6627) -- http://vereshagin.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Spamassassin not working after update of Perl
Hi Damien, What I don't understand is that if I already are on 15.4 and there is an update to 15.4.1 I have to perform always a 'portupgrade -fr perl' to have this work? Normally this only goes for 15.3 to 15.4 (full version upgrade) or do I miss something here? Thanks for your help Jos Chrispijn Damien Fleuriot: On 6/23/11 3:51 PM, Jos Chrispijn wrote: I have updated my Perl version yesterday but now my Spamd doesn't work anymore. Can someone hint me how to solve this? thanks, Jos Chrispijn Pls see output: Can't locate Net/DNS.pm in @INC (@INC contains: /usr/local/lib/perl5/site_perl/5.14.0 /usr/local/lib/perl5/5.14.1/BSDPAN /usr/local/lib/perl5/site_perl/5.14.1/mach /usr/local/lib/perl5/site_perl/5.14.1 /usr/local/lib/perl5/5.14.1/mach /usr/local/lib/perl5/5.14.1) at /usr/local/bin/sa-update line 80. BEGIN failed--compilation aborted at /usr/local/bin/sa-update line 80. Can't locate Net/DNS.pm in @INC (@INC contains: /usr/local/lib/perl5/site_perl/5.14.0 /usr/local/lib/perl5/5.14.1/BSDPAN /usr/local/lib/perl5/site_perl/5.14.1/mach /usr/local/lib/perl5/site_perl/5.14.1 /usr/local/lib/perl5/5.14.1/mach /usr/local/lib/perl5/5.14.1) at /usr/local/bin/sa-update line 80. BEGIN failed--compilation aborted at /usr/local/bin/sa-update line 80. Can't locate NetAddr/IP.pm in @INC (@INC contains: /usr/local/lib/perl5/site_perl/5.14.0 /usr/local/lib/perl5/5.14.1/BSDPAN /usr/local/lib/perl5/site_perl/5.14.1/mach /usr/local/lib/perl5/site_perl/5.14.1 /usr/local/lib/perl5/5.14.1/mach /usr/local/lib/perl5/5.14.1) at /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/NetSet.pm line 25. BEGIN failed--compilation aborted at /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/NetSet.pm line 25. Compilation failed in require at /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/Conf.pm line 86. BEGIN failed--compilation aborted at /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/Conf.pm line 86. Compilation failed in require at /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin.pm line 71. BEGIN failed--compilation aborted at /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin.pm line 71. Compilation failed in require at /usr/local/bin/spamassassin line 80. BEGIN failed--compilation aborted at /usr/local/bin/spamassassin line 80. ClamAV update process started at Thu Jun 23 15:43:00 2011 main.cld is up to date (version: 53, sigs: 846214, f-level: 53, builder: sven) daily.cld is up to date (version: 13231, sigs: 130699, f-level: 60, builder: arnaud) bytecode.cld is up to date (version: 143, sigs: 40, f-level: 60, builder: edwin) spamd not running? (check /var/run/spamd/spamd.pid). Starting spamd. Can't locate NetAddr/IP.pm in @INC (@INC contains: /usr/local/lib/perl5/site_perl/5.14.0 /usr/local/lib/perl5/5.14.1/BSDPAN /usr/local/lib/perl5/site_perl/5.14.1/mach /usr/local/lib/perl5/site_perl/5.14.1 /usr/local/lib/perl5/5.14.1/mach /usr/local/lib/perl5/5.14.1) at /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/NetSet.pm line 25. BEGIN failed--compilation aborted at /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/NetSet.pm line 25. Compilation failed in require at /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/Conf.pm line 86. BEGIN failed--compilation aborted at /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/Conf.pm line 86. Compilation failed in require at /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin.pm line 71. BEGIN failed--compilation aborted at /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin.pm line 71. Compilation failed in require at /usr/local/bin/spamd line 85. BEGIN failed--compilation aborted at /usr/local/bin/spamd line 85. Can't locate NetAddr/IP.pm in @INC (@INC contains: /usr/local/lib/perl5/site_perl/5.14.0 /usr/local/lib/perl5/5.14.1/BSDPAN /usr/local/lib/perl5/site_perl/5.14.1/mach /usr/local/lib/perl5/site_perl/5.14.1 /usr/local/lib/perl5/5.14.1/mach /usr/local/lib/perl5/5.14.1) at /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/NetSet.pm line 25. BEGIN failed--compilation aborted at /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/NetSet.pm line 25. Compilation failed in require at /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/Conf.pm line 86. BEGIN failed--compilation aborted at /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/Conf.pm line 86. Compilation failed in require at /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin.pm line 71. BEGIN failed--compilation aborted at /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin.pm line 71. Compilation failed in require at /usr/local/bin/spamassassin line 80. BEGIN failed--compilation aborted at /usr/local/bin/spamassassin line 80. --- cut --- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org&quo
Installing X11 gives perl version conflict
FreeBSD 8.2 amd64 Attempting to install X11 server. Attempt to install package xf86-video-fbdev-0.4.2.tbz gives conflict between perl-5.10.1_3 and perl-5.12.3 even when installing into clean directory tree. # mkdir /tmp/test_pkg_install # export PKG_DBDIR=/tmp/test_pkg_install/var/db/pkg # pkg_add -P /tmp/test_pkg_install/ xf86-video-fbdev-0.4.2.tbz Note that some of the standard modules are provided as separate ports since they require extra dependencies: bsddb databases/py-bsddb gdbm databases/py-gdbm sqlite3 databases/py-sqlite3 tkinter x11-toolkits/py-tkinter Install them as needed. Removing stale symlinks from /usr/bin... Removing /usr/bin/perl Removing /usr/bin/perl5 Done. Creating various symlinks in /usr/bin... Symlinking /tmp/test_pkg_install//bin/perl5.12.3 to /usr/bin/perl Symlinking /tmp/test_pkg_install//bin/perl5.12.3 to /usr/bin/perl5 Done. Cleaning up /etc/make.conf... Done. Spamming /etc/make.conf... Done. Cleaning up /etc/manpath.config... Done. Spamming /etc/manpath.config... Done. Running fc-cache to build fontconfig cache... Fontconfig error: Cannot load default config file /usr/local/lib/X11/fonts: caching, new cache contents: 0 fonts, 1 dirs /usr/local/lib/X11/fonts/local: caching, new cache contents: 0 fonts, 0 dirs /var/db/fontconfig: cleaning cache directory fc-cache: succeeded * Although libxcb can yield dramatic improvements in speed, memory footprint, and responsiveness, and will probably become the default Xlib for X.org/freedesktop.org, it is still experimental software. Some broken callers will abort() on locking assertion failures. As a temporary workaround, set LIBXCB_ALLOW_SLOPPY_LOCK in your environment to skip the abort(). This may result in noisy stacktrace printing. * pkg_add: package 'perl-5.10.1_3' conflicts with perl-5.12.3 pkg_add: please use pkg_delete first to remove conflicting package(s) or -f to force installation pkg_add: autoload of dependency '/ro/dist/freebsd/freebsd_8.2/amd64/packages/perl-5.10.1_3.tbz' failed! pkg_add: autoload of dependency '/ro/dist/freebsd/freebsd_8.2/amd64/packages/glib-2.26.1_1.tbz' failed! pkg_add: package 'perl-5.10.1_3' conflicts with perl-5.12.3 pkg_add: please use pkg_delete first to remove conflicting package(s) or -f to force installation pkg_add: autoload of dependency '/ro/dist/freebsd/freebsd_8.2/amd64/packages/perl-5.10.1_3.tbz' failed! pkg_add: package 'perl-5.10.1_3' conflicts with perl-5.12.3 pkg_add: please use pkg_delete first to remove conflicting package(s) or -f to force installation pkg_add: autoload of dependency '/ro/dist/freebsd/freebsd_8.2/amd64/packages/perl-5.10.1_3.tbz' failed! pkg_add: autoload of dependency '/ro/dist/freebsd/freebsd_8.2/amd64/packages/glib-2.26.1_1.tbz' failed! pkg_add: autoload of dependency '/ro/dist/freebsd/freebsd_8.2/amd64/packages/gamin-0.1.10_4.tbz' failed! ... Hiding perl-5.10.1_3 from pkg_add doesn't work: pkg_add: could not find package perl-5.10.1_3 ! Hiding perl-5.12.3 from pkg_add doesn't work: pkg_add: could not find package perl-5.12.3 ! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Spamassassin not working after update of Perl
On 23 Jun 2011, at 21:37, Matthew Seaman wrote: > On 23/06/2011 14:55, Damien Fleuriot wrote: >> I have updated my Perl version yesterday but now my Spamd doesn't work >>> anymore. >>> Can someone hint me how to solve this? > > You need to reinstall all perl modules if you upgrade perl from 5.10.x > or 5.12.x to 5.14.1. This is explained in UPDATING. > > If you do it right, there should be pretty much nothing left in > /usr/local/lib/perl5/5.X.Y where 5.X.Y is the version you're upgrading > from. Specifically reinstall p5-NetAddr-IP and p5-Net-DNS > >Cheers, > >Matthew > > -- > Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard > Flat 3 > PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate > JID: matt...@infracaninophile.co.uk Kent, CT11 9PW > You're totally misquoting me as I'm not the OP but I'll live ;)___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Spamassassin not working after update of Perl
On 23/06/2011 14:55, Damien Fleuriot wrote: > I have updated my Perl version yesterday but now my Spamd doesn't work >> anymore. >> Can someone hint me how to solve this? You need to reinstall all perl modules if you upgrade perl from 5.10.x or 5.12.x to 5.14.1. This is explained in UPDATING. If you do it right, there should be pretty much nothing left in /usr/local/lib/perl5/5.X.Y where 5.X.Y is the version you're upgrading from. Specifically reinstall p5-NetAddr-IP and p5-Net-DNS Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: Spamassassin not working after update of Perl
On 6/23/11 3:51 PM, Jos Chrispijn wrote: > I have updated my Perl version yesterday but now my Spamd doesn't work > anymore. > Can someone hint me how to solve this? > > thanks, > Jos Chrispijn > > Pls see output: > > Can't locate Net/DNS.pm in @INC (@INC contains: > /usr/local/lib/perl5/site_perl/5.14.0 /usr/local/lib/perl5/5.14.1/BSDPAN > /usr/local/lib/perl5/site_perl/5.14.1/mach > /usr/local/lib/perl5/site_perl/5.14.1 /usr/local/lib/perl5/5.14.1/mach > /usr/local/lib/perl5/5.14.1) at /usr/local/bin/sa-update line 80. > BEGIN failed--compilation aborted at /usr/local/bin/sa-update line 80. > > Can't locate Net/DNS.pm in @INC (@INC contains: > /usr/local/lib/perl5/site_perl/5.14.0 /usr/local/lib/perl5/5.14.1/BSDPAN > /usr/local/lib/perl5/site_perl/5.14.1/mach > /usr/local/lib/perl5/site_perl/5.14.1 /usr/local/lib/perl5/5.14.1/mach > /usr/local/lib/perl5/5.14.1) at /usr/local/bin/sa-update line 80. > BEGIN failed--compilation aborted at /usr/local/bin/sa-update line 80. > > Can't locate NetAddr/IP.pm in @INC (@INC contains: > /usr/local/lib/perl5/site_perl/5.14.0 /usr/local/lib/perl5/5.14.1/BSDPAN > /usr/local/lib/perl5/site_perl/5.14.1/mach > /usr/local/lib/perl5/site_perl/5.14.1 /usr/local/lib/perl5/5.14.1/mach > /usr/local/lib/perl5/5.14.1) at > /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/NetSet.pm line 25. > > BEGIN failed--compilation aborted at > /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/NetSet.pm line 25. > Compilation failed in require at > /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/Conf.pm line 86. > BEGIN failed--compilation aborted at > /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/Conf.pm line 86. > Compilation failed in require at > /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin.pm line 71. > BEGIN failed--compilation aborted at > /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin.pm line 71. > Compilation failed in require at /usr/local/bin/spamassassin line 80. > BEGIN failed--compilation aborted at /usr/local/bin/spamassassin line 80. > ClamAV update process started at Thu Jun 23 15:43:00 2011 > main.cld is up to date (version: 53, sigs: 846214, f-level: 53, builder: > sven) > daily.cld is up to date (version: 13231, sigs: 130699, f-level: 60, > builder: arnaud) > bytecode.cld is up to date (version: 143, sigs: 40, f-level: 60, > builder: edwin) > spamd not running? (check /var/run/spamd/spamd.pid). > Starting spamd. > > Can't locate NetAddr/IP.pm in @INC (@INC contains: > /usr/local/lib/perl5/site_perl/5.14.0 /usr/local/lib/perl5/5.14.1/BSDPAN > /usr/local/lib/perl5/site_perl/5.14.1/mach > /usr/local/lib/perl5/site_perl/5.14.1 /usr/local/lib/perl5/5.14.1/mach > /usr/local/lib/perl5/5.14.1) at > /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/NetSet.pm line 25. > > BEGIN failed--compilation aborted at > /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/NetSet.pm line 25. > Compilation failed in require at > /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/Conf.pm line 86. > BEGIN failed--compilation aborted at > /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/Conf.pm line 86. > Compilation failed in require at > /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin.pm line 71. > BEGIN failed--compilation aborted at > /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin.pm line 71. > Compilation failed in require at /usr/local/bin/spamd line 85. > BEGIN failed--compilation aborted at /usr/local/bin/spamd line 85. > > Can't locate NetAddr/IP.pm in @INC (@INC contains: > /usr/local/lib/perl5/site_perl/5.14.0 /usr/local/lib/perl5/5.14.1/BSDPAN > /usr/local/lib/perl5/site_perl/5.14.1/mach > /usr/local/lib/perl5/site_perl/5.14.1 /usr/local/lib/perl5/5.14.1/mach > /usr/local/lib/perl5/5.14.1) at > /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/NetSet.pm line 25. > > BEGIN failed--compilation aborted at > /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/NetSet.pm line 25. > Compilation failed in require at > /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/Conf.pm line 86. > BEGIN failed--compilation aborted at > /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/Conf.pm line 86. > Compilation failed in require at > /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin.pm line 71. > BEGIN failed--compilation aborted at > /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin.pm line 71. > Compilation failed in require at /usr/local/bin/spamassassin line 80. > BEGIN failed--compilation aborted at /usr/local/bin/spamassassin line 80. > > --- cut --- > _______ &
Spamassassin not working after update of Perl
I have updated my Perl version yesterday but now my Spamd doesn't work anymore. Can someone hint me how to solve this? thanks, Jos Chrispijn Pls see output: Can't locate Net/DNS.pm in @INC (@INC contains: /usr/local/lib/perl5/site_perl/5.14.0 /usr/local/lib/perl5/5.14.1/BSDPAN /usr/local/lib/perl5/site_perl/5.14.1/mach /usr/local/lib/perl5/site_perl/5.14.1 /usr/local/lib/perl5/5.14.1/mach /usr/local/lib/perl5/5.14.1) at /usr/local/bin/sa-update line 80. BEGIN failed--compilation aborted at /usr/local/bin/sa-update line 80. Can't locate Net/DNS.pm in @INC (@INC contains: /usr/local/lib/perl5/site_perl/5.14.0 /usr/local/lib/perl5/5.14.1/BSDPAN /usr/local/lib/perl5/site_perl/5.14.1/mach /usr/local/lib/perl5/site_perl/5.14.1 /usr/local/lib/perl5/5.14.1/mach /usr/local/lib/perl5/5.14.1) at /usr/local/bin/sa-update line 80. BEGIN failed--compilation aborted at /usr/local/bin/sa-update line 80. Can't locate NetAddr/IP.pm in @INC (@INC contains: /usr/local/lib/perl5/site_perl/5.14.0 /usr/local/lib/perl5/5.14.1/BSDPAN /usr/local/lib/perl5/site_perl/5.14.1/mach /usr/local/lib/perl5/site_perl/5.14.1 /usr/local/lib/perl5/5.14.1/mach /usr/local/lib/perl5/5.14.1) at /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/NetSet.pm line 25. BEGIN failed--compilation aborted at /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/NetSet.pm line 25. Compilation failed in require at /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/Conf.pm line 86. BEGIN failed--compilation aborted at /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/Conf.pm line 86. Compilation failed in require at /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin.pm line 71. BEGIN failed--compilation aborted at /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin.pm line 71. Compilation failed in require at /usr/local/bin/spamassassin line 80. BEGIN failed--compilation aborted at /usr/local/bin/spamassassin line 80. ClamAV update process started at Thu Jun 23 15:43:00 2011 main.cld is up to date (version: 53, sigs: 846214, f-level: 53, builder: sven) daily.cld is up to date (version: 13231, sigs: 130699, f-level: 60, builder: arnaud) bytecode.cld is up to date (version: 143, sigs: 40, f-level: 60, builder: edwin) spamd not running? (check /var/run/spamd/spamd.pid). Starting spamd. Can't locate NetAddr/IP.pm in @INC (@INC contains: /usr/local/lib/perl5/site_perl/5.14.0 /usr/local/lib/perl5/5.14.1/BSDPAN /usr/local/lib/perl5/site_perl/5.14.1/mach /usr/local/lib/perl5/site_perl/5.14.1 /usr/local/lib/perl5/5.14.1/mach /usr/local/lib/perl5/5.14.1) at /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/NetSet.pm line 25. BEGIN failed--compilation aborted at /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/NetSet.pm line 25. Compilation failed in require at /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/Conf.pm line 86. BEGIN failed--compilation aborted at /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/Conf.pm line 86. Compilation failed in require at /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin.pm line 71. BEGIN failed--compilation aborted at /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin.pm line 71. Compilation failed in require at /usr/local/bin/spamd line 85. BEGIN failed--compilation aborted at /usr/local/bin/spamd line 85. Can't locate NetAddr/IP.pm in @INC (@INC contains: /usr/local/lib/perl5/site_perl/5.14.0 /usr/local/lib/perl5/5.14.1/BSDPAN /usr/local/lib/perl5/site_perl/5.14.1/mach /usr/local/lib/perl5/site_perl/5.14.1 /usr/local/lib/perl5/5.14.1/mach /usr/local/lib/perl5/5.14.1) at /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/NetSet.pm line 25. BEGIN failed--compilation aborted at /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/NetSet.pm line 25. Compilation failed in require at /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/Conf.pm line 86. BEGIN failed--compilation aborted at /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin/Conf.pm line 86. Compilation failed in require at /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin.pm line 71. BEGIN failed--compilation aborted at /usr/local/lib/perl5/site_perl/5.14.0/Mail/SpamAssassin.pm line 71. Compilation failed in require at /usr/local/bin/spamassassin line 80. BEGIN failed--compilation aborted at /usr/local/bin/spamassassin line 80. --- cut --- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: perl-threaded
On Mon, May 23, 2011 at 05:50:39PM -0400, Alejandro Imass wrote: > Not necessarily, many cpan modules are either thread unaware/innocuous > or thread safe, though there are exceptions. > I have re-compiled Perl with threads with pre-installed libraries and > never had a problem. > > You will surely know which things fail when they blow-up or leak you > to death, when you use threading of course. Especially long-running > software like mod_perl. But for that, you always have > maxrequestsperchild ;-) > > Now that I mention it, mod_perl would probably need rebuilding IMHO > just to be on the safe side, wherever _that_ is with threads ;-) > > Joking aside, I have scaled tremendously with apache mod_perl + > mod_worker a rare but exquisite high-scale Web software recipe. Hi Alejandro - I did encounter a few issues, rebuilt them all and it's good. Thanks for your reply. jamie ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: perl-threaded
Not necessarily, many cpan modules are either thread unaware/innocuous or thread safe, though there are exceptions. I have re-compiled Perl with threads with pre-installed libraries and never had a problem. You will surely know which things fail when they blow-up or leak you to death, when you use threading of course. Especially long-running software like mod_perl. But for that, you always have maxrequestsperchild ;-) Now that I mention it, mod_perl would probably need rebuilding IMHO just to be on the safe side, wherever _that_ is with threads ;-) Joking aside, I have scaled tremendously with apache mod_perl + mod_worker a rare but exquisite high-scale Web software recipe. Best -- Alejandro Imass On Mon, May 23, 2011 at 4:20 PM, Jamie Paul Griffin wrote: > I have rebuilt my perl5.14 with threading support. do I need to rebuild my > perl-linked ports again now i've made this change? > > jamie > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
perl-threaded
I have rebuilt my perl5.14 with threading support. do I need to rebuild my perl-linked ports again now i've made this change? jamie ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Trying to Make an Alias Execute a Perl Script
At 02:42 PM 2/5/2011, pe...@vfemail.net wrote:
> * * *
>I've tried this entry in my /etc/mail/aliases file, but it returns an empty
>e-mail messages:
>
> extract: "| perl -wne 'while(/[\S\.]+@[\S\.]+\w+/g){print "$&\n"}' | mail
> user"
>
>[and this one]:
>
> extract: "| cat > datafile | perl -wne
> 'while(/[\S\.]+@[\S\.]+\w+/g){print "$&\n"}' < datafile | mail user"
>
>but [they] return an empty e-mail message rather than a list of e-mail
>addresses.
>
>What am I overlooking?
A kind soul helped me figure out how to make this work. This e-mail alias:
extract: "| cat > /home/peter/datafile | /home/peter/extract.pl <
/home/peter/datafile | mail -s \"Results\" user
combined with this Perl script:
#!/usr/bin/perl
while ()
{ while(/[\S\.]+@[\S\.]+\w+/g){print "$&\n"};
};
delivers the desired list of e-mail addresses.
-
This message sent via VFEmail.net
http://www.vfemail.net
$14.95 Lifetime accounts! 15GB disk! No bandwidth quotas!
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Trying to Make an Alias Execute a Perl Script
I have a couple of entries in my /etc/mail/aliases that manipulate the contents
of an e-mail message. For example,
file: "| cat > /home/user/file.incoming"
receives an e-mail message and writes it to the hard drive. Another example:
format: "| sed 's/^.$/~~/g' | sed 's/^$/~~/g' | tr -s ' ' ' ' | fmt 63 64
| sed 's/^ *//g' | tr '~' '\\012\' | mail user"
receives a message, reformats the contents, and sends the reformatted material
back to me by e-mail.
I'm trying to create a new alias that will receive an e-mail message, use a
Perl command to scan for for all e-mail addresses, and return a list of any
e-mail addresses found to me by e-mail.
This little Perl command does a great job of identifying e-mail addresses and
producing a list of them:
perl -wne 'while(/[\S\.]+@[\S\.]+\w+/g){print "$&\n"}'
and I can use this from the command line these ways to extract e-mail addresses
from a file:
perl -wne 'while(/[\S\.]+@[\S\.]+\w+/g){print "$&\n"}' datafile
perl -wne 'while(/[\S\.]+@[\S\.]+\w+/g){print "$&\n"}' < datafile
cat datafile | perl -wne 'while(/[\S\.]+@[\S\.]+\w+/g){print "$&\n"}'
I've tried this entry in my /etc/mail/aliases file, but it returns an empty
e-mail messages:
extract: "| perl -wne 'while(/[\S\.]+@[\S\.]+\w+/g){print "$&\n"}' | mail
user"
I tried modifying it to create a datafile and then examine the datafile:
extract: "| cat > datafile | perl -wne 'while(/[\S\.]+@[\S\.]+\w+/g){print
"$&\n"}' < datafile | mail user"
but it is still returning an empty e-mail message rather than a list of e-mail
addresses.
What am I overlooking?
-
This message sent via VFEmail.net
http://www.vfemail.net
$14.95 Lifetime accounts! 15GB disk! No bandwidth quotas!
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
perl update again
Hi! Again me with the perl update from 5.8 to 5.12. I did portmaster -o lang/perl5.12 /lang/perl5.8 and upgrade was without problem. Than I ran portmaster -r perl- and there were also for rebuild "arts", "qt33" which I dont have installed and portmaster --check-depends doesn't shows any problems. I went back to version 5.8 because I don't want to install those ports which I don't have. Did I do something wrong? Thanks in advance. Mitja http://jpgmag.com/people/lumiwa ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: perl - update
On Wed, 2 Feb 2011 07:47:02 -0600 ajtiM wrote: > Thank you very much. But I like to know if I need to change entry in > make.conf: > # added by use.perl 2010-11-05 > 17:40:46 PERL_VERSION=5.8.9 > > to PERL_VERSION=5.12.3 > > or just delete those line. You don't need to do anything, it'll be updated by installing the new version of perl. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: perl - update
On Wednesday February 2 2011 07:20:43 RW wrote:
> On Wed, 2 Feb 2011 07:03:32 -0600
>
> ajtiM wrote:
> > Hi!
> >
> > My system: FreeBSD 8.1
> >
> > I like to update perl to higher version and I don't want to screw
> > up... I red /usr/ports/UPDATING:
> >
> > "perl-after-upgrade" script supplied with lang/perl5.12
> >
> > If I update to perl 5.12.3 is it enough that I run above script,
> > please? In /etc/make.conf I have:
> > # added by use.perl 2010-11-05
> > 17:40:46 PERL_VERSION=5.8.9
> >
> > I have above from version 8.0. Do I need to change version from 5.8.9
> > to 5.12 or to 5.12.3?
>
> In UPDATING it also says:
>
> " If you want to switch to lang/perl5.12 from lang/perl5.{8,10} please
> follow instructions in the entry 20100715 in this file."
>
>
> Note that 5.8.9 is built out of a different port to 5.12.3
>
Thank you very much. But I like to know if I need to change entry in
make.conf:
# added by use.perl 2010-11-05
17:40:46 PERL_VERSION=5.8.9
to PERL_VERSION=5.12.3
or just delete those line.
Thanks in advance.
Mitja
http://jpgmag.com/people/lumiwa
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: perl - update
On Wed, 2 Feb 2011 07:03:32 -0600
ajtiM wrote:
> Hi!
>
> My system: FreeBSD 8.1
>
> I like to update perl to higher version and I don't want to screw
> up... I red /usr/ports/UPDATING:
>
> "perl-after-upgrade" script supplied with lang/perl5.12
>
> If I update to perl 5.12.3 is it enough that I run above script,
> please? In /etc/make.conf I have:
> # added by use.perl 2010-11-05
> 17:40:46 PERL_VERSION=5.8.9
>
> I have above from version 8.0. Do I need to change version from 5.8.9
> to 5.12 or to 5.12.3?
>
In UPDATING it also says:
" If you want to switch to lang/perl5.12 from lang/perl5.{8,10} please
follow instructions in the entry 20100715 in this file."
Note that 5.8.9 is built out of a different port to 5.12.3
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
perl - update
Hi! My system: FreeBSD 8.1 I like to update perl to higher version and I don't want to screw up... I red /usr/ports/UPDATING: "perl-after-upgrade" script supplied with lang/perl5.12 If I update to perl 5.12.3 is it enough that I run above script, please? In /etc/make.conf I have: # added by use.perl 2010-11-05 17:40:46 PERL_VERSION=5.8.9 I have above from version 8.0. Do I need to change version from 5.8.9 to 5.12 or to 5.12.3? Thank you very much. Mitja http://jpgmag.com/people/lumiwa ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: switching to perl-threaded
On 01/22/11 10:25, Robert Fitzpatrick wrote: I guess I did a stupid thing to 'make deinstall' and then 'make reinstall' to change my perl option for WITH_THREADS. Now it seems all my modules are lost as my LWP::Simple does not work anymore. I then tried to pkg_delete that, successful, and 'perl -MCPAN -e "install LWP::Simple' only to fail with a lot of these... Can't load '/usr/local/lib/perl5/site_perl/5.10.1/mach/auto/HTML/Parser/Parser.so What is the best way to handle getting my modules working under threaded perl? That module in particular was done through CPAN because I couldn't seem to find a port for it. Thanks, Robert -- Robert ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" cd /usr/ports/lang/perl && make config (turn on threads) portupgrade -rf lang/perl ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
switching to perl-threaded
I guess I did a stupid thing to 'make deinstall' and then 'make reinstall' to change my perl option for WITH_THREADS. Now it seems all my modules are lost as my LWP::Simple does not work anymore. I then tried to pkg_delete that, successful, and 'perl -MCPAN -e "install LWP::Simple' only to fail with a lot of these... > Can't load > '/usr/local/lib/perl5/site_perl/5.10.1/mach/auto/HTML/Parser/Parser.so What is the best way to handle getting my modules working under threaded perl? That module in particular was done through CPAN because I couldn't seem to find a port for it. Thanks, Robert -- Robert ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: a perl question
On 05/01/2011 22:15, RW wrote: > Personally I find that using cat makes things simpler and less error > prone when reusing pipelines in shell history. > > For example it's easier to edit > > cat file | foo > > into > > cat file | bar | foo > or cat file? | foo > > than editing > > foo < file > > into > > bar < file | foo > or cat file? | foo Little known factoid -- shell redirections can occur *anywhere* on the command line. % > foo cat abcdefghijklmnopqrstuvwxyz % < foo tr 'a-z' 'm-za-l' mnopqrstuvwxyzabcdefghijkl Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: a perl question
On Wed, 5 Jan 2011 15:13:02 -0700 Chad Perrin wrote: > In this case, example was: > > cat file | foo arg > > . . . where it could have been: > > foo arg file > > That's just kind of absurd. I mean, that sort of usage (foo arg > file) is exactly the purpose for which grep was designed. > Obviously, I'm talking about the general case. If I'd meant grep I'd have written grep and not foo. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: a perl question
On Wed, Jan 05, 2011 at 10:15:38PM +, RW wrote: > > For example it's easier to edit > > cat file | foo > > into > > cat file | bar | foo > or cat file? | foo > > than editing > > foo < file > > into > > bar < file | foo > or cat file? | foo In this case, example was: cat file | foo arg . . . where it could have been: foo arg file That's just kind of absurd. I mean, that sort of usage (foo arg file) is exactly the purpose for which grep was designed. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] pgpuPZgJNS4Mz.pgp Description: PGP signature
Re: a perl question
On Wed, 5 Jan 2011 08:05:14 -0800 Chip Camden wrote: > Quoth Chad Perrin on Tuesday, 04 January 2011: > > The weirdest thing about most useless uses of cat is that not using > > cat would actually be a little clearer and involve fewer keystrokes > > -- as in this case. > > > I blame OOP. Programmer thinks about the data stream before they > think about the process. It's a nouns-first orientation. You might easily get the same prejudice from data flow diagrams - or plumbing. Personally I find that using cat makes things simpler and less error prone when reusing pipelines in shell history. For example it's easier to edit cat file | foo into cat file | bar | foo or cat file? | foo than editing foo < file into bar < file | foo or cat file? | foo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: a perl question
On Thu, Jan 06, 2011 at 12:07:13AM +1100, Ian Smith wrote: > > Do you know of any 'less useless' or more economical way to do such as: > > % cat /boot/boot1 /boot/boot2 | diff - /boot/boot > % Actually, that looks like a useful use of cat, whose original purpose it is to concatenate the contents of two files. `cat /boot/boot1 /boot/boot2` concatenates the contents of two files, so that the resulting single text stream can be treated as a file to be compared by diff to `/boot/boot`. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] pgpTrSURKXqIn.pgp Description: PGP signature
Re: a perl question
Quoth Ian Smith on Thursday, 06 January 2011: > In freebsd-questions Digest, Vol 344, Issue 4, Message: 14 > On Tue, 4 Jan 2011 23:24:01 -0700 Chad Perrin wrote: > > On Tue, Jan 04, 2011 at 09:33:03AM -0800, Randal L. Schwartz wrote: > > > > "Patrick" == Patrick Bihan-Faou > writes: > > > > > > Patrick> cat asdf.txt | grep -v XYZ | grep -v bla > > > > > > And yet, you still have the "Useless Use of Cat". > > > > The weirdest thing about most useless uses of cat is that not using cat > > would actually be a little clearer and involve fewer keystrokes -- as in > > this case. > > Do you know of any 'less useless' or more economical way to do such as: > > % cat /boot/boot1 /boot/boot2 | diff - /boot/boot > % > > ?, Ian > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" Here you're using cat for what it was intended -- conCATenation. It's the right tool for that job. -- Sterling (Chip) Camden| sterl...@camdensoftware.com | 2048D/3A978E4F http://camdensoftware.com | http://chipstips.com| http://chipsquips.com pgp6YwaaNVSZJ.pgp Description: PGP signature
Re: a perl question
Quoth Chad Perrin on Tuesday, 04 January 2011: > On Tue, Jan 04, 2011 at 09:33:03AM -0800, Randal L. Schwartz wrote: > > > "Patrick" == Patrick Bihan-Faou > > > writes: > > > > Patrick> cat asdf.txt | grep -v XYZ | grep -v bla > > > > And yet, you still have the "Useless Use of Cat". > > The weirdest thing about most useless uses of cat is that not using cat > would actually be a little clearer and involve fewer keystrokes -- as in > this case. > > -- > Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] I blame OOP. Programmer thinks about the data stream before they think about the process. It's a nouns-first orientation. -- Sterling (Chip) Camden| sterl...@camdensoftware.com | 2048D/3A978E4F http://camdensoftware.com | http://chipstips.com| http://chipsquips.com pgpaYeod9JmjW.pgp Description: PGP signature
Re: a perl question
In freebsd-questions Digest, Vol 344, Issue 4, Message: 14 On Tue, 4 Jan 2011 23:24:01 -0700 Chad Perrin wrote: > On Tue, Jan 04, 2011 at 09:33:03AM -0800, Randal L. Schwartz wrote: > > > "Patrick" == Patrick Bihan-Faou > > > writes: > > > > Patrick> cat asdf.txt | grep -v XYZ | grep -v bla > > > > And yet, you still have the "Useless Use of Cat". > > The weirdest thing about most useless uses of cat is that not using cat > would actually be a little clearer and involve fewer keystrokes -- as in > this case. Do you know of any 'less useless' or more economical way to do such as: % cat /boot/boot1 /boot/boot2 | diff - /boot/boot % ?, Ian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: best way to rebuild all perl ports
> Check so you not have "perl-threaded". If you have you must type > "portupgrade -fr perl-treaded". Othervise it just do nothing. wow that was easy. this was the problem and it's now rebuilding everything. thanks to everyone for their advice. jamie ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
