i did an upgrade on my laptop from Red Hat 9 to test 2. i personally don't use Gnome and normally don't have it installed a friend wanted to see gnome in action so i went to redhat-config-packages it told me i had no kde and no gnome packages installed. i have all kde and some gnome stuff as i like to use applications such as gnomemeeting. i selected all gnome packages to be installed and got dependencie errors over pspell and aspell deselected gedit and promptly got asked for Red Hat 9 CD 1it would not continue with the install so i did the install manually and ran redhat-config-packages again to see what it would show and again no kde or gnome packages are installed. in the games it shows i have kdegames installed so its getting some but not the main desktop ones. anyone seen anything simmiliar
Dennis
Hi,
Fedora Test 1 installed fine. However, when I install the Test 2 to the same machine, it displays the following message during system boot up. I media-checked 3 disc and they are passed.
Running anaconda, the Fedora Core system installer - please wait ... 'import site' failed: use -v for traceback Traceback (most recent call last): File "/usr/lib/anaconda/isys.py", line 22, in ? from rhpl.log import log ImportError: No module named rhpl.log install exited abnormally sending termination signals...done sending kill signals...done disabling swap... umounting filesystems... /mnt/runtime done disabling /dev/loop0 /proc/bus/usb done /proc done /dev/pts done /tmp/ramfs done /mnt/source done you may safety reboot your system
Best Regards, Andy www.wookieweb.com
On September 27, 2003 01:05 am, Andy Woo Andy Woo wooandy@mac.com wrote:
Hi,
Fedora Test 1 installed fine. However, when I install the Test 2 to the same machine, it displays the following message during system boot up. I media-checked 3 disc and they are passed.
Running anaconda, the Fedora Core system installer - please wait ... 'import site' failed: use -v for traceback Traceback (most recent call last): File "/usr/lib/anaconda/isys.py", line 22, in ? from rhpl.log import log ImportError: No module named rhpl.log install exited abnormally sending termination signals...done sending kill signals...done disabling swap... umounting filesystems... /mnt/runtime done disabling /dev/loop0 /proc/bus/usb done /proc done /dev/pts done /tmp/ramfs done /mnt/source done you may safety reboot your system
I got the same output during my second install attempt. Fedora Core *successfully* installed after the *third* attempt.
Elton
Hi Elton,
What do you mean by "Third" attempt? Did you burn another CD? Please elaborate. Thanks!
Best Regards, Andy www.wookieweb.com
On Sunday, September 28, 2003, at 12:45 AM, Elton Woo wrote:
On September 27, 2003 01:05 am, Andy Woo Andy Woo wooandy@mac.com wrote:
Hi,
Fedora Test 1 installed fine. However, when I install the Test 2 to the same machine, it displays the following message during system boot up. I media-checked 3 disc and they are passed.
Running anaconda, the Fedora Core system installer - please wait ... 'import site' failed: use -v for traceback Traceback (most recent call last): File "/usr/lib/anaconda/isys.py", line 22, in ? from rhpl.log import log ImportError: No module named rhpl.log install exited abnormally sending termination signals...done sending kill signals...done disabling swap... umounting filesystems... /mnt/runtime done disabling /dev/loop0 /proc/bus/usb done /proc done /dev/pts done /tmp/ramfs done /mnt/source done you may safety reboot your system
I got the same output during my second install attempt. Fedora Core *successfully* installed after the *third* attempt.
Elton
-- http://setiathome.ssl.berkeley.edu/stats/team/team_4504.html "You only live once: let's make life BETTER for each other." LINUX User #193975 [AMD ATHLON CPU] ICQ #149608718.
-- fedora-test-list mailing list fedora-test-list@redhat.com http://www.redhat.com/mailman/listinfo/fedora-test-list
Elton Woo schrieb:
I got the same output during my second install attempt. Fedora Core *successfully* installed after the *third* attempt.
Exactly the same, attempt 1 and 3 were ok.
Once upon a time at band camp Sat, 27 Sep 2003 3:01 pm, Craig Ringer wrote:
i did an upgrade on my laptop from Red Hat 9 to test 2.
You're better off clean-installing the betas.
Clean installs defeat the purpose of part of the beta testing process, i.e how are upgrades handled. if noonw tests an upgrade during beta period how will upgrade bugs be found?
Dennis
On Saturday 27 September 2003 03:45 am, Dennis Gilmore wrote:
Once upon a time at band camp Sat, 27 Sep 2003 3:01 pm, Craig Ringer wrote:
You're better off clean-installing the betas.
Clean installs defeat the purpose of part of the beta testing process, i.e how are upgrades handled. if noonw tests an upgrade during beta period how will upgrade bugs be found?
Dennis is very correct here. Upgrades have been a beta test target ever since I first started beta testing back in 6.2 days. While upgrading to a public beta (you do realize that there have been private betas, right (see www.beta.redhat.com)?) should be supported, upgrading from that beta to something else is not, so be prepared to do a clean install for the next step. Or clean reinstall the old system and upgrade. I have done this a number of times. One thing you have to watch out for in the clean reinstall case is if you move your home directory back in with a newer version of some things that store configuration in home. I had a pretty severe problem once (I think it was with a home that had gotten touched by the pre-7.3 beta series) going to RHL 8.0. Had to completely wipe .kde out and reconfigure KDE from scratch. But that is just what a beta tester has to be aware of -- betas can and do break your system. Let the tester beware! So far my home directory has survived in mostly unmangled form since Red Hat Linux 4.2.
On Sat, 2003-09-27 at 07:02, Lamar Owen wrote:
One thing you have to watch out for in the clean reinstall case is if you move your home directory back in with a newer version of some things that store configuration in home. I had a pretty severe problem once (I think it was with a home that had gotten touched by the pre-7.3 beta series) going to RHL 8.0. Had to completely wipe .kde out and reconfigure KDE from scratch. But that is just what a beta tester has to be aware of -- betas can and do break your system. Let the tester beware! So far my home directory has survived in mostly unmangled form since Red Hat Linux 4.2.
I got tired of that worry, so now I keep all my home directory "data" on a separate /data partition and place a link to it in my actual home directory. My "actual home directory" then contains only that link and any config data the system puts there. Before new install or upgrade, I copy all the "actual home directory" config stuff to a directory in /data called something like "oldconfig" so that I can restore any of it that I think is useful after a new install. Then on a new install I simply write over the old stuff or on an upgrade, delete all the config stuff from the home directory and start the install/upgrade.
This is also convenient for sharing the files in /data among various versions I'm running/testing.
This is not my original idea - I copied it from someone else on one of these lists. It has worked great through a number of installs.
Gerry Tool
On Sat, 27 Sep 2003, Dennis Gilmore wrote:
Once upon a time at band camp Sat, 27 Sep 2003 3:01 pm, Craig Ringer wrote:
i did an upgrade on my laptop from Red Hat 9 to test 2.
You're better off clean-installing the betas.
Clean installs defeat the purpose of part of the beta testing process, i.e how are upgrades handled. if noonw tests an upgrade during beta period how will upgrade bugs be found?
The only valid tests are upgrading from a release to a beta. If you installed beta1 you should either reinstall 9 and then upgrade to severn2... or do a clean install.
beta to beta has never been supported or will ever be because it is not a valid QA process.
Now the real test is to install up the trail... go from RHL 2.1, 3.0.3, 4.0,4.1,5.0,5.1,5.2,6.0,6.1,6.2,7.0,7.1,7.2,7.3,8.0,9 and then see what cruft is left over :).
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Sat, 27 Sep 2003 13:01:09 +0800, Craig Ringer wrote:
i did an upgrade on my laptop from Red Hat 9 to test 2.
You're better off clean-installing the betas.
And who tests the upgrade path then?
- -- Michael, who doesn't reply to top posts and complete quotes anymore.
Either upgrade your comps package with rpm comps*.rpm --oldpackage from the base on the cd or do what I did on two machines.
rpm -e comps up2date comps
Since Fedora is going to be version 1 and the numbers are lower than 1 for the second test install (0.94), rpm sees the program as older (9.0.x) and ignores the "older" version.
The program information is in the comps data and the program information will be incorrect for RH9's version of comps and test 2's version of comps.
It's like trying to find a city in Iowa, with an Ohio roadmap. Just upgrade comps, then try again.
Jim
Dennis Gilmore wrote:
i did an upgrade on my laptop from Red Hat 9 to test 2. i personally don't use Gnome and normally don't have it installed a friend wanted to see gnome in action so i went to redhat-config-packages it told me i had no kde and no gnome packages installed. i have all kde and some gnome stuff as i like to use applications such as gnomemeeting. i selected all gnome packages to be installed and got dependencie errors over pspell and aspell deselected gedit and promptly got asked for Red Hat 9 CD 1it would not continue with the install so i did the install manually and ran redhat-config-packages again to see what it would show and again no kde or gnome packages are installed. in the games it shows i have kdegames installed so its getting some but not the main desktop ones. anyone seen anything simmiliar
Dennis
-- fedora-test-list mailing list fedora-test-list@redhat.com http://www.redhat.com/mailman/listinfo/fedora-test-list