Bug#31370: marked as done (libc6 and libc6-doc dependency loop?)
Your message dated Fri, 17 Sep 1999 12:55:04 -0700
with message-id <v04205526b4084cd773f0@[206.163.71.146]>
and subject line Fixed
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Darren Benham
(administrator, Debian Bugs database)
Received: (at submit) by bugs.debian.org; 1 Jan 1999 22:12:19 +0000
Received: (qmail 25312 invoked from network); 1 Jan 1999 22:12:18 -0000
Received: from aurora.alaska.edu (fsblk@137.229.18.100)
by master.debian.org with SMTP; 1 Jan 1999 22:12:18 -0000
Received: from localhost (fsblk@localhost)
by aurora.alaska.edu (8.9.1a/8.9.1) with SMTP id NAA03031
for <submit@bugs.debian.org>; Fri, 1 Jan 1999 13:12:14 -0900 (AKST)
Date: Fri, 1 Jan 1999 13:12:14 -0900 (AKST)
From: Britton <fsblk@aurora.alaska.edu>
To: submit@bugs.debian.org
Subject: libc6 and libc6-doc dependency loop?
Message-ID: <Pine.OSF.3.96.990101130439.7416A-100000@aurora.alaska.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Package: libc6
Version: latest libc6, obsolete libc6-doc
libc6-doc is listed as an obsolete package, but when you hit return for
the final time during package selection, a list recursive list comes up
with both libc6 and libc6-doc selected. However, when you hit return
again, the same list comes up again. Could the dependence rules for these
packages be outdated in some wierd way to cause this problem?
__
GNU GPL: "The Source will be with you... always."
Britton Kerin
Reply to: