which-pkg-broke(1) [debian man page]

which-pkg-broke(1)						  debian-goodies						which-pkg-broke(1)

NAME

       which-pkg-broke - find which package might have broken another

SYNOPSIS

       which-pkg-broke package

DESCRIPTION

       The  which-pkg-broke  program  will retrieve a list of the named package and all its dependencies sorted by the time they were installed on
       the system (as determined from the mtime information of /var/lib/dpkg/info/*.list .

       This tool makes it possible for a system admin to obtain information that might correlate installation of package dependencies with a pack-
       age breakage in order to find which package update might be responsible for the breakage.

EXAMPLES

       This tool can be useful determine which package dependencies were upgraded more recently and might be associated with the bug that is being
       observed.  For example, if aptitude stops working properly, an administrator can run:

       $ which-pkg-broke aptitude
       Package <libapt-pkg-libc6.3-5-3.3> has no install time info
       libdb1-compat			Fri Aug  8 03:02:11 2003
       libsigc++-1.2-5c102		Fri Aug  8 05:15:58 2003
       aptitude 			Sun Jan 11 17:38:06 2004
       libncurses5			Sun Jan 18 08:11:05 2004
       libc6				Thu Jan 22 07:55:10 2004
       libgcc1				Tue Jan 27 07:37:22 2004
       gcc-3.3-base			Tue Jan 27 07:37:31 2004
       libstdc++5			Tue Jan 27 07:37:32 2004

       So depending on exactly when the misbehaviour started, there may be a reason to point the finger at a more-recently  updated  library  like
       libstdc++ or libncurses, which are more-recently installed than aptitude itself.

SEE ALSO

       rc-alert(1)

AUTHOR

       which-pkg-broke was written by Bill Gribble <grib AT billgribble.com>

       This manual page was written by Javier Fernandez-Sanguino for the Debian GNU/Linux distribution.

debian-goodies							   July 24 2006 						which-pkg-broke(1)

scap-as-rpm(8)						  System Administration Utilities					    scap-as-rpm(8)

NAME

       scap-as-rpm - manual page for scap-as-rpm

DESCRIPTION

       usage: scap-as-rpm [-h] [--pkg-name PKG_NAME] [--pkg-version PKG_VERSION]

	      [--pkg-release   PKG_RELEASE]   [--pkg-summary  PKG_SUMMARY]  [--pkg-license  PKG_LICENSE]  [--pkg-scap-location	PKG_SCAP_LOCATION]
	      [--rpm-destination RPM_DESTINATION] [--srpm-destination SRPM_DESTINATION] FILE [FILE ...]

       Takes given SCAP input(s) and makes an RPM package that contains them. The result  RPM  can  be	installed  using  #  yum  install  ./pack-
       age-name-1-1.rpm which will put the contents into /usr/share/xml/scap. No dependency on openscap or scapworkbench is enforced in the output
       package so you can use any SCAP-capable scanner to evaluate the content.

   positional arguments:
       FILE   List of files that should be put into the result package. These should be SCAP XML files but such requirement is not enforced.

   optional arguments:
       -h, --help
	      show this help message and exit

       --pkg-name PKG_NAME
	      Name of the RPM package, if none is provided the basename of the first SCAP input is used. Ex.: xyzsecurity-guide

       --pkg-version PKG_VERSION

       --pkg-release PKG_RELEASE

       --pkg-summary PKG_SUMMARY
	      Optional short description of the package.

       --pkg-license PKG_LICENSE
	      Short name of the license that you want to publish the package under. Ex.: GPLv2+, BSD, ...

       --pkg-scap-location PKG_SCAP_LOCATION
	      Folder where SCAP files are supposed to be installed.  Each package will have its own folder inside this folder. RPM  variables  can
	      be used and will be expanded as usual. It is recommended to keep the default settings.

       --rpm-destination RPM_DESTINATION
	      The folder (absolute or relative to CWD) where the result RPM shall be saved.

       --srpm-destination SRPM_DESTINATION
	      The folder (absolute or relative to CWD) where the result SRPM shall be saved.

scap-as-rpm							   November 2013						    scap-as-rpm(8)