[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#55167: marked as done (ncurses-base obsolete, but essential)



Your message dated Thu, 10 Feb 2000 19:06:30 -0700 (MST)
with message-id <Pine.LNX.3.96.1000210190454.18414G-100000@wakko.deltatee.com>
and subject line Blah?
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; 15 Jan 2000 00:59:50 +0000
Received: (qmail 9511 invoked from network); 15 Jan 2000 00:59:48 -0000
Received: from adsl-63-193-116-241.dsl.snfc21.pacbell.net (HELO kitenet.net) (qmailr@63.193.116.241)
  by master.debian.org with SMTP; 15 Jan 2000 00:59:48 -0000
Received: (qmail 9117 invoked by uid 500); 15 Jan 2000 00:59:46 -0000
Date: Fri, 14 Jan 2000 16:59:46 -0800
From: Joey Hess <joeyh@debian.org>
To: Konrad Mierendorff <mierendorff@gmx.net>
Cc: debian-user@lists.debian.org, submit@bugs.debian.org
Subject: Re: ncurses-base obsolete, but essential
Message-ID: <20000114165946.A27676@kitenet.net>
Mail-Followup-To: Konrad Mierendorff <mierendorff@gmx.net>,
	debian-user@lists.debian.org, submit@bugs.debian.org
References: <E1291iA-0001X3-00@riva.ucam.org> <387F58CA.1CC69BBE@gmx.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
User-Agent: Mutt/1.0i
In-Reply-To: <387F58CA.1CC69BBE@gmx.net>; from mierendorff@gmx.net on Fri, Jan 14, 2000 at 06:11:38PM +0100

Package: apt
Version: 0.3.16

Konrad Mierendorff wrote:
> > You are about to do something potentially harmful
> > To continue type in the phrase 'Yes, I understand this may be bad'
> >  ?]
> 
> I can't believe this one! Programm behavior like this really sucks!
> 
> One of the many small details that make Linux more usable is the absence
> of such queries. Seems as if this is changing now.

You're missing a lot of history. Historically, the only way to remove an
essential package has been "dpkg --force-essential --remove foo". You could
not do it from inside dselect. Dselect remove methods probably just gave up
with something like:

dpkg: error processing bash (--remove):
 This is an essential package - it should not be removed.

Apt allows you to remove essential packages from inside dselect for the
first time. The prompt really isn't any different than dpkg's insistance on
--force options in some situations.

I do think that apt should be modified to omit the prompt if some other
essential package declares a conflicts (and perhaps a replaces too?) on the
obsolete essential package. Jason, the idea there is that we need *some* way
to allow obsolete essential packages (like ncurses-base) to be removed
without forcing everyone who upgrades to type in that sentance, and if the
maintainer of an essential package declares a conflicts, I think that is a
good indication that removing the obsolete essential package is safe.

-- 
see shy jo
---------------------------------------
Received: (at 55167-done) by bugs.debian.org; 11 Feb 2000 02:05:52 +0000
Received: (qmail 4146 invoked from network); 11 Feb 2000 02:05:51 -0000
Received: from wakko.powersurfr.com (HELO wakko.deltatee.com) (mail@24.108.53.97)
  by master.debian.org with SMTP; 11 Feb 2000 02:05:51 -0000
Received: from localhost (wakko.deltatee.com) [127.0.0.1] (jgg)
	by wakko.deltatee.com with smtp (Exim 2.11 #1)
	id 12J5Ta-00053y-00 (Debian); Thu, 10 Feb 2000 19:06:30 -0700
Date: Thu, 10 Feb 2000 19:06:30 -0700 (MST)
From: Jason Gunthorpe <jgg@ualberta.ca>
X-Sender: jgg@wakko.deltatee.com
To: 55167-done@bugs.debian.org
Subject: Blah?
Message-ID: <Pine.LNX.3.96.1000210190454.18414G-100000@wakko.deltatee.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


This isn't even a bug :>

Jason


Reply to: