01-12-2009
RPM and dependencies OPENSSH
Hello
Sorry, I am not to well versed in RHE and I am having some issues.
I have doen a cursury look around and could not find an answer.
I have 2 RHE4 servers. Both have old versions of OPENSSH along with , server, askpass, askpass-gnome, etc.
I cannot upgrade to our new pkg release of openssh (internal) because of all the dependencied for each of these.
Is --nodeps a safe solution and upgrade each package indivudually? Should I just remove each and install new? A better solution?
Thanks in advance
Mike
10 More Discussions You Might Find Interesting
1. Linux
Hey,
I've a problem installing a package. rpm -ivh brings the errors:
libjvm.so is needed by
libverify.so is needed by
But I have installed the Java SDK like requested and the files are on the disk. But I have no idea how to find out, why rpm cann't find them.
I have also... (2 Replies)
Discussion started by: mod
2 Replies
2. SuSE
Hi,
I have got few RPM's from rpmfind.net ( mainly gcc ).
But it seems to be src files instead of the image.
so I think we have to build the src files according to target machine using rpmbuild.
Can any one help me with
1) Various options of rpm build that have to be taken care
2)... (3 Replies)
Discussion started by: Sivaswami
3 Replies
3. UNIX for Advanced & Expert Users
I am needing to recompile openssh to hide the ssh banner which I found I can do in the version.h. I know.. I know, but its a requirement of some dumb security company so the company I work for can get their blessing.
Anyway. I am going to upgrade in the process and have downloaded the source... (2 Replies)
Discussion started by: creedog
2 Replies
4. Shell Programming and Scripting
It's the end of the day and I just can't get my head around this. I'm trying to extract just the name of the RPM from the path to a .rpm file. So from:
/home/me/rpm/RPMS/i386/nagios-our-plugins-1.2-6.i386.rpmI need to extract 'nagios-our-plugins'.
I can't get the awk syntax right:
awk '{... (5 Replies)
Discussion started by: aussieos
5 Replies
5. Red Hat
Hello,
I am trying to install krb5-libs-1.4-4.pp-rh73.i386.rpm on my Red Hat 7.X server, however while installing/upgrading it fails due to dependencies.
I checked for these dependencies and i already found them on the server.
I wonder why it is giving these errors.
I tried copying these... (1 Reply)
Discussion started by: sunny_a_j
1 Replies
6. Shell Programming and Scripting
How to make RPM not write to RPM database if RPM fails to deploy?
IE I create an rpm spec file that contains the following
if
then
exit 1
fi
My rpm will fail at deployment, but if I do rpm -qa , I can see the rpm in the rpm db (3 Replies)
Discussion started by: 3junior
3 Replies
7. SuSE
Hi,
I'm having issues with implicit dependencies for my RPM package. This is the error I'm getting:
error: Failed dependencies:
libclntsh.so.11.1()(64bit) is needed by geomatica-10.4-0.x86_64
Our software has a dynamically loaded library which links to the Oracle's libclntsh.so.11.1... (2 Replies)
Discussion started by: pneveu
2 Replies
8. SuSE
Hi All,
I wanted to install an rpm package on two suse 10 systems. It installed successfully on one system but on the other it throws an error like
error: Failed dependencies:
rpmlib(PayloadIsLzma) <= 4.4.2-1 is needed by linuxProj-1-1.noarch
Now this means that rpnm... (4 Replies)
Discussion started by: dirshah
4 Replies
9. AIX
dears
i am trying to install the autoconf-2.63-1.aix6.1.noarch.rpm but its shows the below error message .
P700_dev/svn/dependencies>rpm -i autoconf-2.63-1.aix6.1.noarch.rpm
error: failed dependencies:
m4 is needed by autoconf-2.63-1
P700_dev/svn/dependencies> (6 Replies)
Discussion started by: thecobra151
6 Replies
10. Red Hat
I'm trying to package the latest Oracle JDK (1.7.0_51) into an RPM. Packaging works fine but when i try to install via rpm -Uvh xxx.rpm, i get the following:
#sudo rpm -ivh Sun_JDK7-1.7.0-51.x86_64.rpm
error: Failed dependencies:
libavcodec.so.52()(64bit) is needed by Sun_JDK7-1.7.0-51.x86_64... (3 Replies)
Discussion started by: asc123321
3 Replies
LEARN ABOUT V7
dh_systemd_start
DH_SYSTEMD_START(1) Debhelper DH_SYSTEMD_START(1)
NAME
dh_systemd_start - start/stop/restart systemd unit files
SYNOPSIS
dh_systemd_start [debhelperoptions] [--restart-after-upgrade] [--no-stop-on-upgrade] [unitfile...]
DESCRIPTION
dh_systemd_start is a debhelper program that is responsible for starting/stopping or restarting systemd unit files in case no corresponding
sysv init script is available.
As with dh_installinit, the unit file is stopped before upgrades and started afterwards (unless --restart-after-upgrade is specified, in
which case it will only be restarted after the upgrade). This logic is not used when there is a corresponding SysV init script because
invoke-rc.d performs the stop/start/restart in that case.
OPTIONS
--restart-after-upgrade
Do not stop the unit file until after the package upgrade has been completed. This is the default behaviour in compat 10.
In earlier compat levels the default was to stop the unit file in the prerm, and start it again in the postinst.
This can be useful for daemons that should not have a possibly long downtime during upgrade. But you should make sure that the daemon
will not get confused by the package being upgraded while it's running before using this option.
--no-restart-after-upgrade
Undo a previous --restart-after-upgrade (or the default of compat 10). If no other options are given, this will cause the service to
be stopped in the prerm script and started again in the postinst script.
-r, --no-stop-on-upgrade, --no-restart-on-upgrade
Do not stop service on upgrade.
--no-start
Do not start the unit file after upgrades and after initial installation (the latter is only relevant for services without a
corresponding init script).
NOTES
Note that this command is not idempotent. dh_prep(1) should be called between invocations of this command (with the same arguments).
Otherwise, it may cause multiple instances of the same text to be added to maintainer scripts.
Note that dh_systemd_start should be run after dh_installinit so that it can detect corresponding SysV init scripts. The default sequence
in dh does the right thing, this note is only relevant when you are calling dh_systemd_start manually.
SEE ALSO
debhelper(7)
AUTHORS
pkg-systemd-maintainers@lists.alioth.debian.org
11.1.6ubuntu2 2018-05-10 DH_SYSTEMD_START(1)