Sponsored Content
Full Discussion: New Patchset
Operating Systems Solaris New Patchset Post 303014596 by DukeNuke2 on Thursday 15th of March 2018 10:10:59 AM
Old 03-15-2018
From when is the latest patchset you use? The latest patchcluster I can see is from january.
This User Gave Thanks to DukeNuke2 For This Post:
 

2 More Discussions You Might Find Interesting

1. Solaris

Recommended patchset for Solaris and the patch bundle

Hello I recently downloaded and installed the latest patchset for Solaris 10 (update 5) running on SPARC. Actually I am new to Solaris (I come from Red Hat) and the security department asked me to update the system for security fixes. I logged in to Oracle support and used the recommended patch... (3 Replies)
Discussion started by: abohmeed
3 Replies

2. Solaris

Problem with SMC after applying Patchset 1-148888-03

Here is the problem: I have several servers that now have been updated from PatchSet # 147440-19 to PatchSet # 148888-03. The servers range from: (1) SunFire T2000 (3) Enterprise T5140 (2) Enterprise T5220 Solaris 10 08/11 u10 on 1 and u7 on the others. After the patch is applied I... (7 Replies)
Discussion started by: Wraith_G2IC
7 Replies
PKGKDE-OVERRIDE-SC-DEV-LATEST(1)			User Contributed Perl Documentation			  PKGKDE-OVERRIDE-SC-DEV-LATEST(1)

NAME
pkgkde-override-sc-dev-latest - loosen kde-sc-dev-latest Break restrictions SYNOPSIS
pkgkde-override-sc-dev [-bbase_version] [-vversion] DESCRIPTION
pkgkde-override-sc-dev-lastest is a helper utility which can be used to generate a dummy kde-sc-dev-latest package without Breaks field that is present in the original version. Original kde-sc-dev-latest package is used to force KDE Software Compilation modules to be built against the latest version of the KDE Development Platform modules without bumping versions of a bunch build dependencies for each KDE SC module. However, while original kde-sc-dev-latest does not cause problems when building in clean chroots, the restrictions imposed by its Breaks field might be undesirable on the maintainer system when: o the maintainer wants to (test)build KDE module version X.Y.A against KDE Development Platform X.Y.B where (A > B); o the maintainer builds a new upstream version of the some KDE Development Platform module on the system that has an old version of some KDE Development Platform packages installed. For example, even if kdepimlibs does not build depend on kdebase-workspace-dev, original kde-sc-dev-latest may prevent kdepimlibs X.Y.A to be built on the system which has kdebase-workspace X.Y.B (where A > B) installed. By default, pkgkde-override-sc-dev-latest generates a dummy kde-sc-dev-latest package in the current working directory that is based on the current "candidate" version of the original kde-sc-dev-latest (as per apt-cache policy). You may specify a base version with the -b option. The resulting dummy kde-sc-dev-latest override package will have "base_version+override" as its version unless another one is specified with -v option. Once the package is generated, you can install it like: # dpkg --install kde-sc-dev_<version>+override_all.deb OPTIONS
-bbase_version, --basever=base_version The version of the original kde-sc-dev-latest package to base an override package on. It must be available in the APT database on the system. You may also pass special value "latest" to select the latest available version in the APT database. If you specify "priority", the latest version with the highest priority will be selection. By default (if this option is not specified), candidate version is selected -vversion, --version=version Generate an override package with the specified "version+override" rather than default "base_version+override" version. AUTHOR
Modestas Vainius <modax@debian.org> perl v5.14.2 2011-12-26 PKGKDE-OVERRIDE-SC-DEV-LATEST(1)
All times are GMT -4. The time now is 06:53 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy