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

Bug#250422: marked as done (Base-config: package installation inconsistency)

Your message dated Mon, 10 Oct 2005 00:11:40 +0200
with message-id <200510100011.41056.aragorn@tiscali.nl>
and subject line Base-config: package installation inconsistency
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.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

Received: (at submit) by bugs.debian.org; 22 May 2004 21:06:50 +0000
>From aragorn@tiscali.nl Sat May 22 14:06:49 2004
Return-path: <aragorn@tiscali.nl>
Received: from 195-240-184-66-mx.xdsl.tiscali.nl (elrond.fjphome.nl) [] 
	by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
	id 1BRdhh-0001qE-00; Sat, 22 May 2004 14:06:49 -0700
Received: from galadriel.fjphome.nl ([] ident=fjp)
	by elrond.fjphome.nl with esmtp (Exim 3.35 #1 (Debian))
	id 1BRdhC-0006T2-00
	for <submit@bugs.debian.org>; Sat, 22 May 2004 23:06:18 +0200
From: Frans Pop <aragorn@tiscali.nl>
To: submit@bugs.debian.org
Subject: Base-config: package installation inconsistency
Date: Sat, 22 May 2004 23:06:18 +0200
User-Agent: KMail/1.6
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: text/plain;
Content-Transfer-Encoding: 7bit
Message-Id: <200405222306.18252.aragorn@tiscali.nl>
Delivered-To: submit@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-7.0 required=4.0 tests=BAYES_01,HAS_PACKAGE 
	autolearn=no version=2.60-bugs.debian.org_2004_03_25

Package: base-config
Version: 2.21
Severity: wishlist

If I use apt to select which package to install, mdetect and read-edid (and 
possibly others) are shown as:
 *** Opt utils   mdetect     ....
 *** Opt utils   read-edid   ....

However, when I check after installation has completed, both packages have 
magically disappeared. This is confusing to users.
It would be more consistent if the package selection tools would show which 
packages will be present on the system after installation.

Packages that are to be removed (or added) by the installer, should
- either be installed/removed,
- or be marked as such (so the user can override this or the package
  installation step can handle the actual installation/removal)
before the package selection step in base-config.

This is not a 'hard' bug, but I was very confused the first time I noticed 
this. My feeling is this should be possible, because nothing really important 
gets done after package selection, but if there are problems 'won't fix' is 
OK with me.

Received: (at 250422-done) by bugs.debian.org; 9 Oct 2005 22:11:38 +0000
>From aragorn@tiscali.nl Sun Oct 09 15:11:38 2005
Return-path: <aragorn@tiscali.nl>
Received: from smtp-out2.tiscali.nl [] 
	by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
	id 1EOjOM-0007Le-00; Sun, 09 Oct 2005 15:11:38 -0700
Received: from [] (helo=strider.fjphome.nl)
	by smtp-out2.tiscali.nl with esmtp (Tiscali http://www.tiscali.nl)
	id 1EOjOL-0000ox-GO
	for <250422-done@bugs.debian.org>; Mon, 10 Oct 2005 00:11:37 +0200
From: Frans Pop <aragorn@tiscali.nl>
To: 250422-done@bugs.debian.org
Subject: Base-config: package installation inconsistency
Date: Mon, 10 Oct 2005 00:11:40 +0200
User-Agent: KMail/1.7.2
MIME-Version: 1.0
Content-Type: text/plain;
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200510100011.41056.aragorn@tiscali.nl>
Delivered-To: 250422-done@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no 

Closing as this bug is no longer relevant.

Reply to: