Your message dated Fri, 29 Jan 2010 13:30:40 +1100
with message-id <20100129023040.gc12...@enc.com.au>
and subject line Re: Bug#566211: procps init.d script problem
has caused the Debian Bug report #566211,
regarding procps: Installation/Removal scripts give install-rc.d issues with 
symlinks
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
566211: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=566211
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: procps
Version: 1:3.2.7-11
Severity: grave
Justification: renders package unusable



-- System Information:
Debian Release: 5.0.3
  APT prefers proposed-updates
  APT policy: (500, 'proposed-updates'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-2 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_US.utf8)
Shell: /bin/sh linked to /bin/bash

Versions of packages procps depends on:
ii  libc6                     2.7-18lenny2   GNU C Library: Shared libraries
ii  libncurses5               5.7+20081213-1 shared libraries for terminal hand
ii  lsb-base                  3.2-20         Linux Standard Base 3.2 init scrip

Versions of packages procps recommends:
ii  psmisc                        22.6-1     Utilities that use the proc filesy

procps suggests no packages.

-- no debconf information

I get several errors from install-rc.d when I try to install procps, mentioning 
"dangling" symlinks. I've tried everything to get it working.



--- End Message ---
--- Begin Message ---
On Thu, Jan 28, 2010 at 03:21:34PM -0500, Glen wrote:
>    Sorry for not replying to you originally. Somehow I got it fixed, I think
>    it may have been through deleting the post-rm script in dpkg, running the
>    uninstaller, then reinstalling it.
As this bug looks like either a transistional one, or one due to local
changes I'll close it. There's no way of diagnosing what it was anyhow.

 - Craig
-- 
Craig Small      GnuPG:1C1B D893 1418 2AF4 45EE  95CB C76C E5AC 12CA DFA5
http://www.enc.com.au/                             csmall at : enc.com.au
http://www.debian.org/          Debian GNU/Linux, software should be Free 


--- End Message ---

Reply via email to