Debian bug report logs - #1640
dselect conflict resolution is confusing

Package: dpkg; Reported by: rdm@tad.micro.umn.edu (Raul Miller); Done: Raul Miller <moth@magenta.com>.

Message received at debian-bugs:


From cus.cam.ac.uk!iwj10 Wed Oct 11 17:30:35 1995
Return-Path: <iwj10@cus.cam.ac.uk>
Received: from pixar.com by mongo.pixar.com with smtp
	(Smail3.1.28.1 #15) id m0t3BXf-000BCzC; Wed, 11 Oct 95 17:30 PDT
Received: from bootes.cus.cam.ac.uk by pixar.com with SMTP id AA17109
  (5.67b/IDA-1.5 for debian-bugs-pipe@mongo.pixar.com); Wed, 11 Oct 1995 17:29:48 -0700
Received: by bootes.cus.cam.ac.uk 
	(Smail-3.1.29.0 #36) id m0t3BWh-000BzMC; Thu, 12 Oct 95 01:29 BST
Received: by chiark
	id <m0t3B9f-0002ZwZ@chiark.al.cl.cam.ac.uk>
	(Debian /\oo/\ Smail3.1.29.1 #29.33); Thu, 12 Oct 95 01:05 BST
Message-Id: <m0t3B9f-0002ZwZ@chiark.al.cl.cam.ac.uk>
Date: Thu, 12 Oct 95 01:05 BST
From: Ian Jackson <iwj10@cus.cam.ac.uk>
To: debian-bugs@pixar.com
Subject: Re: Bug#1640: dselect conflict resolution is confusing

Raul Miller writes ("Bug#1640: dselect conflict resolution is confusing"):
> Package: dpkg
> Version: 1.0.3
> 
> When in "conflict resolution" in deselect, it's difficult to deselect
> the [old] conflicting package.  Ideally, you could just hit "-" to deselect
> some such old package, but there's no visible confirmation that this works.

If you look at the suggestions dselect makes about which packages it
thinks you might like to select you should see that the default action
is to deselect any package which conflicts with the one you've just
selected.

So, you can just hit Return - like it says on the intro help screen
that you got presented at the start of the conflict/dependency listing
- to accept dselect's suggestion.

> Furthermore, hitting RETURN (which I associate with "go down a level in
> the hierarchy") sometimes presents a more detailed conflict resolution
> mechanism and sometimes does not.

It will present another conflict/dependency resolution screen if your
selections on the first conflict/dependency screen still have
unresolved conflicts or dependencies.

Return means `accept these selections and go back up a level', not `go
down a level'.  I think this is better - I changed this recently; you
used to have to say `q' for `confirm changes and exit this list,
checking dependencies'.

> Furthermore, the select all packages option doesn't really select all
> packages (which is also confusing).

It does when I use it.  You have to use `D' followed by `Q' in the
resulting conflict resolution screen - but that's hardly surprising,
since many of the packages conflict with each other.

Ian.

Acknowledgement sent to Ian Jackson <iwj10@cus.cam.ac.uk>:
Extra info received and forwarded. Full text available.
Information forwarded to debian-devel@pixar.com:
Bug#1640; Package dpkg. Full text available.

Message received at debian-bugs-done:


From magenta.com!moth Wed Oct 11 08:33:34 1995
Return-Path: <moth@magenta.com>
Received: from pixar.com by mongo.pixar.com with smtp
	(Smail3.1.28.1 #15) id m0t339x-000HTKC; Wed, 11 Oct 95 08:33 PDT
Received: from magenta.com by pixar.com with SMTP id AA18370
  (5.67b/IDA-1.5 for debian-bugs-done-pipe@mongo.pixar.com); Wed, 11 Oct 1995 08:33:11 -0700
Received: (moth@localhost) by magenta.com (8.6.12/8.6.4) id LAA04019; Wed, 11 Oct 1995 11:28:38 -0400
Date: Wed, 11 Oct 1995 11:28:38 -0400
Message-Id: <199510111528.LAA04019@magenta.com>
From: Raul Miller <moth@magenta.com>
Reply-To: Raul Miller <moth@magenta.com>
To: debian-bugs-done@Pixar.com
In-Reply-To: <m0t32n8-0006iKC@rdm.legislate.com>
Subject: Re: Bug#1640: dselect conflict resolution is confusing

I'm marking this as done -- a large part of it came from trying to hit
'space' to select some of the packages.

- 
Raul

Notification sent to rdm@tad.micro.umn.edu (Raul Miller):
Bug acknowledged by developer. Full text available.
Reply sent to Raul Miller <moth@magenta.com>:
You have taken responsibility. Full text available.

Message received at debian-bugs:


From tad.micro.umn.edu!rdm Wed Oct 11 08:09:55 1995
Return-Path: <rdm@tad.micro.umn.edu>
Received: from pixar.com by mongo.pixar.com with smtp
	(Smail3.1.28.1 #15) id m0t32n5-000DxVC; Wed, 11 Oct 95 08:09 PDT
Received: from rdm.legislate.com ([192.77.155.13]) by pixar.com with SMTP id AA17726
  (5.67b/IDA-1.5 for debian-bugs-pipe@mongo.pixar.com); Wed, 11 Oct 1995 08:09:33 -0700
Received: by rdm.legislate.com
	id <m0t32n8-0006iKC@rdm.legislate.com>
	(Debian /\oo/\ Smail3.1.29.1 #29.33); Wed, 11 Oct 95 11:09 EDT
Message-Id: <m0t32n8-0006iKC@rdm.legislate.com>
Date: Wed, 11 Oct 95 11:09 EDT
From: rdm@tad.micro.umn.edu (Raul Miller)
To: debian-bugs@pixar.com
Subject: dselect conflict resolution is confusing

Package: dpkg
Version: 1.0.3

When in "conflict resolution" in deselect, it's difficult to deselect
the [old] conflicting package.  Ideally, you could just hit "-" to deselect
some such old package, but there's no visible confirmation that this works.

Furthermore, hitting RETURN (which I associate with "go down a level in
the hierarchy") sometimes presents a more detailed conflict resolution
mechanism and sometimes does not.

Furthermore, the select all packages option doesn't really select all
packages (which is also confusing).

-- 
Raul

Acknowledgement sent to rdm@tad.micro.umn.edu (Raul Miller):
New bug report received and forwarded. Full text available.
Report forwarded to debian-devel@pixar.com:
Bug#1640; Package dpkg. Full text available.
Ian Jackson / iwj10@thor.cam.ac.uk, with the debian-bugs tracking mechanism
This page last modified 07:43:01 GMT Wed 01 Nov