Re: [MiNT] SSH RPM?

[Guido.Flohr@t-online.de (Guido Flohr)]

Hi,

On Wed, Dec 13, 2000 at 03:44:48PM -0500, Noah silva wrote:
> Hello,
> 
> I downloaded the sparemint ssh RPMs, but had a minor problem,
> Can anyone explain why this happens?:
> 
> monolith:~#rpm -ivh openssh-2.3.0p1-1.m68kmint.rpm
> error: openssh-2.3.0p1-1.m68kmint.rpm cannot be installed
> 
> Rather non-descriptive error (_why_ can' tit be installed).

Better than "A fatal exception 0E has occured at ...". ;-)

> I have used .deb format a lot, but I am not so familiar with the RPM tool,
> so I thought I would ask here before I banged my head against the wall too
> much.  

Try to run "rpm -ivvh openssh..." (double 'v'!) to get some more
information about what's going on.  It's maybe just a missing directory.

You can try

	rpm -qpvl openssh-2.3.0p1-1.m68kmint.rpm

and check whether all directories where openssh wants to install files
exist.  You should pay a lot of care to double check all symlinks in the
archive.  A lot of errors are caused by (dangling) symlinks of the form 
"-> ../../lib" and the like.  If the dots in symlinks must be resolved
across the file system root you almost inevitably run into problems
because the top-level directories in MiNT are soft links instead of mount
points.

Another thing worth trying is

        rpm -qp --scripts openssh-2.3.0p1-1.m68kmint.rpm

which will dump the various installation and de-installation scripts (if
any) to stdout.

Have you successfully installed any other RPMs already? If not, you may
have a general problem with rpm (database not initialized, missing files
...)

Yes, RPM is not very talkative when it comes to errors.  But many problems
(like the soft link problem) are actually caused by MiNT problems or
oddities.  Furthermore there should be some base package called
"installdirs" or so that creates a directory skeleton.  Unfortunately this
is not so easy with MiNT (no real filesystem root but only that drive
u: with various soft links).

Ciao

Guido