06-28-2009
rpm -Uvh
Use the -U option with rpm to upgrade packages.
I'd use the command line and forget about using the gui to handle rpm packages.
The -Uvh option will first check to see if the new module is an upgrade of an existing module and if it meets the requirements it will perform the upgrade and you'll see the upgrade in verbose mode via stdout.
-Outervillage
Quote:
Originally Posted by
shipon_97
Friends ,
I cannot upgrade or add any package in RHEL 5 using 'package manager' GUI tools . When I run the 'package manager' tool then in BROWSE tab , it shows nothing . I try it inserting the RHEL5 DVD in the DVD-Rom . But the condition is the same .
Would anybody plz tell me , How can I resolve this problem ?
Last edited by vbe; 06-29-2009 at 05:59 AM..
Reason: rm URL
10 More Discussions You Might Find Interesting
1. Solaris
Hi,
Is there an easy way to remove a cluster/meta cluster package (along with all the packages contained in the cluster package) in Solaris 10 ? I'm new to Solaris. (0 Replies)
Discussion started by: agn
0 Replies
2. Linux
Dear all,
I would like to install a new version of package without remove old version on Centos and vice versa.
Please give me advice!
thanks much, (2 Replies)
Discussion started by: all4cfa
2 Replies
3. Emergency UNIX and Linux Support
Hello,
i have installed a package by using the command
sudo rpm -i filepackage.rpm
package filepackage is already installed
when i try to remove it, i get an error saying "is not installed":
sudo rpm -e filepackage.rpm
error: package filepackage is not installed
How can... (4 Replies)
Discussion started by: g_p
4 Replies
4. Red Hat
Hi, I can't delete an NIS user. Does it sound too simple for you? :( Here is the result:
nis_server# ypcat passwd | grep heisgone
heisgone:xxxxxx:1000:200:He is gone:/home/heisgone:/usr/bin/ksh
nis_server# userdel heisgone
userdel: error deleting password entry
userdel: error deleting... (1 Reply)
Discussion started by: aixlover
1 Replies
5. UNIX for Advanced & Expert Users
Hi,
How to remove the allocate SAN Lun on the Linux Server. I am using rhel 5.8. I have assigned a LUN to the existing Volume group.
For eg: I have allocated a LUN with 20GB to the existing volume group(test123). Now, how can I take back the allocated lun without any issues. (1 Reply)
Discussion started by: gsiva
1 Replies
6. Red Hat
Hello!,
I can't remove a rpm package with rpm -e net-snmp
Nothing happened, and the process returns D status when i see with ps aux | grep rpm. When i say "Nothing Happened", the terminal don't return any message, and not remove the package.
What can I do to remove?
Ps: I work with Red... (1 Reply)
Discussion started by: Douglas Ramalho
1 Replies
7. Red Hat
Hi all,
Im studying rhcsa as of now, so yum installation and dependencies are messing me to not workit out.
i have dual os, win 7 & rhel 6.
i have tried this installation of vsftpd package with rhel 6 dvd in VM rhel 6 in win 7 as well as host rhel 6.still the same issue.
below error... (6 Replies)
Discussion started by: redhatlbug
6 Replies
8. Red Hat
Hi all,
I have a 2 node rhel 5.5 cluster (2 server and 1 quorum disk).
I created 2 cluster resources using Luci web console, they are 2 Volume Groups.
I want to remove that cluster and shutdown node 2, but I don't want to loose data on Volume Groups clustered.
How can I remove that... (0 Replies)
Discussion started by: peppeunz
0 Replies
9. Red Hat
Hi All,
I am a Solaris administartor. I got in to a probelm with RHEL.
I thought someone can help me on this forum ..
Can we download/install packages on a Redhat server with yum with out registering on RHEL network or website ? (1 Reply)
Discussion started by: sri243
1 Replies
10. Red Hat
I require to install xrdp for remote desktop access of my linux server (RHEL 7.3).I searched a lot for it in google, but not able to find any suitable package for the same.One post I have found where the server where I am need to connect the server in Internet.But it is not possible for me to... (2 Replies)
Discussion started by: Anjan Ganguly
2 Replies
LEARN ABOUT NETBSD
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)