By the way, I suggest changing the 'stable' keyword in your sources.list to the release you use (woody/sarge/etch). It happened before that packages got broken because of this when a new release got out.
Hey whats up all of you pro's i have one question for you im not to familiar with HP UX 11i, but i would like to load it on my home machine. I am sure this is a dumb question but is there any special hardware requirements. I have reloaded the sysem at my work on a L class 9000 well not exactly by... (9 Replies)
I am trying to build a Sun Ultra 10 with solaris 10. This computer is one of a collection that was donated to the non-profic company I work for. All media was wiped before I recieved them, so I am starting from stratch.
I downloaded the Solaris 10 ISO and burned a DVD. The computer came with a... (4 Replies)
Hello,
What is the simplest way to install CentOS 6.1 with console base-system only using official LiveDVD image on VirtualBox machine? I'd like to get simplest console with network support like FreeBSD base installation. Then, install services which I need.
The installer jest extracts the... (2 Replies)
Hi guys
I would like to install Red Hat Linux 4.2 on my old box (pIII). However there is a problem: i can't find the .iso image anywhere in the Net, all the material that i've found is (i think) an install tree of the OS.
It will be possible for me to install the OS from that install tree?
... (3 Replies)
Hello,
I would like to ask if someone knows if is possible to install sofware via smitty or installp in another directorie , or we have to accept the default location?
i would like to intall in /opt folder , but smitty installed it in /usr
Thanks in advance (4 Replies)
Discussion started by: prpkrk
4 Replies
LEARN ABOUT DEBIAN
which-pkg-broke
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)