Problems upgrading openssh on RHL 7.3

I'm trying to upgrade openssh from 3.1p1 to 3.7p1 on RHL 7.3

I downloaded the src rpm file and created an installable RPM.

When I try to do a rpm -Fvh or rpm Uvh on the rpm I get a dependency
complaint that openssh-1.3p1-blah-14 are needed.

If I do a rpm -qa |grep openssh, all of he dependency complaints list as
being installed.

I've read the white papers on the rpm implementation and I realize that it
is .... sub optimal. However, before installing this upgrade from source I
wanted to see if anyone had any suggestions. Rpm is really great when it
works and I certainly admit to being now expert. Perhaps someone's seen
this problem?

On Thu, 18 Mar 2004 09:14:37 -0800, Vigilance Monitoring wrote:

> I'm trying to upgrade openssh from 3.1p1 to 3.7p1 on RHL 7.3
>
> I downloaded the src rpm file and created an installable RPM.
>
> When I try to do a rpm -Fvh or rpm Uvh on the rpm I get a dependency
> complaint that openssh-1.3p1-blah-14 are needed.
>
> If I do a rpm -qa |grep openssh, all of he dependency complaints list as
> being installed.
>
> I've read the white papers on the rpm implementation and I realize that
> it is .... sub optimal. However, before installing this upgrade from
> source I wanted to see if anyone had any suggestions. Rpm is really
> great when it works and I certainly admit to being now expert. Perhaps
> someone's seen this problem?

Yes, the problem your understanding of the upgrade effort and what the
package manager (RPM) 'warning messages' are telling you in this case. The
package manager (RPM) 'warning messages' is an attempt in not allowing you
to break your system configuration by the single package upgrade when
multiple packages are required for the upgrade.

You have the list of the openssh RPM's that are required for the openssh
upgrade, the 'rpm -qa | grep openssh' output. Use this list as a reference
guide for the upgrade.

You have created the openssh-3.7p1 RPM package, what about the rest? If
during the time you created the binary RPM for the openssh 3.7p1 upgrade,
where any other non debug RPM's created also? If yes, then do they match
the known list of the openssh 3.1p1 RPM's? If yes, then install them all
at the same time, as root type something like 'rpm -Fvh *.rpm' from where
the packages are located. If not then you have some more work to do.
Basically you want the same updated openssh 3.7p1 RPM packages as the
currently installed openssh 3.1p1 RPM's as list from the output of the
'rpm -qa | grep openssh' command.


--
Posted under the XFree86 v.1.0 license
Copyright remains with the author

On Thu, 18 Mar 2004 09:14:37 -0800, Vigilance Monitoring wrote:

> I'm trying to upgrade openssh from 3.1p1 to 3.7p1 on RHL 7.3
>
> I downloaded the src rpm file and created an installable RPM.
>
> When I try to do a rpm -Fvh or rpm Uvh on the rpm I get a dependency
> complaint that openssh-1.3p1-blah-14 are needed.
>
> If I do a rpm -qa |grep openssh, all of he dependency complaints list as
> being installed.
>
> I've read the white papers on the rpm implementation and I realize that
> it is .... sub optimal. However, before installing this upgrade from
> source I wanted to see if anyone had any suggestions. Rpm is really
> great when it works and I certainly admit to being now expert. Perhaps
> someone's seen this problem?

Yes, the problem your understanding of the upgrade effort and what the
package manager (RPM) 'warning messages' are telling you in this case. The
package manager (RPM) 'warning messages' is an attempt in not allowing you
to break your system configuration by the single package upgrade when
multiple packages are required for the upgrade.

You have the list of the openssh RPM's that are required for the openssh
upgrade, the 'rpm -qa | grep openssh' output. Use this list as a reference
guide for the upgrade.

You have created the openssh-3.7p1 RPM package, what about the rest? If
during the time you created the binary RPM for the openssh 3.7p1 upgrade,
where any other non debug RPM's created also? If yes, then do they match
the known list of the openssh 3.1p1 RPM's? If yes, then install them all
at the same time, as root type something like 'rpm -Fvh *.rpm' from where
the packages are located. If not then you have some more work to do.
Basically you want the same updated openssh 3.7p1 RPM packages as the
currently installed openssh 3.1p1 RPM's as list from the output of the
'rpm -qa | grep openssh' command.


--
Posted under the XFree86 v.1.0 license
Copyright remains with the author

On Thu, 18 Mar 2004 09:14:37 -0800, Vigilance Monitoring wrote:

> I'm trying to upgrade openssh from 3.1p1 to 3.7p1 on RHL 7.3
>
> I downloaded the src rpm file and created an installable RPM.
>
> When I try to do a rpm -Fvh or rpm Uvh on the rpm I get a dependency
> complaint that openssh-1.3p1-blah-14 are needed.
>
> If I do a rpm -qa |grep openssh, all of he dependency complaints list as
> being installed.
>
> I've read the white papers on the rpm implementation and I realize that
> it is .... sub optimal. However, before installing this upgrade from
> source I wanted to see if anyone had any suggestions. Rpm is really
> great when it works and I certainly admit to being now expert. Perhaps
> someone's seen this problem?

Yes, the problem your understanding of the upgrade effort and what the
package manager (RPM) 'warning messages' are telling you in this case. The
package manager (RPM) 'warning messages' is an attempt in not allowing you
to break your system configuration by the single package upgrade when
multiple packages are required for the upgrade.

You have the list of the openssh RPM's that are required for the openssh
upgrade, the 'rpm -qa | grep openssh' output. Use this list as a reference
guide for the upgrade.

You have created the openssh-3.7p1 RPM package, what about the rest? If
during the time you created the binary RPM for the openssh 3.7p1 upgrade,
where any other non debug RPM's created also? If yes, then do they match
the known list of the openssh 3.1p1 RPM's? If yes, then install them all
at the same time, as root type something like 'rpm -Fvh *.rpm' from where
the packages are located. If not then you have some more work to do.
Basically you want the same updated openssh 3.7p1 RPM packages as the
currently installed openssh 3.1p1 RPM's as list from the output of the
'rpm -qa | grep openssh' command.


--
Posted under the XFree86 v.1.0 license
Copyright remains with the author

rpm -Fvh *.rpm solved it. Thanks very much.

A follow up question if you don't mind.

The new openssh is still using openssl 0.9.6b which I plan to upgrade
shortly. Will I need to do anything further with openssh or will it pick up
the new SSL stuff once it's installed?

Many thanks in advance


"Lenard" <lenard@127.0.0.1> wrote in message
newsan.2004.03.18.18.54.17.307781@127.0.0.1...
> On Thu, 18 Mar 2004 09:14:37 -0800, Vigilance Monitoring wrote:
>
> > I'm trying to upgrade openssh from 3.1p1 to 3.7p1 on RHL 7.3
> >
> > I downloaded the src rpm file and created an installable RPM.
> >
> > When I try to do a rpm -Fvh or rpm Uvh on the rpm I get a dependency
> > complaint that openssh-1.3p1-blah-14 are needed.
> >
> > If I do a rpm -qa |grep openssh, all of he dependency complaints list as
> > being installed.
> >
> > I've read the white papers on the rpm implementation and I realize that
> > it is .... sub optimal. However, before installing this upgrade from
> > source I wanted to see if anyone had any suggestions. Rpm is really
> > great when it works and I certainly admit to being now expert. Perhaps
> > someone's seen this problem?
>
> Yes, the problem your understanding of the upgrade effort and what the
> package manager (RPM) 'warning messages' are telling you in this case. The
> package manager (RPM) 'warning messages' is an attempt in not allowing you
> to break your system configuration by the single package upgrade when
> multiple packages are required for the upgrade.
>
> You have the list of the openssh RPM's that are required for the openssh
> upgrade, the 'rpm -qa | grep openssh' output. Use this list as a reference
> guide for the upgrade.
>
> You have created the openssh-3.7p1 RPM package, what about the rest? If
> during the time you created the binary RPM for the openssh 3.7p1 upgrade,
> where any other non debug RPM's created also? If yes, then do they match
> the known list of the openssh 3.1p1 RPM's? If yes, then install them all
> at the same time, as root type something like 'rpm -Fvh *.rpm' from where
> the packages are located. If not then you have some more work to do.
> Basically you want the same updated openssh 3.7p1 RPM packages as the
> currently installed openssh 3.1p1 RPM's as list from the output of the
> 'rpm -qa | grep openssh' command.
>
>
> --
> Posted under the XFree86 v.1.0 license
> Copyright remains with the author

rpm -Fvh *.rpm solved it. Thanks very much.

A follow up question if you don't mind.

The new openssh is still using openssl 0.9.6b which I plan to upgrade
shortly. Will I need to do anything further with openssh or will it pick up
the new SSL stuff once it's installed?

Many thanks in advance


"Lenard" <lenard@127.0.0.1> wrote in message
newsan.2004.03.18.18.54.17.307781@127.0.0.1...
> On Thu, 18 Mar 2004 09:14:37 -0800, Vigilance Monitoring wrote:
>
> > I'm trying to upgrade openssh from 3.1p1 to 3.7p1 on RHL 7.3
> >
> > I downloaded the src rpm file and created an installable RPM.
> >
> > When I try to do a rpm -Fvh or rpm Uvh on the rpm I get a dependency
> > complaint that openssh-1.3p1-blah-14 are needed.
> >
> > If I do a rpm -qa |grep openssh, all of he dependency complaints list as
> > being installed.
> >
> > I've read the white papers on the rpm implementation and I realize that
> > it is .... sub optimal. However, before installing this upgrade from
> > source I wanted to see if anyone had any suggestions. Rpm is really
> > great when it works and I certainly admit to being now expert. Perhaps
> > someone's seen this problem?
>
> Yes, the problem your understanding of the upgrade effort and what the
> package manager (RPM) 'warning messages' are telling you in this case. The
> package manager (RPM) 'warning messages' is an attempt in not allowing you
> to break your system configuration by the single package upgrade when
> multiple packages are required for the upgrade.
>
> You have the list of the openssh RPM's that are required for the openssh
> upgrade, the 'rpm -qa | grep openssh' output. Use this list as a reference
> guide for the upgrade.
>
> You have created the openssh-3.7p1 RPM package, what about the rest? If
> during the time you created the binary RPM for the openssh 3.7p1 upgrade,
> where any other non debug RPM's created also? If yes, then do they match
> the known list of the openssh 3.1p1 RPM's? If yes, then install them all
> at the same time, as root type something like 'rpm -Fvh *.rpm' from where
> the packages are located. If not then you have some more work to do.
> Basically you want the same updated openssh 3.7p1 RPM packages as the
> currently installed openssh 3.1p1 RPM's as list from the output of the
> 'rpm -qa | grep openssh' command.
>
>
> --
> Posted under the XFree86 v.1.0 license
> Copyright remains with the author

rpm -Fvh *.rpm solved it. Thanks very much.

A follow up question if you don't mind.

The new openssh is still using openssl 0.9.6b which I plan to upgrade
shortly. Will I need to do anything further with openssh or will it pick up
the new SSL stuff once it's installed?

Many thanks in advance


"Lenard" <lenard@127.0.0.1> wrote in message
newsan.2004.03.18.18.54.17.307781@127.0.0.1...
> On Thu, 18 Mar 2004 09:14:37 -0800, Vigilance Monitoring wrote:
>
> > I'm trying to upgrade openssh from 3.1p1 to 3.7p1 on RHL 7.3
> >
> > I downloaded the src rpm file and created an installable RPM.
> >
> > When I try to do a rpm -Fvh or rpm Uvh on the rpm I get a dependency
> > complaint that openssh-1.3p1-blah-14 are needed.
> >
> > If I do a rpm -qa |grep openssh, all of he dependency complaints list as
> > being installed.
> >
> > I've read the white papers on the rpm implementation and I realize that
> > it is .... sub optimal. However, before installing this upgrade from
> > source I wanted to see if anyone had any suggestions. Rpm is really
> > great when it works and I certainly admit to being now expert. Perhaps
> > someone's seen this problem?
>
> Yes, the problem your understanding of the upgrade effort and what the
> package manager (RPM) 'warning messages' are telling you in this case. The
> package manager (RPM) 'warning messages' is an attempt in not allowing you
> to break your system configuration by the single package upgrade when
> multiple packages are required for the upgrade.
>
> You have the list of the openssh RPM's that are required for the openssh
> upgrade, the 'rpm -qa | grep openssh' output. Use this list as a reference
> guide for the upgrade.
>
> You have created the openssh-3.7p1 RPM package, what about the rest? If
> during the time you created the binary RPM for the openssh 3.7p1 upgrade,
> where any other non debug RPM's created also? If yes, then do they match
> the known list of the openssh 3.1p1 RPM's? If yes, then install them all
> at the same time, as root type something like 'rpm -Fvh *.rpm' from where
> the packages are located. If not then you have some more work to do.
> Basically you want the same updated openssh 3.7p1 RPM packages as the
> currently installed openssh 3.1p1 RPM's as list from the output of the
> 'rpm -qa | grep openssh' command.
>
>
> --
> Posted under the XFree86 v.1.0 license
> Copyright remains with the author