Debian bug report logs - #1640, boring messages

Subject: Bug#1640: dselect conflict resolution is confusing
Reply-To: rdm@tad.micro.umn.edu (Raul Miller), debian-bugs@pixar.com
Resent-From: rdm@tad.micro.umn.edu (Raul Miller)
Resent-To: debian-devel@pixar.com
Resent-Date: Wed, 11 Oct 1995 15:18:02 GMT
Resent-Message-ID: <debian-bugs-handler.1640.B10111513460@pixar.com>
Resent-Sender: iwj10@cus.cam.ac.uk
X-Debian-PR-Package: dpkg
X-Debian-PR-Keywords: 
Received: via spool for debian-bugs; Wed, 11 Oct 1995 15:18:02 GMT
Received: with rfc822 via encapsulated-mail; Wed, 11 Oct 1995 15:13:44 GMT
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

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

From: iwj10@thor.cam.ac.uk (Ian Jackson)
To: rdm@tad.micro.umn.edu (Raul Miller)
Subject: Bug#1640: Acknowledgement (was: dselect conflict resolution is confusing)
In-Reply-To: <m0t32n8-0006iKC@rdm.legislate.com>
References: <m0t32n8-0006iKC@rdm.legislate.com>

Thank you for the problem report you have sent regarding Debian GNU/Linux.
This is an automatically generated reply, to let you know your message has
been received.  It is being forwarded to the developers' mailing list for
their attention; they will reply in due course.

If you wish to submit further information on your problem, please send
it to debian-bugs@pixar.com, but please ensure that the Subject
line of your message starts with "Bug#1640" or "Re: Bug#1640" so that
we can identify it as relating to the same problem.

Please do not reply to the address at the top of this message,
unless you wish to report a problem with the bug-tracking system.

Ian Jackson
(maintainer, debian-bugs)

From: iwj10@thor.cam.ac.uk (Ian Jackson)
To: Raul Miller <moth@magenta.com>
In-Reply-To: <199510111528.LAA04019@magenta.com>
References: <199510111528.LAA04019@magenta.com> <m0t32n8-0006iKC@rdm.legislate.com>
Subject: Bug#1640: marked as done (was: dselect conflict resolution is confusing)

Your message dated Wed, 11 Oct 1995 11:28:38 -0400
with message-id <199510111528.LAA04019@magenta.com>
and subject line Bug#1640: dselect conflict resolution is confusing
has caused the attached bug report to be marked as done.

It is your now responsibility to ensure that the bug report is dealt
with.

(NB: If you are a system administrator and have no idea what I'm
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Ian Jackson
(maintainer, debian-bugs)

Received: with rfc822 via encapsulated-mail; Wed, 11 Oct 1995 15:13:44 GMT
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

From: iwj10@thor.cam.ac.uk (Ian Jackson)
To: rdm@tad.micro.umn.edu (Raul Miller)
Subject: Bug#1640 acknowledged by developer (was: dselect conflict resolution is confusing)
References: <199510111528.LAA04019@magenta.com> <m0t32n8-0006iKC@rdm.legislate.com>
In-Reply-To: <m0t32n8-0006iKC@rdm.legislate.com>

This is an automatic notification regarding your bug report.

Responsibility for it has been taken by one of the developers, namely
Raul Miller <moth@magenta.com>.

You should be hearing from them with a substantive response shortly, if
you have not already done so.  If not, please contact them directly,
or email debian-bugs@pixar.com or myself.

Ian Jackson
(maintainer, debian-bugs)

Subject: Bug#1640: dselect conflict resolution is confusing
Reply-To: Ian Jackson <iwj10@cus.cam.ac.uk>, debian-bugs@pixar.com
Resent-From: Ian Jackson <iwj10@cus.cam.ac.uk>
Resent-To: debian-devel@pixar.com
Resent-Date: Thu, 12 Oct 1995 00:33:04 GMT
Resent-Message-ID: <debian-bugs-handler.1640.B10120032100@pixar.com>
Resent-Sender: iwj10@cus.cam.ac.uk
X-Debian-PR-Package: dpkg
X-Debian-PR-Keywords: 
Received: via spool for debian-bugs; Thu, 12 Oct 1995 00:33:04 GMT
Received: with rfc822 via encapsulated-mail; Thu, 12 Oct 1995 00:32:08 GMT
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

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.

From: iwj10@thor.cam.ac.uk (Ian Jackson)
To: Ian Jackson <iwj10@cus.cam.ac.uk>
Subject: Bug#1640: Info received (was Bug#1640: dselect conflict resolution is confusing)
In-Reply-To: <m0t3B9f-0002ZwZ@chiark.al.cl.cam.ac.uk>
References: <m0t3B9f-0002ZwZ@chiark.al.cl.cam.ac.uk>

Thank you for the additional information you have supplied regarding
this problem report.  It has been forwarded to the developers to
accompany the original report.

If you wish to continue to submit further information on your problem,
please do the same thing again: send it to debian-bugs@pixar.com, ensuring
that the Subject line starts with "Bug#1640" or "Re: Bug#1640" so that
we can identify it as relating to the same problem.

Please do not reply to the address at the top of this message,
unless you wish to report a problem with the bug-tracking system.

Ian Jackson
(maintainer, debian-bugs)