Re: need help fixing yast2 problem on 9.3

__/ [ Brian Hall ] on Tuesday 28 February 2006 02:41 \__

On 2006-02-27, Brian Hall wrote:
Reinstallation isn't in option in my case. I either have to figure out how
to fix yast, or do without and install RPMs manually at the command line.

I do have a little more information. When I do a search, it can find only
already-installed packages. If I search for a package provided by 9.3 but
not installed, nothing is found. For example, a search for "emacs" comes
up emtpy. Looks to me like the part of the yast2 config that goes to an
external online repository is broken.

The online update does appear to be set to a valid server, in that it does
download the patch information, instead of hanging or aborting.

OK, I figured out and fixed the problem.

Problem was the yast package database was either fried or missing. There
are files in /var/adm/YaST, but yast wasn't happy with them. I only figured
this out by doing "yast2 repair", which apparently you aren't supposed to
do from a running system, but oh well. Anyway, the repair process would
complain about the package DB being missing, and try to rebuild it, which
would appearently succeed, but running it again would fail with the same
problem.

So, having another server I hadn't configured yet, I simply scp'ed the
entire contents of /var/adm/YaST over to the server where I was having the
problem.

Somewhat unsatifying in that I have no idea what exactly the problem
was, but at least this fixed it...

On rare occasions, the same 'quick and dirty' solution can be used for KDE
applications that have gone 'tits-up'. It is somewhat re-assuring that all
settings are centralised so neatly as directories with files, so you can
merely graft (drag-and-drop) entire directories.

I should point out, however, that this is better (especially safer) done as
restoration from backup, rather than from one machine to another, i.e. one
installation base to another. Back up regularly just in case things go
morbid and you want to revert to an old state, even if only one small
component is involved:

nice scp -r ~/.[0-z]* ~/* you@mirror_machine:/home/you/mutual_backup/

This saved me from restoration efforts a few times, e.g. .ispell_english
being emptied or mail folders mistakenly erased.
.

Relevant Pages

  • Re: Good practices with NFS sharing of binaries
    ... > In order to avoid having to install the same software on different ... Sharing the binary packages via automounter is quite a common practice. ... *building* the binaries on production NFS server is IMHO ... then you can look into the package and figure out whether ...
    (comp.unix.solaris)
  • RE: [SLE] Not So Fast: Linux on the Desktop
    ... >> Yes, YaST can work, but more often than not I have found it ... >> available from the SuSE disc or not and then install that package. ... > compare Windows XP Home Edition with something like Lindows ...
    (SuSE)
  • Re: SSIS package wont run in production server
    ... I also would like to mention that on my production server, ... When you run the setup of SQL 2005, it is indeed possible to install only ... I have a package that I developed on my local machine and runs well. ...
    (microsoft.public.sqlserver.dts)
  • Re: The task ... cannot run on this edition of integration services. It requires a higher level edit
    ... My problem is that I can run/debug package in Visual Studio on my client PC, ... installed on the server. ... Without SSIS install, with just Tools install, user can design and debug ... Microsoft Online Community Support ...
    (microsoft.public.sqlserver.dts)
  • flexible restore/install system
    ... at home I run a server with actually to many stuff on it to be safe. ... Anyway, for normal quick restores, restoring a backup is quick and painless. ... to install a base system, install needed utils and copy the ... them when you install the "customizing" package or whatever you would ...
    (Debian-User)