03-04-2008
Package Installation HELP!
To all,
I have just installed a newer software package on one of our Performance testing AIX machine A. I later found out that this package didn't need to be installed on this machine cause it was a client and not a server package. I want to back out with pkgrm but the old package doesn't exist on our repository machine anymore for some reason. We do have another machine B that is replicated with the same package i need located in /var/sadm/pkg/PACKAGEINEED. Is it safe to copy over the contents from Machine B over to A w/o causing any issues. My overall goal is to remove the new package and re-install the old one.
Many thanks,
AC
10 More Discussions You Might Find Interesting
1. HP-UX
Hi,
I have a question and hoping that someone might already know. I'm trying to do a silent installation on a packages. I generate a set of response files manually.
# swask -s /package.depot -c response_files \*
I'm able to install the package silently without any issues if I install... (0 Replies)
Discussion started by: mendocino
0 Replies
2. Solaris
Hi Friends,,
I got a doubt about installing packages after the installation of Solaris 10.
Suppose if we want to get smc tool by installing some packages from cd-3,,
then how can we know the packages that has to be installed to get the smc tool.
Can anyone help to solve this small... (1 Reply)
Discussion started by: sdspawankumar
1 Replies
3. Solaris
Hi,
I want to install man pages package from solaris 10.
Solaris 10 has already been installed on my servor but I have to add the man pages packages. I search for a long time on internet this package but I didn't find a compatible one... So I downloaded Solaris 10 from Sun site to get this... (12 Replies)
Discussion started by: MasterapocA
12 Replies
4. Red Hat
Hi,
can someone help me with this?
How do we apply a new version of s/w package without disrupting the processes & daemons running with the old version?
Thanks (1 Reply)
Discussion started by: naan
1 Replies
5. Red Hat
Hi there,
I've started playing around with Linux a few days back, as part of my intenship. I was wondering if there is anyway I can install custom packages (non RPM packages...say like Oracle) as a part of Kickstart. My machines are running RHEL 4.
Thanks a lot :) (1 Reply)
Discussion started by: iman453
1 Replies
6. Red Hat
Hi,
I have configured YUM repository on a server and we have 10 linux machine (clients).
Is there any way we can install a package on all the 10 machines from YUM repository server?
Please help me. (7 Replies)
Discussion started by: uday123
7 Replies
7. Solaris
Hi All,
I have a solaris machine, in which I wanted to find the Oracle Installation date and Solaris Installation date.Any ways of finding out the package installation dates.
Kindly let me know
Thanks
Rj (1 Reply)
Discussion started by: jegaraman
1 Replies
8. Solaris
can u tell me the procedure to install php 5 using package ..
i downloaded php-5.2.1-sol10-x86-local.gz from sunfreeware
i have added package using
pkgadd -d php-5.2.1-sol10-x86-local
then i have added these two lines in httpd.conf
LoadModule php5_module modules/libphp5.so... (7 Replies)
Discussion started by: senkerth
7 Replies
9. Fedora
Hi Guys I want to know whether is it possible to automatically Install a RPM package after installing OS.
Basically we have have one rpm package which we want to install as part of OS installation . Please Suggest (3 Replies)
Discussion started by: mr_deb
3 Replies
10. Solaris
I have Solaris-11 and installed few non global zones inside it. I saw many of the packages are not installed in non global zone after installing it.
root@pos_ddr01 # pkg list | wc -l
479
root@pos_ddr01 #
root@pos_ddr01-zkmq01:~# pkg list | wc -l
206
root@pos_ddr01-zkmq01:~#
I can... (1 Reply)
Discussion started by: solaris_1977
1 Replies
LEARN ABOUT MINIX
dh_systemd_enable
DH_SYSTEMD_ENABLE(1) Debhelper DH_SYSTEMD_ENABLE(1)
NAME
dh_systemd_enable - enable/disable systemd unit files
SYNOPSIS
dh_systemd_enable [debhelperoptions] [--no-enable] [--name=name] [unitfile...]
DESCRIPTION
dh_systemd_enable is a debhelper program that is responsible for enabling and disabling systemd unit files.
In the simple case, it finds all unit files installed by a package (e.g. bacula-fd.service) and enables them. It is not necessary that the
machine actually runs systemd during package installation time, enabling happens on all machines in order to be able to switch from
sysvinit to systemd and back.
In the complex case, you can call dh_systemd_enable and dh_systemd_start manually (by overwriting the debian/rules targets) and specify
flags per unit file. An example is colord, which ships colord.service, a dbus-activated service without an [Install] section. This service
file cannot be enabled or disabled (a state called "static" by systemd) because it has no [Install] section. Therefore, running
dh_systemd_enable does not make sense.
For only generating blocks for specific service files, you need to pass them as arguments, e.g. dh_systemd_enable quota.service and
dh_systemd_enable --name=quotarpc quotarpc.service.
FILES
debian/package.service, debian/package@.service
If this exists, it is installed into lib/systemd/system/package.service (or lib/systemd/system/package@.service) in the package build
directory.
debian/package.tmpfile
If this exists, it is installed into usr/lib/tmpfiles.d/package.conf in the package build directory. (The tmpfiles.d mechanism is
currently only used by systemd.)
debian/package.target, debian/package@.target
If this exists, it is installed into lib/systemd/system/package.target (or lib/systemd/system/package@.target) in the package build
directory.
debian/package.socket, debian/package@.socket
If this exists, it is installed into lib/systemd/system/package.socket (or lib/systemd/system/package@.socket) in the package build
directory.
debian/package.mount
If this exists, it is installed into lib/systemd/system/package.mount in the package build directory.
debian/package.path, debian/package@.path
If this exists, it is installed into lib/systemd/system/package.path (or lib/systemd/system/package@.path) in the package build
directory.
debian/package.timer, debian/package@.timer
If this exists, it is installed into lib/systemd/system/package.timer (or lib/systemd/system/package@.timer) in the package build
directory.
OPTIONS
--no-enable
Disable the service(s) on purge, but do not enable them on install.
Note that this option does not affect whether the services are started. That is controlled by dh_systemd_start(1) (using e.g. its
--no-start option).
--name=name
Install the service file as name.service instead of the default filename, which is the package.service. When this parameter is used,
dh_systemd_enable looks for and installs files named debian/package.name.service instead of the usual debian/package.service.
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_enable should be run before dh_installinit. The default sequence in dh does the right thing, this note is only
relevant when you are calling dh_systemd_enable manually.
SEE ALSO
dh_systemd_start(1), debhelper(7)
AUTHORS
pkg-systemd-maintainers@lists.alioth.debian.org
11.1.6ubuntu2 2018-05-10 DH_SYSTEMD_ENABLE(1)