I've successfully upgraded (using the SuSE 9.2 Pro DVD) my SLES8 system to 9.2. It's nice to be cought up again, but I find that YaST Only Update does not work. It seems to be looking for SLES8 directories on the you servers, and that is obviously not what I want. How can I fix up the YOU configuration so that it works again? -- Steve Williams "The woods are lovely, dark and deep. steve at .......... But I have promises to keep, http://www........... and lines to code before I sleep, http://www.picturel.com And lines to code before I sleep."
"Stephen Williams" <1mc9i5i02@sneakemail.com> writes:
I've successfully upgraded (using the SuSE 9.2 Pro DVD) my SLES8 system to 9.2. It's nice to be cought up again, but I find that YaST Only Update does not work. It seems to be looking for SLES8 directories on the you servers, and that is obviously not what I want.
How can I fix up the YOU configuration so that it works again?
/var/adm/YaST/ProdDB/ contains a file with all info - handedit or copy it over... Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
Andreas Jaeger aj-at-suse.de |suse-amd64| wrote:
"Stephen Williams" <1mc9i5i02@sneakemail.com> writes:
I've successfully upgraded (using the SuSE 9.2 Pro DVD) my SLES8 system to 9.2. It's nice to be cought up again, but I find that YaST Only Update does not work. It seems to be looking for SLES8 directories on the you servers, and that is obviously not what I want.
How can I fix up the YOU configuration so that it works again?
/var/adm/YaST/ProdDB/ contains a file with all info - handedit or copy it over...
Andreas
OK, I see 3 products there, the old UnitedLinks, the old SLES8 and the new 9.2 product. The latter has this in it: =DescriptionDir: ./suse/setup/descr =DataDir: ./suse =Flags: update =RelnotesUrl: http://www.suse.com/relnotes/i386/SUSE-LINUX/9.2/release-notes.rpm =YouUrl: =YouType: =YouPath: i386/update/9.2 This is an AMD64 machine, but if I read this right, YOU is treating it as an i386. It appears from the +Arch: section above that you (SuSE) are treating x86_64 as a specialization of i386, kinda like i686 and i586? Saying "Yes" would give me warm fuzzies. Here's a Customer Suggestion: Add some sort of YaST applet to manage that product database. Seems like this issue will come up for each and every upgrade, -- Steve Williams "The woods are lovely, dark and deep. steve at .......... But I have promises to keep, http://www........... and lines to code before I sleep, http://www.picturel.com And lines to code before I sleep."
"Stephen Williams" <1mc9i5i02@sneakemail.com> writes:
Andreas Jaeger aj-at-suse.de |suse-amd64| wrote:
"Stephen Williams" <1mc9i5i02@sneakemail.com> writes:
I've successfully upgraded (using the SuSE 9.2 Pro DVD) my SLES8 system to 9.2. It's nice to be cought up again, but I find that YaST Only Update does not work. It seems to be looking for SLES8 directories on the you servers, and that is obviously not what I want.
How can I fix up the YOU configuration so that it works again? /var/adm/YaST/ProdDB/ contains a file with all info - handedit or copy it over... Andreas
OK, I see 3 products there, the old UnitedLinks, the old SLES8 and the new 9.2 product. The latter has this in it:
Remove the two old ones... Andreas
=DescriptionDir: ./suse/setup/descr =DataDir: ./suse =Flags: update =RelnotesUrl: http://www.suse.com/relnotes/i386/SUSE-LINUX/9.2/release-notes.rpm =YouUrl: =YouType: =YouPath: i386/update/9.2
This is an AMD64 machine, but if I read this right, YOU is treating it as an i386. It appears from the +Arch: section above that you (SuSE) are treating x86_64 as a specialization of i386, kinda like i686 and i586? Saying "Yes" would give me warm fuzzies.
Yes, this is correct.
Here's a Customer Suggestion: Add some sort of YaST applet to manage that product database. Seems like this issue will come up for each and every upgrade,
It's a bug that it comes up ;-) Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
Here's a Customer Suggestion: Add some sort of YaST applet to manage that product database. Seems like this issue will come up for each and every upgrade,
Only for unsupported updates. Normally only updates in the same product are supported/tested, no cross updates: e.g. SL8.2->SL9.0->SL9.1->SL9.2 and SLES8->SLES9 but no SLES<anything>->SL or the other way round. You were lucky that it worked, but such smaller issues cannot be ruled out. -Andi
Andi Kleen ak-at-suse.de |suse-amd64| wrote:
Here's a Customer Suggestion: Add some sort of YaST applet to manage that product database. Seems like this issue will come up for each and every upgrade,
Only for unsupported updates. Normally only updates in the same product are supported/tested, no cross updates:
e.g. SL8.2->SL9.0->SL9.1->SL9.2 and SLES8->SLES9 but no SLES<anything>->SL or the other way round.
You were lucky that it worked, but such smaller issues cannot be ruled out.
Well gee, it worked quite well, actually. That was the only glitch I can see so far (although today is my first workday with this new installation). Whether it's officially supported or not doesn't mean it's not a reasonable thing to do. Hell, I'm running Xilinx software on a SuSE system, and *that* sure ain't a supported thing, by Xilinx or SuSE; but that doesn't mean it isn't something people are going to want to do. (I'm running Xilinx software on a 64bit system, and *that's not supported either:-) So you've got at least one customer who decided it was best to go from SLES8 to SuSE9.2Pro, who had to do something because SLES8 was getting moldy, and who's glad he did it. And for future reference, in case anyone wants to do anything about it, the glitch was that the YOU update didn't account for the old SLES8 and UnitedLinux config files left behind. -- Steve Williams "The woods are lovely, dark and deep. steve at .......... But I have promises to keep, http://www........... and lines to code before I sleep, http://www.picturel.com And lines to code before I sleep."
participants (3)
-
Andi Kleen -
Andreas Jaeger -
Stephen Williams