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
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
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 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.
Slinks away in shame ...
___
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 waves 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
Perl upgrade problem...
Up till now I've kept Perl on my machine at 5.8.9. I now see from UPDATING that upgrading to 5.10 is recommended. However, when I follow the instructions, I get the following error: laptop# portupgrade -o lang/perl5.10 -f perl-5.8.9_3 --- Upgrading 'perl-5.8.9_3' to 'perl-5.10.1' (lang/perl5.10) --- Building '/usr/ports/lang/perl5.10' === Cleaning for perl-5.10.1 === perl-5.10.1 conflicts with installed package(s): perl-5.8.9_3 They install files into the same place. Please remove them first with pkg_delete(1). *** Error code 1 Stop in /usr/ports/lang/perl5.10. *** Error code 1 Stop in /usr/ports/lang/perl5.10. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade20100212-42732-1onozbt-0 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=perl-5.8.9_3 UPGRADE_PORT_VER=5.8.9_3 make ** Fix the problem and try again. ** Listing the failed packages (-:ignored / *:skipped / !:failed) ! lang/perl5.10 (perl-5.8.9_3) (unknown build error) Any advice on how to fix? Thanks in advance. Peter Harrison. ___ 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 problem...
On Fri, Feb 12, 2010 at 2:44 PM, Peter Harrison peter.piggy...@virgin.netwrote: Up till now I've kept Perl on my machine at 5.8.9. I now see from UPDATING that upgrading to 5.10 is recommended. However, when I follow the instructions, I get the following error: laptop# portupgrade -o lang/perl5.10 -f perl-5.8.9_3 if you're referring to this: 20090911: AFFECTS: users of lang/perl5.10 AUTHOR: s...@freebsd.org lang/perl5.10 has been updated to 5.10.1. You should update everything that depends on perl. The easiest way to do that is to use perl-after-upgrade script supplied with lang/perl5.10. Please see its manual page for details. If you want switch to lang/perl5.10 from lang/perl5.8 please follow instructions in the entry 20090328 in this file. Then you have misunderstood what it's saying. That only applies to folks already running 5.10 and if you have no need for that then do nothing further. If you really believe you need to run 5.10 then you should follow the complete instructions from the entry. -- Adam Vande More ___ 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 problem...
On 12/02/2010 20:50, Adam Vande More wrote: On Fri, Feb 12, 2010 at 2:44 PM, Peter Harrison peter.piggy...@virgin.netwrote: Up till now I've kept Perl on my machine at 5.8.9. I now see from UPDATING that upgrading to 5.10 is recommended. However, when I follow the instructions, I get the following error: laptop# portupgrade -o lang/perl5.10 -f perl-5.8.9_3 if you're referring to this: 20090911: AFFECTS: users of lang/perl5.10 AUTHOR: s...@freebsd.org lang/perl5.10 has been updated to 5.10.1. You should update everything that depends on perl. The easiest way to do that is to use perl-after-upgrade script supplied with lang/perl5.10. Please see its manual page for details. If you want switch to lang/perl5.10 from lang/perl5.8 please follow instructions in the entry 20090328 in this file. Then you have misunderstood what it's saying. That only applies to folks already running 5.10 and if you have no need for that then do nothing further. If you really believe you need to run 5.10 then you should follow the complete instructions from the entry. Err... he's following the right instructions. It's just that since those instructions were written there have been some badly thought-out changes in bsd.ports.mk. Any time you try and use portupgrade to replace one port with another now, you'll likely need to tell it to ignore CONFLICTS settings: # portupgrade -m DISABLE_CONFLICTS=yes -o lang/perl5.10 \ -f perl-5.8.9_3 Then reinstall every port that depends on perl -- you can't use perl_after_upgrade for this update: the delta in version numbers is too large. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard, Flat 3 Black Earth Consulting Ramsgate Kent, CT11 9PW Free and Open Source Solutions Tel: +44 (0)1843 580647 signature.asc Description: OpenPGP digital signature
Re: Perl upgrade problem...
On Fri, Feb 12, 2010 at 3:03 PM, Matthew Seaman m.sea...@black-earth.co.ukwrote: Err... he's following the right instructions. ports/UPDATING does not recommend to upgrade. -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Perl upgrade problem...
On Fri, Feb 12, 2010 at 3:07 PM, Adam Vande More amvandem...@gmail.comwrote: On Fri, Feb 12, 2010 at 3:03 PM, Matthew Seaman m.sea...@black-earth.co.uk wrote: Err... he's following the right instructions. ports/UPDATING does not recommend to upgrade. I mean does not recommend going from 5.8 to 5.10 as the op has done. You are correctly in the previous entry containing incorrect instructions. -- Adam Vande More ___ 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 problem...
Friday, 12 February 2010 at 14:50:56 -0600, Adam Vande More said: On Fri, Feb 12, 2010 at 2:44 PM, Peter Harrison peter.piggy...@virgin.netwrote: Up till now I've kept Perl on my machine at 5.8.9. I now see from UPDATING that upgrading to 5.10 is recommended. However, when I follow the instructions, I get the following error: laptop# portupgrade -o lang/perl5.10 -f perl-5.8.9_3 if you're referring to this: 20090911: AFFECTS: users of lang/perl5.10 AUTHOR: s...@freebsd.org lang/perl5.10 has been updated to 5.10.1. You should update everything that depends on perl. The easiest way to do that is to use perl-after-upgrade script supplied with lang/perl5.10. Please see its manual page for details. If you want switch to lang/perl5.10 from lang/perl5.8 please follow instructions in the entry 20090328 in this file. Then you have misunderstood what it's saying. That only applies to folks already running 5.10 and if you have no need for that then do nothing further. If you really believe you need to run 5.10 then you should follow the complete instructions from the entry. I don't need 5.10, but I was prompted to think about upgrading from 20100205. I was trying to follow 20090328, I ran pkgdb -Ff (no problem) then portupgrade -o lang/per5.10 -f perl-5.8.9 which generated the error given. Peter Harrison. -- Adam Vande More ___ 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 problem...
On Fri, Feb 12, 2010 at 3:26 PM, Peter Harrison peter.piggy...@virgin.netwrote: I don't need 5.10, but I was prompted to think about upgrading from 20100205. I was trying to follow 20090328, I ran pkgdb -Ff (no problem) then portupgrade -o lang/per5.10 -f perl-5.8.9 which generated the error given. Peter Harrison. i see, my port tree was out of date, sorry. -- Adam Vande More ___ 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 problem...
Friday, 12 February 2010 at 21:03:54 +, Matthew Seaman said: On 12/02/2010 20:50, Adam Vande More wrote: On Fri, Feb 12, 2010 at 2:44 PM, Peter Harrison peter.piggy...@virgin.netwrote: Up till now I've kept Perl on my machine at 5.8.9. I now see from UPDATING that upgrading to 5.10 is recommended. However, when I follow the instructions, I get the following error: laptop# portupgrade -o lang/perl5.10 -f perl-5.8.9_3 if you're referring to this: 20090911: AFFECTS: users of lang/perl5.10 AUTHOR: s...@freebsd.org lang/perl5.10 has been updated to 5.10.1. You should update everything that depends on perl. The easiest way to do that is to use perl-after-upgrade script supplied with lang/perl5.10. Please see its manual page for details. If you want switch to lang/perl5.10 from lang/perl5.8 please follow instructions in the entry 20090328 in this file. Then you have misunderstood what it's saying. That only applies to folks already running 5.10 and if you have no need for that then do nothing further. If you really believe you need to run 5.10 then you should follow the complete instructions from the entry. Err... he's following the right instructions. It's just that since those instructions were written there have been some badly thought-out changes in bsd.ports.mk. Any time you try and use portupgrade to replace one port with another now, you'll likely need to tell it to ignore CONFLICTS settings: # portupgrade -m DISABLE_CONFLICTS=yes -o lang/perl5.10 \ -f perl-5.8.9_3 Then reinstall every port that depends on perl -- you can't use perl_after_upgrade for this update: the delta in version numbers is too large. Cheers, Matthew OK - that seems inconvenient, but I guess it makes sense. I remember some stuff on the list about this earlier now that you mention it. Seems to have made a bit of a hassle of replacing one port with another. Thanks for the advice. Peter. -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard, Flat 3 Black Earth Consulting Ramsgate Kent, CT11 9PW Free and Open Source Solutions Tel: +44 (0)1843 580647 ___ 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
Hi Jerry, Jerry wrote: Perl-5.10 was released to the public over a year ago. Another year transpired before it was released into the ports system. There was an immediate problem that was corrected when the maintainer switched to 'bison' from 'YACC'. Other than that, it has performed flawlessly as far as I can tell. Thanks, I didn't know that as it only appeared in UPDATING at 280309. regards, Jos Chrispijn ___ 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
On Sat, 9 May 2009 08:31:45 -0500 (CDT) Lars Eighner luvbeas...@larseighner.com wrote: On Sat, 9 May 2009, Jos Chrispijn wrote: Lars Eighner wrote: On Sat, 9 May 2009, Jos Chrispijn wrote: You must be new around here. Yes, I am L-) The process described in UPDATING for upgrading to Perl 5.10 is relatively painless compared to previous perl upgrades. So much stuff depends upon perl that: [snip] Do you recommend having Perl updated or should I stay with 5.8? Unless you know there is something in 5.10 that you need now, I recommend waiting at least a little bit. Let the gotta-have-the-newest-shiny folks take the sharp edges off. Study the dependencies list from pkg_info and dependencies of any big thing you plan to install. If you are going to (re-)build something big or a lot of little things anyway, it may make sense to upgrade perl just before you do that so that rebuilding the ports that depend on perl will kill two birds with one stone. If such an opportunity doesn't arise, maybe do it anyway about the time of the first frost --- snuggle up in front of the blazing compiler and sip hot chocolate. Perl-5.10 was released to the public over a year ago. Another year transpired before it was released into the ports system. There was an immediate problem that was corrected when the maintainer switched to 'bison' from 'YACC'. Other than that, it has performed flawlessly as far as I can tell. -- Jerry ges...@yahoo.com The Martian Canals were clearly the Martian's last ditch effort! signature.asc Description: PGP signature
Perl upgrade
Not that I am that paranoid, but can someone tell me why Perl 5.8 is not automatically updated to 5.10 thru the ports, but (accordingly by UPDATING) has to be updated by some manual interaction? -- Jos Chrispijn ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Perl upgrade
On Sat, 09 May 2009 13:05:32 +0200 Jos Chrispijn j...@webrz.net wrote: Not that I am that paranoid, but can someone tell me why Perl 5.8 is not automatically updated to 5.10 thru the ports, but (accordingly by UPDATING) has to be updated by some manual interaction? That's the way the port system works. perl5.6, perl5.8 and perl5.10 are separate ports, making it automatic would involve forcing people off perl5.8 and marking it as moved. ___ 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
On Sat, 9 May 2009, Jos Chrispijn wrote: Not that I am that paranoid, but can someone tell me why Perl 5.8 is not automatically updated to 5.10 thru the ports, but (accordingly by UPDATING) has to be updated by some manual interaction? You must be new around here. The process described in UPDATING for upgrading to Perl 5.10 is relatively painless compared to previous perl upgrades. So much stuff depends upon perl that: 1) special treatment is required to be sure you end up with a system that is functional in practice, and 2) people should not be misled as to the extent of the work involved. Use pkg_info -R name of installed perl package to see what you may be in for. Perl was once (recently for some of us) part of the system. Logic may be on the side of considering it an application, but as a practical matter it is a distinction without a (big) difference. -- Lars Eighner http://www.larseighner.com/index.html 8800 N IH35 APT 1191 AUSTIN TX 78753-5266 ___ 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
Lars Eighner wrote: On Sat, 9 May 2009, Jos Chrispijn wrote: You must be new around here. Yes, I am L-) The process described in UPDATING for upgrading to Perl 5.10 is relatively painless compared to previous perl upgrades. So much stuff depends upon perl that: [snip] Do you recommend having Perl updated or should I stay with 5.8? thanks, Jos Chrispijn ___ 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
Jos Chrispijn wrote: Lars Eighner wrote: On Sat, 9 May 2009, Jos Chrispijn wrote: The process described in UPDATING for upgrading to Perl 5.10 is relatively painless compared to previous perl upgrades. So much stuff depends upon perl that: Do you recommend having Perl updated or should I stay with 5.8? I've updated a number of machines to perl-5.10, and apart from the sheer amount of stuff that needs re-installing it has been virtually painless. Most publicly available perl modules are written to be compatible with perl-5.8.3 or later and unless you're being bitten by some version specific bug there's no really pressing reason to upgrade to 5.10 right now. On the other hand, neither is there any really pressing reason /not/ to upgrade. It's all down to personal preference. However, I expect the consensus on the minimum supported version to change over time and more use to be made of 5.10 specific features, so I'd certainly recommend installing brand new machines with perl-5.10 in order to minimize the potential for future pain. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: Perl upgrade
On Sat, 9 May 2009, Jos Chrispijn wrote: Lars Eighner wrote: On Sat, 9 May 2009, Jos Chrispijn wrote: You must be new around here. Yes, I am L-) The process described in UPDATING for upgrading to Perl 5.10 is relatively painless compared to previous perl upgrades. So much stuff depends upon perl that: [snip] Do you recommend having Perl updated or should I stay with 5.8? Unless you know there is something in 5.10 that you need now, I recommend waiting at least a little bit. Let the gotta-have-the-newest-shiny folks take the sharp edges off. Study the dependencies list from pkg_info and dependencies of any big thing you plan to install. If you are going to (re-)build something big or a lot of little things anyway, it may make sense to upgrade perl just before you do that so that rebuilding the ports that depend on perl will kill two birds with one stone. If such an opportunity doesn't arise, maybe do it anyway about the time of the first frost --- snuggle up in front of the blazing compiler and sip hot chocolate. -- Lars Eighner http://www.larseighner.com/index.html 8800 N IH35 APT 1191 AUSTIN TX 78753-5266 ___ 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
On Sat, 9 May 2009, Matthew Seaman wrote: However, I expect the consensus on the minimum supported version to change over time and more use to be made of 5.10 specific features, so I'd certainly recommend installing brand new machines with perl-5.10 in order to minimize the potential for future pain. I concur. If you do the pkg_info thing and the list of stuff depending on perl is very short, by all means upgrade before it gets long. -- Lars Eighner http://www.larseighner.com/index.html 8800 N IH35 APT 1191 AUSTIN TX 78753-5266 ___ 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
Lars Eighner wrote: On Sat, 9 May 2009, Matthew Seaman wrote: I concur. If you do the pkg_info thing and the list of stuff depending on perl is very short, by all means upgrade before it gets long. After having some investigation on this subject, it comes clear to me that Perl is a very important part of my FreeBSD. Before that I considered it only as an app, nothing more than that *-) I did the update on a backup server and it took me 5 hours to get this done (going thru a full install of FreeBSD). Rebooted the system and so far no strange side-effects. I will though keep attention on evt. flaws on its behavior, allthough I expect the developer has it throuroughly tested before releasing it. thanks for sharing, -- Jos Chrispijn ___ 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: Can I resume the perl upgrade?
On Sun, Apr 12, 2009 at 12:05:50PM -0700, David Southwell typed: On Saturday 11 April 2009 17:20:56 Chris Rees wrote: I hope it is not too far off topic but: Can anyone tell me how to fix this one: Stale dependency: bsdpan-Pod-Perldoc-3.15 - perl-5.8.9_2 (lang/perl5.8): can't convert nil into string My update to 10 seems to be OK except for this.. I cannot find its origin so do not know what to deinstall and reinstall It would also be great to get all bsdpan into the pkgdb with their origins.. is there any way to do that? Thanks in advance David Perhaps you should start a new thread. Chris Tried that last week to no avail So asmy question was vaguely on topic I had hoped someone might be able to contribute something useful!! If you can send a reply-all to the list, you certainly can send a new question, can't you? Hijacking threads *is* considered rude/ignorant/dumb by some. That said, Pod::Perldoc seems to be part of perl-5.8.[8-9] on my systems, so unless you're doing some nonstandard things with this package, I suggest you just pkg_delete the bsdpan package and get on with it. Ruben No such luck!! Thank you for your contribution most helpful David ___ 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: Can I resume the perl upgrade?
On Tuesday 14 April 2009 05:20:35 Ruben de Groot wrote: On Sun, Apr 12, 2009 at 12:05:50PM -0700, David Southwell typed: On Saturday 11 April 2009 17:20:56 Chris Rees wrote: I hope it is not too far off topic but: Can anyone tell me how to fix this one: Stale dependency: bsdpan-Pod-Perldoc-3.15 - perl-5.8.9_2 (lang/perl5.8): can't convert nil into string My update to 10 seems to be OK except for this.. I cannot find its origin so do not know what to deinstall and reinstall It would also be great to get all bsdpan into the pkgdb with their origins.. is there any way to do that? Thanks in advance David Perhaps you should start a new thread. Chris Tried that last week to no avail So asmy question was vaguely on topic I had hoped someone might be able to contribute something useful!! If you can send a reply-all to the list, you certainly can send a new question, can't you? Hijacking threads *is* considered rude/ignorant/dumb by some. That said, Pod::Perldoc seems to be part of perl-5.8.[8-9] on my systems, so unless you're doing some nonstandard things with this package, I suggest you just pkg_delete the bsdpan package and get on with it. Hi Ruben Sorry to get cross with you but it has been clear from your responses that you have not actually troubled to read the detail of what I posted. The origibnal posting refrred to the issue as being one that came as a result of doing something similar to the OP for the thread. There was a second part (relating to getting the info on bsdpan into the DB. a. If you had read carefully you would have found that I have already tried: posting another thread b. I had already tried pkg_delete without success. c. I had tried package_deinstall again without success. d. I am totally puzzled why bsdpan-Pod_Perldoc should be showing a dependency on perl-5.8-9 when I have upgraded to 10. I will be very happy to get on with it when I know how to achieve that nirvana. In the meantime those who get try to get picky without reading a thread carefully do tend to offeset the work of so many people who are friendly and helpful Thanks in advance for positive contributions david ___ 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: Can I resume the perl upgrade?
On Saturday 11 April 2009 17:20:56 Chris Rees wrote:
2009/4/11 David Southwell da...@vizion2000.net:
On Friday 10 April 2009 11:43:33 kime...@gmail.com wrote:
Paul Schmehl wrote:
--On Friday, April 10, 2009 11:17:00 -0500 Paul Schmehl
pschmehl_li...@tx.rr.com wrote:
According to /usr/ports/UPDATING, if you want to upgrade to perl5.10,
you do
the following:
Portupgrade users:
0) Fix pkgdb.db (for safety):
pkgdb -Ff
1) Reinstall perl with new 5.10:
portupgrade -o lang/perl5.10 -f perl-5.8.\*
2) Reinstall everything that depends on Perl:
portupgrade -fr perl
My machine got rebooted right in the middle of step 3. Is there a
way to
resume where I left off? Or do I just start over?
Let me rephrase. I don't see a way in portupgrade to start over where
I left off. However, pkg_info -R lang/perl* shows that all my ports
depend on 5.10 and no ports are still depending upon 5.8. Is it safe
to assume that the reboot happened after portupgrade had finished?
Nope. With this info you can assume that step 2/3 worked. Not the step
3/3. I dont know how to restart at the stage it was before reboot as I
dont use portupgrade.
Personnaly, as portmaster failed with some ports and abort the whole
update process, I wrote a simple sh script which loop over the packages
which need perl (got via the via pkg_info -R, need reordering
thought...), exec portmaster ${PKG}, and keep a list of which reinstall
succeed and which failed.
Regards
I hope it is not too far off topic but:
Can anyone tell me how to fix this one:
Stale dependency: bsdpan-Pod-Perldoc-3.15 - perl-5.8.9_2 (lang/perl5.8):
can't convert nil into string
My update to 10 seems to be OK except for this..
I cannot find its origin so do not know what to deinstall and reinstall
It would also be great to get all bsdpan into the pkgdb with their
origins.. is there any way to do that?
Thanks in advance
David
Perhaps you should start a new thread.
Chris
Tried that last week to no avail
So asmy question was vaguely on topic I had hoped someone might be able to
contribute something useful!!
No such luck!!
Thank you for your contribution
most helpful
David
___
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 bsdpan into pkgdb
--On April 12, 2009 2:05:50 PM -0500 David Southwell da...@vizion2000.net wrote: I hope it is not too far off topic but: It is, so note the change of subject Can anyone tell me how to fix this one: Stale dependency: bsdpan-Pod-Perldoc-3.15 - perl-5.8.9_2 (lang/perl5.8): can't convert nil into string Rather than installing directly from bsdpan, install all your perl modules from ports. It takes a little getting used to, but many of the bsdpan modules are in ports with the convention p5-Name-Name. Paul Schmehl, If it isn't already obvious, my opinions are my own and not those of my employer. ** WARNING: Check the headers before replying ___ 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: Can I resume the perl upgrade?
2009/4/11 David Southwell da...@vizion2000.net:
On Friday 10 April 2009 11:43:33 kime...@gmail.com wrote:
Paul Schmehl wrote:
--On Friday, April 10, 2009 11:17:00 -0500 Paul Schmehl
pschmehl_li...@tx.rr.com wrote:
According to /usr/ports/UPDATING, if you want to upgrade to perl5.10,
you do
the following:
Portupgrade users:
0) Fix pkgdb.db (for safety):
pkgdb -Ff
1) Reinstall perl with new 5.10:
portupgrade -o lang/perl5.10 -f perl-5.8.\*
2) Reinstall everything that depends on Perl:
portupgrade -fr perl
My machine got rebooted right in the middle of step 3. Is there a
way to
resume where I left off? Or do I just start over?
Let me rephrase. I don't see a way in portupgrade to start over where
I left off. However, pkg_info -R lang/perl* shows that all my ports
depend on 5.10 and no ports are still depending upon 5.8. Is it safe
to assume that the reboot happened after portupgrade had finished?
Nope. With this info you can assume that step 2/3 worked. Not the step 3/3.
I dont know how to restart at the stage it was before reboot as I dont
use portupgrade.
Personnaly, as portmaster failed with some ports and abort the whole
update process, I wrote a simple sh script which loop over the packages
which need perl (got via the via pkg_info -R, need reordering
thought...), exec portmaster ${PKG}, and keep a list of which reinstall
succeed and which failed.
Regards
I hope it is not too far off topic but:
Can anyone tell me how to fix this one:
Stale dependency: bsdpan-Pod-Perldoc-3.15 - perl-5.8.9_2 (lang/perl5.8):
can't convert nil into string
My update to 10 seems to be OK except for this..
I cannot find its origin so do not know what to deinstall and reinstall
It would also be great to get all bsdpan into the pkgdb with their origins..
is there any way to do that?
Thanks in advance
David
Perhaps you should start a new thread.
Chris
--
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
___
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
On 6/28/05, John Larson [EMAIL PROTECTED] wrote: I recently upgraded to perl 5.8.5.. I then issued the use.perl port command. I then issued the portupgrade 'p5-*' command as root. DBI cannot be found in the @INC array. what am I missing. John Larson South Lake Tahoe CA Can you tell us a bit more about the system, is it FreeBSD 4.x? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
perl upgrade
I recently upgraded to perl 5.8.5.. I then issued the use.perl port command. I then issued the portupgrade 'p5-*' command as root. DBI cannot be found in the @INC array. what am I missing. John Larson South Lake Tahoe CA Yahoo! Sports Rekindle the Rivalries. Sign up for Fantasy Football http://football.fantasysports.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
perl upgrade to 5.8.6 and DB_File won't build
It all started with a simple perl upgrade from 5.8.0 to 5.8.6. Unfortunately, DB_File fails to build properly. I am running FreeBSD 4.10 Stable #1 Here's the resu.llts of the make test make test PERL_DL_NONLAZY=1 /usr/local/bin/suidperl -MExtUtils::Command::MM -e test_harness(0, 'blib/lib', 'blib/arch') t/*.t t/db-btreeCan't load '/usr/home/joe/DB_File-1.811/blib/arch/auto/DB_File/DB_File.so' for module DB_File: /usr/home/joe/DB_File-1.811/blib/arch/auto/DB_File/DB_File.so: Undefined symbol db_create_4002 at /usr/local/lib/perl5/5.8.6/mach/DynaLoader.pm line 230. at t/db-btree.t line 34 Compilation failed in require at t/db-btree.t line 34. BEGIN failed--compilation aborted at t/db-btree.t line 34. t/db-btreedubious Test returned status 255 (wstat 65280, 0xff00) t/db-hash.Can't load '/usr/home/joe/DB_File-1.811/blib/arch/auto/DB_File/DB_File.so' for module DB_File: /usr/home/joe/DB_File-1.811/blib/arch/auto/DB_File/DB_File.so: Undefined symbol db_create_4002 at /usr/local/lib/perl5/5.8.6/mach/DynaLoader.pm line 230. at t/db-hash.t line 23 Compilation failed in require at t/db-hash.t line 23. BEGIN failed--compilation aborted at t/db-hash.t line 23. t/db-hash.dubious Test returned status 255 (wstat 65280, 0xff00) t/db-recnoCan't load '/usr/home/joe/DB_File-1.811/blib/arch/auto/DB_File/DB_File.so' for module DB_File: /usr/home/joe/DB_File-1.811/blib/arch/auto/DB_File/DB_File.so: Undefined symbol db_create_4002 at /usr/local/lib/perl5/5.8.6/mach/DynaLoader.pm line 230. at t/db-recno.t line 23 Compilation failed in require at t/db-recno.t line 23. BEGIN failed--compilation aborted at t/db-recno.t line 23. t/db-recnodubious Test returned status 255 (wstat 65280, 0xff00) FAILED--3 test scripts could be run, alas--no output ever seen *** Error code 2 Stop in /usr/home/joe/DB_File-1.811. -- Thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
perl upgrade broke 5.3 system
Hello, I just updated ports after being away for two weeks. The update process itself went fine, my problem came when i ran the command to update perl-dependent ports as suggested in /usr/ports/UPDATING. I got a bunch of failed updates, php4-extensions, and any of my p5* ports, apache2, subversion, ices, etc. I've tried manually running portupgrade packagename but all i get is a prompt, it's as if portupgrade thinks everything is updated, but dependent perl ports are not working. The noticer was when MailScanner couldn't find SpamAssassin although the latest version of both ports are installed. On another question when i install a port if it installs dependencies and those are only needed by that port, when i uninstall the port i'd like to updte and remove those dependencies as well, is this doable? Some urgency! Thanks. Dave. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: perl upgrade broke 5.3 system
On Monday 07 February 2005 09:02 am, dave [EMAIL PROTECTED] wrote: Hello, I just updated ports after being away for two weeks. The update process itself went fine, my problem came when i ran the command to update perl-dependent ports as suggested in /usr/ports/UPDATING. I got a bunch of failed updates, php4-extensions, and any of my p5* ports, apache2, subversion, ices, etc. I've tried manually running portupgrade packagename but all i get is a prompt, it's as if portupgrade thinks everything is updated, but dependent perl ports are not working. The noticer was when MailScanner couldn't find SpamAssassin although the latest version of both ports are installed. Well, it's always tricky. What I did this time is: % pkg_info -R perl\* ~/perlports A list of dependencies is now in the text file perlports. In order to get a working environment, I did this first (I use xfce4 on this machine): # portupgrade -rRf xfce Then I force-upgraded all the rest of the xorg ports that weren't upgraded by that command, then all libraries, then individual programs, and finally the ports in meta ports, then the meta ports themselves. Most of this was done automatically; I copied perlports to a different file, edited out some lines, and added commands, put the list in the order stated previously, set the file as executable, then I ran it as a script. Most of the lines in the script look like this (yelp is an example): portupgrade -f yelp-2.6.5 ; It took a long time, as always, but I had zero problems. I also had xfce4, SpamAssassin, KMail and some other programs I use all the time up and running right away. I'm sure this could be done in a more automated fashion, but I've always run into dependency problems that way, if ports aren't upgraded in the right order, e.g., libraries first, so there's always clean up work to do. I avoided that this time, though it took a little longer to have each upgrade be a separate line in a script. On another question when i install a port if it installs dependencies and those are only needed by that port, when i uninstall the port i'd like to updte and remove those dependencies as well, is this doable? Some urgency! Yes, as long as those dependencies aren't needed elsewhere. You can run the pkg_info -r command to find out, then run pkg_info -R on the dependencies, or you can run: make pretty-print-run-depends-list make pretty-print-build-depends-list in the appropriate port folder (e.g., /usr/ports/www/firefox). There's also sysutils/pkg_cutleaves . - jt ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: perl upgrade broke 5.3 system
On Mon, Feb 07, 2005 at 12:02:08PM -0500, dave wrote: Hello, I just updated ports after being away for two weeks. The update process itself went fine, my problem came when i ran the command to update perl-dependent ports as suggested in /usr/ports/UPDATING. I got a bunch of failed updates, php4-extensions, and any of my p5* ports, apache2, subversion, ices, etc. I've tried manually running portupgrade packagename but all i get is a prompt, it's as if portupgrade thinks everything is updated, but dependent perl ports are not working. portupgrade -f The noticer was when MailScanner couldn't find SpamAssassin although the latest version of both ports are installed. It sounds like some of the ports are still installed in the perl 5.8.5 directory, so the newer ports that have been rebuilt against perl 5.8.6 cannot find them. That was what the command in UPDATING was supposed to fix though, so maybe there is a corner case that was not covered. If you can reproduce this, talk to the [EMAIL PROTECTED] mailing list. On another question when i install a port if it installs dependencies and those are only needed by that port, when i uninstall the port i'd like to updte and remove those dependencies as well, is this doable? Not automatically, because the system can't know if you're actually using any of those build-time dependencies yourself (e.g. you might be using gmake or gcc 3.4 for your own non-port projects), but the pkg_cutleaves port can help to do this. Kris pgpcz5zAQYGAu.pgp Description: PGP signature
Re: Dumb perl upgrade question
In the immortal words of Brent Wiese [EMAIL PROTECTED]... Am I missing some environment variable somewhere or what? Did you run use.perl port after you upgraded the port? -- Tim Aslat [EMAIL PROTECTED] Spyderweb Consulting http://www.spyderweb.com.au Phone: +61 0401088479 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Dumb perl upgrade question
-Original Message- In the immortal words of Brent Wiese [EMAIL PROTECTED]... Am I missing some environment variable somewhere or what? Did you run use.perl port after you upgraded the port? D'oh! See, I knew it was dumb. For some reason, I didn't think that needed to be done after an upgrade since I'd done it after installing perl 5.8.2 from ports originally. But, its now looking at 5.8.4. Thanks! Brent ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Dumb perl upgrade question
This is the sort of thing I know I should know, but I don't right now... Too many other stresses... Upgraded perl from 5.8.2 to 5.8.4 (both were ports). I need to recompile a bunch of modules (for example, mod_perl). But, most of them error out because they can't find perl 5.8.2 libraries. Am I missing some environment variable somewhere or what? Thanks! Brent ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Update module ports after Perl upgrade?
Jim Flowers [EMAIL PROTECTED] writes: I just upgraded to perl-5.8.1 on my FreeBSD 4.9R system (5.8.0 threw an error on shared.bs) but after I had installed mysql-server which builds p5-DBI-137- 1.37 and p5-DBD-mysql-2.1026_1 as dependencies. In the past I have uninstalled perl modules and reinstalled them to get them in the right place to use with the upgraded perl version but it seems a bit hit-or-miss on establishing the new dependencies. What is the right, or at least preferred, way to do this? Update again; there was a bug in the 5.8.1 release of perl. In general, I think that you won't need to update your modules, but things aren't guaranteed to work if you don't. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Update module ports after Perl upgrade?
I just upgraded to perl-5.8.1 on my FreeBSD 4.9R system (5.8.0 threw an error on shared.bs) but after I had installed mysql-server which builds p5-DBI-137- 1.37 and p5-DBD-mysql-2.1026_1 as dependencies. In the past I have uninstalled perl modules and reinstalled them to get them in the right place to use with the upgraded perl version but it seems a bit hit-or-miss on establishing the new dependencies. What is the right, or at least preferred, way to do this? Thanks. -- Jim Flowers[EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Perl Upgrade
Does anyone know a way to upgrade perl (from 5.00503) to 5.8.0 without loosing all currently install modules? -Grant Grant W. Peel Server Admin [EMAIL PROTECTED] http://thenetnow.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
