|
Bugzilla – Full Text Bug Listing |
| Summary: | some yast modules crashed after last yast update. | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Dmitry Semkin <ds> |
| Component: | YaST2 | Assignee: | E-mail List <bnc-team-screening> |
| Status: | RESOLVED INVALID | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | i686 | ||
| OS: | SuSE Linux 10.0 | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Dmitry Semkin
2005-11-30 09:38:44 UTC
i'm a little bit confused. Last update for 10.0 is 2.12.21 for the yast2-packagemanager. Are you sure this is 10.0? Which installation source do you have, which directory are you using for online-update? hmm. dunno what real version is :) I've installed it as opensuse-rc3(or 2?) and regular update after. sorry, I've came to linux from freebsd and I still didn't quiet understand suse versioning. with freebsd I just regular cvsup source tree and rebuild the system to keep it up to date. and system version change with it. something like 5.2-stable, 5.2-stable, 5.3-rc1, 5.3-rc2, 5.3-stable... where is nothing special to change os version, just regular update. so I thought the same with suse, and the difference is only in building system/packages from source (freebsd) or binary patches (suse). please tell me if I'm mistaking. and how I can check the real version? now I'm using the next sources /home/lslarry> installation_sources -s Installation Sources: [x]* SUSE LINUX Version 10.0 (dir:///suse/) [x]* Packman (SuSE LINUX 10.0) (http://packman.iu-bremen.de//suse/10.0/) [x]* SUSE LINUX Version 10.0.42 (http://mirrors.kernel.org/opensuse/distribution/SL-OSS-edge/inst-source/) [x]* SUSE LINUX Version 10.0 (http://mirrors.kernel.org/opensuse/distribution/SL-OSS-stable/inst-source-java/) [x]* SUSE LINUX Version 10.0 (http://mirrors.kernel.org/suse/i386/current/SUSE-Linux10.0-GM-Extra/) [x]* SUSE LINUX Version 10.0 (ftp://mirror.switch.ch/mirror/opensuse/distribution/SL-OSS-stable/inst-source/) [ ]* SUSE LINUX Version 10.0 (cd:///;devices=/dev/hdc) the first is a local copy of 5 suse cd's on my hd /home/lslarry> head -4 /suse/README ------------------------ README on SuSE Linux 10.0 2005/09/04 ok, we handle it different. patches, the packages you recieve via the online update usually have the same version (if possible). When you add another installation source with a newer version, you have to select system update. But afaik this is not supported. Usually you download a ISO file and select update instead of installation. I guess this is the problem here, it's a mix of 2 Versions. You installed some packages from edge and when you do an online update it will search for 10.0 packages. You can try system update, but as i said usually you boot from CD and select update. I have to agree with Martin: Updates are always critical in a certain manner. Buf before using new packages, an update has to be done, of course. The crash could resolve from a binary incompatability against a linked libray, for example, which would then be natural. Dimitry: Have you actually done an update here (by booting and select update)? Or did you just add new installation sources? Updating a running system is not really supported, sorry. It will probably work if you change all dependent packages, too. But then you could create problems with other packages... i will close the bug now, for me it's not a bug. If you think it is one, please reopen, thanks. |