Re: Major Error Upgrading to GNOME 2.12
Micah wrote: Bob Perry wrote: This past weekend, I CVSup'd the ports tree and prepared to run portupgrade. I noticed a large number of GNOME ports in my output from pkg_version and, found that I would need to run the GNOME Project 's upgrade script to upgrade to 2.12. I use a dial-up modem had been timed out on several occasions.during the process This happened about three times during the night and I had to restart the upgrade each time. Note that I failed to use the restart flag recommended during the first restart. I finally ended up with a succesful upgrade... message even though I now have only 188 ports after beginning with 297. Amongst the missing is gnome 2.12 itself. I'm hoping there is some way to get things back to normal and rerun the upgrade without re-installing the missing ports. BTW, I did back up /var/db/pkg. Any advice would be appreciated. I run 5.4 -RELEASE #0. I'm running this message from a second machine but should be able to supply the logs if needed. Thanks, Bob Perry gnome_upgrade_lst. in your tmp folder should contain a list of all the software that the script was going to update. Compare that list with the output from pkg_version/portversion to see what needs reinstalling. Reinstall it via whatever method you like (portinstall, cd /user/port/xxx/xxx make install). I am in a similar situation but I had the output from portversion from before the upgrade to rely on (and wrote a script that made a list of the differences). HTH, Micah I was able to compare the list of files the script was going to update to output from pkg_version to get an idea of what was missing. I started with gnome2 (cd /user/port/x11/gnome2 make install) and now have about a dozen ports left to install. (Think I'll try portmanager at a later date when I feel more comfortable with it.) I certainly want to thank you all for your help. Can't wait 'til next upgrade. Thanks, Bob Perry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Major Error Upgrading to GNOME 2.12
Bob Perry [EMAIL PROTECTED] writes: This past weekend, I CVSup'd the ports tree and prepared to run portupgrade. I noticed a large number of GNOME ports in my output from pkg_version and, found that I would need to run the GNOME Project 's upgrade script to upgrade to 2.12. I use a dial-up modem had been timed out on several occasions.during the process This happened about three times during the night and I had to restart the upgrade each time. Note that I failed to use the restart flag recommended during the first restart. I finally ended up with a succesful upgrade... message even though I now have only 188 ports after beginning with 297. Amongst the missing is gnome 2.12 itself. I'm hoping there is some way to get things back to normal and rerun the upgrade without re-installing the missing ports. BTW, I did back up /var/db/pkg. Any advice would be appreciated. I run 5.4 -RELEASE #0. I'm running this message from a second machine but should be able to supply the logs if needed. In the worst case, you should be able to delete all the Gnome-related ports and re-add them. [I did that on purpose, because my only Gnome machine is *so* much slower than my build server.] -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Major Error Upgrading to GNOME 2.12
My own horror story: ruby started throwing errors: INFO: Running /usr/local/sbin/pkg_deinstall -fO graphics/kimdaba [Updating the pkgdb format:bdb1_btree in /var/db/pkg ... - 690 packages found (-1 +0) (...)/usr/local/lib/rub y/site_ruby/1.8/pkgdb.rb:466: [BUG] Segmentation fault ruby 1.8.2 (2004-12-25) [i386-freebsd6] halfway through the package removal process, but the gnome_upgrade212.sh script kept cheerfully chewing its way through my package list. I ended up looking in the list of packages that it was going to fix, manually pkg_deleteing them, and then manually reinstalling them. Out of curiosity, exactly what's wrong with portupgrade that these upgrade scripts (which never seem to work as expected on my system) claim to fix? -- Kirk Strauser pgp6pxB3yg4Hs.pgp Description: PGP signature
Re: Major Error Upgrading to GNOME 2.12
On Tuesday 08 November 2005 06:16, Kirk Strauser wrote: My own horror story: ruby started throwing errors: INFO: Running /usr/local/sbin/pkg_deinstall -fO graphics/kimdaba [Updating the pkgdb format:bdb1_btree in /var/db/pkg ... - 690 packages found (-1 +0) (...)/usr/local/lib/rub y/site_ruby/1.8/pkgdb.rb:466: [BUG] Segmentation fault ruby 1.8.2 (2004-12-25) [i386-freebsd6] halfway through the package removal process, but the gnome_upgrade212.sh script kept cheerfully chewing its way through my package list. I ended up looking in the list of packages that it was going to fix, manually pkg_deleteing them, and then manually reinstalling them. Out of curiosity, exactly what's wrong with portupgrade that these upgrade scripts (which never seem to work as expected on my system) claim to fix? Not sure why the scripts arte needed, I do know portmanager 0.3.3 handles the upgrade no problem, no special scripts required. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Major Error Upgrading to GNOME 2.12
Bob Perry wrote: This past weekend, I CVSup'd the ports tree and prepared to run portupgrade. I noticed a large number of GNOME ports in my output from pkg_version and, found that I would need to run the GNOME Project 's upgrade script to upgrade to 2.12. I use a dial-up modem had been timed out on several occasions.during the process This happened about three times during the night and I had to restart the upgrade each time. Note that I failed to use the restart flag recommended during the first restart. I finally ended up with a succesful upgrade... message even though I now have only 188 ports after beginning with 297. Amongst the missing is gnome 2.12 itself. I'm hoping there is some way to get things back to normal and rerun the upgrade without re-installing the missing ports. BTW, I did back up /var/db/pkg. Any advice would be appreciated. I run 5.4 -RELEASE #0. I'm running this message from a second machine but should be able to supply the logs if needed. Thanks, Bob Perry gnome_upgrade_lst. in your tmp folder should contain a list of all the software that the script was going to update. Compare that list with the output from pkg_version/portversion to see what needs reinstalling. Reinstall it via whatever method you like (portinstall, cd /user/port/xxx/xxx make install). I am in a similar situation but I had the output from portversion from before the upgrade to rely on (and wrote a script that made a list of the differences). HTH, Micah ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Major Error Upgrading to GNOME 2.12
On Monday 07 November 2005 22:32, Bob Perry wrote: This past weekend, I CVSup'd the ports tree and prepared to run portupgrade. I noticed a large number of GNOME ports in my output from pkg_version and, found that I would need to run the GNOME Project 's upgrade script to upgrade to 2.12. I use a dial-up modem had been timed out on several occasions.during the process This happened about three times during the night and I had to restart the upgrade each time. Note that I failed to use the restart flag recommended during the first restart. I finally ended up with a succesful upgrade... message even though I now have only 188 ports after beginning with 297. Amongst the missing is gnome 2.12 itself. I'm hoping there is some way to get things back to normal and rerun the upgrade without re-installing the missing ports. BTW, I did back up /var/db/pkg. Any advice would be appreciated. I run 5.4 -RELEASE #0. I'm running this message from a second machine but should be able to supply the logs if needed. Thanks, Bob Perry get sysutils/portmanager make sure it is version 0.3.3, you need a very up to date tree, then run portmanager x11/gnome2 -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
