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
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
Bob Hall wrote: I don't know squat about perl. I recently ran portupgrade, which upgraded perl. Goose stopped working, because the location for Curses.pm was no longer in @INC. I tried to run perl-after-upgrade, but I couldn't get it to run. I've got a book that said to use # perl perl-after-upgrade or # ./perl-after-upgrade I also tried just # perl-after-upgrade No joy. Just for the heck of it, I tried * sh perl-after-upgrade and dang if it didn't run. It didn't look to me like an sh script, but what do I know? It wasn't supposed to change anything without the -f option, but goose ran afterward, so it obviously changed things. I looked for Curses.pm, and it moved to a directory listed in @INC. Anybody have any advice? Comments? How was I supposed to get perl-after-upgrade to run? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] A longish message appears at the end of the perl upgrade build, that explains how to run perl-after-upgrade. If you overlooked that, the same instructions are at #perldoc perl-after-upgrade If the script is in a directory not in your root's path, find the full path to the script with #locate perl-after-upgrade (but make sure your locate db is up-to-date, first). - Jacques ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: perl-after-upgrade
On Thu, Jul 07, 2005 at 06:55:58PM +0200, legalois wrote: Bob Hall wrote: I don't know squat about perl. I recently ran portupgrade, which upgraded perl. Goose stopped working, because the location for Curses.pm was no longer in @INC. I tried to run perl-after-upgrade, but I couldn't get it to run. I've got a book that said to use # perl perl-after-upgrade or # ./perl-after-upgrade I also tried just # perl-after-upgrade No joy. Just for the heck of it, I tried * sh perl-after-upgrade and dang if it didn't run. It didn't look to me like an sh script, but what do I know? It wasn't supposed to change anything without the -f option, but goose ran afterward, so it obviously changed things. I looked for Curses.pm, and it moved to a directory listed in @INC. Anybody have any advice? Comments? How was I supposed to get perl-after-upgrade to run? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] A longish message appears at the end of the perl upgrade build, that explains how to run perl-after-upgrade. As I stated above, I used portupgrade. That means that any messages at the end of the perl upgrade scrolled off the screen and out of the screen buffer when portupgrade carried out the next install. One of the problems with portupgrade is that you rarely see the post-upgrade messages when you do batch upgrades. If you overlooked that, the same instructions are at #perldoc perl-after-upgrade That's identical to the man page, which didn't supply any information that helped. So if the man page, perldoc page, and post-install message were the same, none of them contained the information I needed. If the script is in a directory not in your root's path, find the full path to the script with #locate perl-after-upgrade (but make sure your locate db is up-to-date, first). As I stated above, I tried ./perl-after-upgrade and I looked at the script, neither of which would have been possible if I didn't know where the script was. As I mentioned in my followup post, I solved the problem with rehash. A mention of this in /usr/ports/UPDATING would help those of use who rarely use tcsh unless we need to run something as root. Also in the man page. Any situation that requires perl-after-upgrade probably also requires rehash. I found the solution at http://marc.theaimsgroup.com/?l=freebsd-portsm=111980508717308w=2 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: perl-after-upgrade
--On Thursday, July 07, 2005 14:39:44 -0400 Bob Hall [EMAIL PROTECTED] wrote: As I stated above, I used portupgrade. That means that any messages at the end of the perl upgrade scrolled off the screen and out of the screen buffer when portupgrade carried out the next install. One of the problems with portupgrade is that you rarely see the post-upgrade messages when you do batch upgrades. That's an easily solved problem. After you finish portupgrade, view the pkg-message file in any port you have a question about. E.g. % view /usr/ports/lang/perl5.8/pkg-message Paul Schmehl ([EMAIL PROTECTED]) Adjunct Information Security Officer University of Texas at Dallas AVIEN Founding Member http://www.utdallas.edu/ir/security/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: perl-after-upgrade
On Wednesday 06 July 2005 20:10, Bob Hall wrote: I don't know squat about perl. I recently ran portupgrade, which upgraded perl. Goose stopped working, because the location for Curses.pm was no longer in @INC. I tried to run perl-after-upgrade, but I couldn't get it to run. I've got a book that said to use # perl perl-after-upgrade or # ./perl-after-upgrade I also tried just # perl-after-upgrade No joy. Just for the heck of it, I tried * sh perl-after-upgrade and dang if it didn't run. It didn't look to me like an sh script, but what do I know? It wasn't supposed to change anything without the -f option, but goose ran afterward, so it obviously changed things. I looked for Curses.pm, and it moved to a directory listed in @INC. Anybody have any advice? Comments? How was I supposed to get perl-after-upgrade to run? I used to be a bit sceptical about portmanager, but for the sake of a few hours of unattended extra building, you can simply ignore this kind of thing. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: perl-after-upgrade
On Thu, Jul 07, 2005 at 01:53:48PM -0500, Paul Schmehl wrote: --On Thursday, July 07, 2005 14:39:44 -0400 Bob Hall [EMAIL PROTECTED] wrote: As I stated above, I used portupgrade. That means that any messages at the end of the perl upgrade scrolled off the screen and out of the screen buffer when portupgrade carried out the next install. One of the problems with portupgrade is that you rarely see the post-upgrade messages when you do batch upgrades. That's an easily solved problem. After you finish portupgrade, view the pkg-message file in any port you have a question about. E.g. % view /usr/ports/lang/perl5.8/pkg-message Aha. The instructions in the post-install message are not repeated in the perldoc page. And the message does suggest using rehash. Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
perl-after-upgrade
I don't know squat about perl. I recently ran portupgrade, which upgraded perl. Goose stopped working, because the location for Curses.pm was no longer in @INC. I tried to run perl-after-upgrade, but I couldn't get it to run. I've got a book that said to use # perl perl-after-upgrade or # ./perl-after-upgrade I also tried just # perl-after-upgrade No joy. Just for the heck of it, I tried * sh perl-after-upgrade and dang if it didn't run. It didn't look to me like an sh script, but what do I know? It wasn't supposed to change anything without the -f option, but goose ran afterward, so it obviously changed things. I looked for Curses.pm, and it moved to a directory listed in @INC. Anybody have any advice? Comments? How was I supposed to get perl-after-upgrade to run? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: perl-after-upgrade
On Wed, Jul 06, 2005 at 03:10:04PM -0400, Bob Hall wrote: I don't know squat about perl. I recently ran portupgrade, which upgraded perl. Goose stopped working, because the location for Curses.pm was no longer in @INC. I tried to run perl-after-upgrade, but I couldn't get it to run. I found a thread on this in freebsd-ports. I tried rehash and all seems to be well. The three apps modified when running perl-after-upgrade as an sh script seem to function OK. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Can't get perl-after-upgrade to run
On 26 Jun Dominique Goncalves wrote: And, if I type sh perl-after-upgrade -f I get the EXACT same output as above, leading me to believe it is ignoring the -f option. Use /usr/local/bin/perl-after-upgrade To OP: are you sure you did a rehash ? The file not found seems to tell you, you did not ;-) -- dick -- http://nagual.st/ -- PGP/GnuPG key: F86289CE ++ Running FreeBSD 4.11-stable ++ FreeBSD 5.4 + Nai tiruvantel ar vayuvantel i Valar tielyanna nu vilja ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Should I Keep Default Perl After Upgrade to 5.8 on FBSD 4.9?
I upgraded my 4.9-RELEASE system to use Perl 5.8.2 from ports. Is there any reason to keep the default 5.005.03 version? If not, are there any steps required beyond deleting /usr/local/lib/perl5/5.00503? Thanks, Drew ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
